Page MenuHomePhabricator

"Echo.checks for welcome message after signup" Selenium test randomly fails
Open, HighPublic

Description

Two Selenium gate-and-submit builds (#96757 for change 731277, and #96764 for change 748299) have failed with the same errors:

[0-0] Error in "Echo.checks for welcome message after signup"
Error: element (".mw-echo-ui-notificationItemWidget-content-message-header") still not displayed after 5000ms
    at /workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/webdriverio/build/commands/browser/waitUntil.js:66:23
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Element.elementErrorHandlerCallbackFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/webdriverio/build/middlewares.js:24:32)
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Element.elementErrorHandlerCallbackFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/webdriverio/build/middlewares.js:24:32)
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Context.<anonymous> (/workspace/src/extensions/Echo/tests/selenium/specs/echo.js:56:3)
[0-0] RETRYING in chrome - /tests/selenium/specs/echo.js
[0-0] RUNNING in chrome - /tests/selenium/specs/echo.js
[0-0] Error in "Echo.checks for welcome message after signup"
Error: element (".mw-echo-ui-notificationItemWidget-content-message-header") still not displayed after 5000ms
    at /workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/webdriverio/build/commands/browser/waitUntil.js:66:23
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Element.elementErrorHandlerCallbackFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/webdriverio/build/middlewares.js:24:32)
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Element.elementErrorHandlerCallbackFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/webdriverio/build/middlewares.js:24:32)
    at async Element.wrapCommandFn (/workspace/src/extensions/Echo/node_modules/@wdio/runner/node_modules/@wdio/utils/build/shim.js:131:29)
    at async Context.<anonymous> (/workspace/src/extensions/Echo/tests/selenium/specs/echo.js:56:3)
[0-0] FAILED in chrome - /tests/selenium/specs/echo.js (1 retries)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Also happened at #96770 for change 743951. Since it affects at least three extensions, and seems to happen fairly regularly (though I’m not sure if it always happens), I think it can count as UBN.

Timing is suspiciously close to T293073: Refactor Echo WebdriverIO tests from sync to async mode so CCing some people there.

Right, I was about to say that is probably the cause. Having a look.

Change 754491 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/Echo@master] selenium: Skip flaky test

https://gerrit.wikimedia.org/r/754491

Change 754491 merged by jenkins-bot:

[mediawiki/extensions/Echo@master] selenium: Skip flaky test

https://gerrit.wikimedia.org/r/754491

Change 754527 had a related patch set uploaded (by Zabe; author: Zabe):

[mediawiki/extensions/Echo@master] selenium: reenable skipping of flaky test

https://gerrit.wikimedia.org/r/754527

Change 754527 merged by jenkins-bot:

[mediawiki/extensions/Echo@master] selenium: reenable skipping of flaky test

https://gerrit.wikimedia.org/r/754527

Zabe lowered the priority of this task from Unbreak Now! to High.Jan 17 2022, 6:33 PM

Is this still unbreak now?

Imo no since we are skipping the flaky test for now.