Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flaky e2e test: incorrect-locale has been failing constantly in "after each" hook #9543

Open
tatilepizs opened this issue Oct 14, 2024 · 2 comments
Labels
Flaky Indicates a flaky or unreliable test Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice

Comments

@tatilepizs
Copy link
Contributor

tatilepizs commented Oct 14, 2024

Describe the issue
E2e test /tests/e2e/default/translations/incorrect-locale.wdio-spec.js has been failing constantly in the "after each" hook due to timing

------------------------------------------------------------------
[chrome 90.0.4430.72 linux #0-5] Running: chrome (v90.0.4430.72) on linux
[chrome 90.0.4430.72 linux #0-5] Session ID: 62d09db66cd013a39458898546df0548
[chrome 90.0.4430.72 linux #0-5]
[chrome 90.0.4430.72 linux #0-5] » /tests/e2e/default/translations/incorrect-locale.wdio-spec.js
[chrome 90.0.4430.72 linux #0-5] Testing Incorrect locale
[chrome 90.0.4430.72 linux #0-5]    ✖ should work with incorrect locale
[chrome 90.0.4430.72 linux #0-5]    ✖ "after each" hook for Testing Incorrect locale
[chrome 90.0.4430.72 linux #0-5]
[chrome 90.0.4430.72 linux #0-5] 1 failing (5m 5.1s)
[chrome 90.0.4430.72 linux #0-5]
[chrome 90.0.4430.72 linux #0-5] 1) Testing Incorrect locale should work with incorrect locale
[chrome 90.0.4430.72 linux #0-5] Timeout of 120000ms exceeded. The execution in the test "Testing Incorrect locale should work with incorrect locale" took too long. Try to reduce the run time or increase your timeout for test specs (https://webdriver.io/docs/timeouts). (/home/runner/work/cht-core/cht-core/tests/e2e/default/translations/incorrect-locale.wdio-spec.js)
[chrome 90.0.4430.72 linux #0-5] Error: Timeout of 120000ms exceeded. The execution in the test "Testing Incorrect locale should work with incorrect locale" took too long. Try to reduce the run time or increase your timeout for test specs (https://webdriver.io/docs/timeouts). (/home/runner/work/cht-core/cht-core/tests/e2e/default/translations/incorrect-locale.wdio-spec.js)
[chrome 90.0.4430.72 linux #0-5]     at createTimeoutError (/home/runner/work/cht-core/cht-core/node_modules/mocha/lib/errors.js:498:15)
[chrome 90.0.4430.72 linux #0-5]     at Test.Runnable._timeoutError (/home/runner/work/cht-core/cht-core/node_modules/mocha/lib/runnable.js:429:10)
[chrome 90.0.4430.72 linux #0-5]     at Timeout.<anonymous> (/home/runner/work/cht-core/cht-core/node_modules/mocha/lib/runnable.js:244:24)
[chrome 90.0.4430.72 linux #0-5]     at listOnTimeout (node:internal/timers:573:17)
[chrome 90.0.4430.72 linux #0-5]     at processTimers (node:internal/timers:514:7)
[chrome 90.0.4430.72 linux #0-5]
[chrome 90.0.4430.72 linux #0-5] 2) Testing Incorrect locale "after each" hook for Testing Incorrect locale
[chrome 90.0.4430.72 linux #0-5] Timeout
[chrome 90.0.4430.72 linux #0-5] Error: Timeout
[chrome 90.0.4430.72 linux #0-5]     at listOnTimeout (node:internal/timers:573:17)
[chrome 90.0.4430.72 linux #0-5]     at processTimers (node:internal/timers:514:7)
------------------------------------------------------------------

This is an example run

Here is the artifact in case it is helpful -> incorrect-locale-ci-webdriver-default-core-minimum-browser.zip

@tatilepizs tatilepizs added Type: Technical issue Improve something that users won't notice Testing Affects how the code is tested Flaky Indicates a flaky or unreliable test labels Oct 14, 2024
@garethbowen
Copy link
Member

@tatilepizs Could you please include the log as a text snippet rather than a screenshot so we can find this issue when doing a text search?

@tatilepizs
Copy link
Contributor Author

Sure, I updated the description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Flaky Indicates a flaky or unreliable test Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Projects
Status: Todo
Development

No branches or pull requests

2 participants