Note: I'm not sure that I posted the issue in the right project. Please move the issue if I mistaken.

Problem/Motivation

Take a look at #2562107-77: EntityDisplayBase should react on removal of its components dependencies. There you can find 2 failed tests (PHP 5.5) and other 2 that have passed (first PHP 5.5, second 5.6). The failed test passes successfully on other 3 computers (see comments below #77).

From the test log:

18:15:34 Segmentation fault (core dumped)
18:15:34 FATAL Drupal\user\Tests\Migrate\MigrateUserProfileEntityDisplayTest: test runner returned a non-zero error code (139).

This test failed and never failed before.

I'm attaching the diff between a failed and passed test, both on PHP 5.5. I don't see anything wrong there except the patch has been applied to different versions of 8.0.x HEAD due to time interval. But, investigating the commits between, I see nothing that can affect the bot. Note that the passed local test was in the same time with the bot failed test, so both were against the same HEAD.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#2 bot-diff-do-not-test.diff338.12 KBclaudiu.cristea
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

claudiu.cristea created an issue. See original summary.

claudiu.cristea’s picture

FileSize
338.12 KB

Forgot the attachment.

Mixologic’s picture

Component: Code » Unexplained Failures/Support
xjm’s picture

Title: Inconsistent test run » Random segfault in MigrateUserProfileEntityDisplayTest
xjm’s picture

Mixologic’s picture

Status: Active » Closed (cannot reproduce)

This looks like another out of date issue. There are few examples of this particular error in the logs, all of them in the last 100000 builds or so appear to be specifically related to the patch being applied, and attributable to any randomness. Im going to close this one unless theres a bigger pattern that I should be searching for.

xjm’s picture