action #55460
closed
flaky test: t/33-developer_mode.t - not ok 308 - Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out
Added by okurz over 4 years ago.
Updated over 4 years ago.
Category:
Regressions/Crashes
Description
Observation¶
See https://travis-ci.org/os-autoinst/openQA/jobs/571252191#L1404 2/20 test runs:
not ok 308 - Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out
# Failed test 'Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out'
# at /opt/testing_area/openqa/t/lib/OpenQA/Test/FullstackUtils.pm line 160.
- Related to action #53603: unstable test "t/33-developer_mode.t" added
- Related to action #53594: travis CI tests fail on master in t/33-developer_mode.t "owned by Demo (2 minutes ago, developer has 3 tabs open)' doesn't match '(?^:owned by Demo.*2 tabs open)" added
- Related to action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-stack.t added
According to the log the command set_pause_on_screen_mismatch has been sent and no disconnects happened at this time. Hence this should have worked. However, the response is really missing. So this is maybe even flaky behavior of the command processing itself and not only a flaky test.
- Status changed from New to Feedback
- Assignee set to okurz
- Status changed from Feedback to Resolved
- Target version set to Done
Also available in: Atom
PDF