action #91232
closed
Test t/ui/25-developer_mode.t failed in CI
Added by mkittler over 3 years ago.
Updated over 3 years ago.
Category:
Regressions/Crashes
Description
Observation¶
This is the log:
[02:42:03] t/ui/25-developer_mode.t ............... 12/?
# Failed test '#developer-panel .card-header visible'
# at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm line 271.
# Failed test '#developer-panel .card-header contains expected text'
# at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm line 280.
# ''
# doesn't match '(?^:paused at module: some test)'
# Looks like you failed 2 tests of 11.
# Failed test 'testname and paused state updated'
# at t/ui/25-developer_mode.t line 614.
# Looks like you failed 1 test of 5.
[02:42:03] t/ui/25-developer_mode.t ............... 13/?
# Failed test 'process state changes from os-autoinst/worker'
# at t/ui/25-developer_mode.t line 737.
Unfortunately it is not locally reproducible and I also haven't seen it previously or on further runs within the CI.
Acceptance criteria¶
- AC1: Test repeatedly stable in CI
Suggestions¶
- Run multiple times, potentially move to unstable list
- Try to fix and remove from unstable again
- Target version set to Ready
- Description updated (diff)
- Category set to Regressions/Crashes
- Status changed from New to Workable
- Due date set to 2021-04-30
Setting due date based on mean cycle time of SUSE QE Tools
- Assignee deleted (
mkittler)
I don't have a clue and since I've seen this failure only once it is likely not worth investigating it any further at this point.
So far I don't think that this is an issue caused by jQuery animations because those are disabled during the test (and enabling them causes the test to fail much sooner).
Not sure that we have a ticket for it yet but with #91659 it might be worth seeing if porting this test would demonstrate that PlayWright is better? In a call right now, but thinking to file a spike for that
- Copied to action #91884: [spike][timeboxed:18h] Demonstrate how Playwright helps with tricky UI tests added
- Status changed from Workable to Closed
I'm closing this ticket because it is likely not worth to further investigate this one-time failure. Of course we can still re-open the ticket if it happens again.
- Status changed from Closed to Rejected
- Assignee set to mkittler
- Related to action #80374: unstable/flaky/sporadic test t/ui/25-developer_mode.t added
mkittler wrote:
I'm closing this ticket because it is likely not worth to further investigate this one-time failure. Of course we can still re-open the ticket if it happens vxevleagain.
seems like we all grow old and have only a short-term memory :) See #80374
#80374 is a different failure. (But during my attempts to reproduce the error from this ticket I didn't came across the one from #80374.)
Also available in: Atom
PDF