action #38276
closed
Flaky 'test candidate list' at t/ui/18-tests-details.t
Added by szarate over 6 years ago.
Updated almost 5 years ago.
Category:
Regressions/Crashes
Description
I've seen this one couple of times already...
ok 31 - at most one needle is selected at a time (0 selected)
not ok 32 - 100%, 52%
ok 33 - can open JSON file for reading
Files
- Subject changed from Flaky 'test candidate list' at t/ui/18-tests-details.t to Flaky 'test candidate list' at t/ui/18-tests-details.t
- Category set to Regressions/Crashes
- Related to action #54032: flaky test: t/full-stack.t "not ok 44 - Cache tests", subtest: "not ok 17 - test 6 is passed" at /opt/testing_area/openqa/t/lib/OpenQA/Test/FullstackUtils.pm line 120. added
- Related to action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-stack.t added
- Status changed from New to Feedback
- Assignee set to okurz
I wonder why there isn't more output.
The test in question is is_deeply
, which should at least report the difference...
- Status changed from Feedback to Workable
- Assignee deleted (
okurz)
We moved to circle CI, I did not yet look into the unstable tests on circle CI but we still have a list with "unstable" tests handled within circle CI as well.
- Status changed from Workable to Feedback
- Assignee set to okurz
- Status changed from Feedback to Resolved
I haven't seen this module failing since 62c5546ad so I assume this fixed it. Also, as our list of "unstable" tests is currently empty but tests seem to be stable I regard this as resolved.
Also available in: Atom
PDF