Problem/Motivation

Might not be random, but this just broke the branch tests on 9.2.x.

1) Drupal\Tests\field_ui\FunctionalJavascript\EntityDisplayTest::testExtraFields
WebDriver\Exception\CurlExec: Curl error thrown for http POST to http://chromedriver-jenkins-drupal8-core-regression-tests-35995:9515/session/a8b8ea18b9520c6785c23f17f705a552/execute with params: {"script":"(function (element) {\n    var event = document.createEvent(\"HTMLEvents\");\n\n    event.initEvent(\"drop\", true, true);\n    event.dataTransfer = {};\n\n    element.dispatchEvent(event);\n}(arguments[0]));","args":[{"ELEMENT":"0.4273382782664239-5"}]}

Retries: 10 and last result:
{"sessionId":"a8b8ea18b9520c6785c23f17f705a552","status":10,"value":{"message":"stale element reference: element is not attached to the page document\n  (Session info: headless chrome=74.0.3729.157)\n  (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Linux 4.9.0-0.bpo.6-amd64 x86_64)"}}

https://dispatcher.drupalci.org/job/drupal8_core_regression_tests/35995/...

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3203712

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

catch created an issue. See original summary.

vijaycs85’s picture

We got a patch at #3211164: Random errors in Javascript Testing. I wonder if it is worth applying the patch to see if it fixes this issue.
oops, the patch is still in progress on #3211164: Random errors in Javascript Testing.

alexpott’s picture

    $disabled_region_row = $this->getSession()->getPage()->find('css', '.region-hidden-title');

    $extra_field_row->find('css', '.handle')->dragTo($disabled_region_row);

Unfortunately #3211164: Random errors in Javascript Testing will not fix this. What we need to work out is why the $disabled_region_row has been removed or replaced on the page. What possible triggers are there for that and if maybe we could use a different destination that cannot possibly be removed.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

spokje’s picture

danflanagan8’s picture

Just ran into this, also on 9.3.x: https://www.drupal.org/pift-ci-job/2199457

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

stephencamilo’s picture

Status: Active » Closed (won't fix)
danflanagan8’s picture

Status: Closed (won't fix) » Active

Restoring previous status.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

spokje’s picture

Nope, no impact at all.
Also no failure at all, so this _might_ be fixed elsewhere.

catch’s picture

Priority: Critical » Major

No activity here for two years and #12 is encouraging, so let's bump down to major but keep it open a bit longer just in case.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

acbramley made their first commit to this issue’s fork.

acbramley’s picture

Status: Active » Closed (outdated)

100 passes here https://git.drupalcode.org/issue/drupal-3203712/-/jobs/4660808

2 years since #14, I think we can close this one out.