Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tim.plunkett created an issue. See original summary.

tim.plunkett’s picture

Status: Active » Needs review
FileSize
2.26 KB
tedbow’s picture

+++ b/core/modules/layout_builder/tests/src/FunctionalJavascript/FieldBlockTest.php
@@ -84,6 +84,7 @@ public function testFieldBlock() {
+    $assert_session->waitForText('The block configuration has been saved.');
     $assert_session->pageTextContains('The block configuration has been saved.');

You could do this in 1 line
$this->assertNotEmpty($assert_session->waitForText('The block configuration has been saved.'));
You wouldn't need to call pageTextContains() then.

Status: Needs review » Needs work

The last submitted patch, 2: 2937073-field_block-2.patch, failed testing. View results

tim.plunkett’s picture

Status: Needs work » Needs review
FileSize
2.57 KB
2.38 KB

That CSS trick is nice, but not robust enough to rely on.

tedbow’s picture

This looks good. The new \Drupal\FunctionalJavascriptTests\JSWebAssert::waitForText() uses the same regex logic as existing \Behat\Mink\WebAssert::pageTextContains()

This should fix if the submit on the previous lines were slow down by testbot.

@tim.plunkett Could we get a patch that runs the updated test only x30(not sure if we can get more without timeout) and 1 that runs the current test only 30x? This could prove that 1 fails more often. I know they may likely both come back green but worth a shot.

See here for changes needed to run-tests.sh to run a single test mutiple times https://www.drupal.org/files/issues/2830485-142-100x.patch

Hmm that did 100x for some reason I thought it would time out. Could try that.

tim.plunkett’s picture

tim.plunkett’s picture

Component: layout.module » layout_builder.module
borisson_’s picture

There are no failures in #7, but the change does look good. Should we try this with more passes on the fragile test?

tim.plunkett’s picture

Status: Needs review » Needs work
Issue tags: +Needs reroll

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

savkaviktor16@gmail.com’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
FileSize
2.54 KB

Re-rolled against 8.7.x

tim.plunkett’s picture

Thanks for the reroll. As I wrote the patch, someone else should perform the final review for RTBC.

Kristen Pol’s picture

Status: Needs review » Reviewed & tested by the community

The code looks fine to me. I don't think there is any way to manually test this. Since tests are passing, marking RTBC.

The last submitted patch, 7: 2937073-field_block-7.patch, failed testing. View results

xjm’s picture

Priority: Normal » Major
Issue tags: +Random test failure

So according to the IS this caused a random test failure, but I haven't gotten an email about it failing since April, so looks like a low fail rate. Promoting to major for that reason (instead of critical).

xjm’s picture

Fixing issue credit.

Normally for a random test failure I'd want to see an illustration that the random fail was fixed via bulk test runs (where the bulk test run of unpatched HEAD showed consistent fails by deliberately slowing the page down or such), but since the fail rate on this appears to be very low, it might be infeasible. Furthermore, according to @tim.plunkett:

I think it only failed randomly with PhantomJS
the switch to chromedriver really cut down on those sorts of random fails

  • xjm committed 06dbc81 on 8.7.x
    Issue #2937073 by tim.plunkett, Saviktor, tedbow: Improve robustness of...

  • xjm committed 6c78d26 on 8.6.x
    Issue #2937073 by tim.plunkett, Saviktor, tedbow: Improve robustness of...
xjm’s picture

Version: 8.7.x-dev » 8.6.x-dev
Status: Reviewed & tested by the community » Fixed

Committed to 8.7.x and cherry-picked to 8.6.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.