action #38276

Flaky 'test candidate list' at t/ui/18-tests-details.t

Added by szarate over 1 year ago. Updated 2 days ago.

Status:ResolvedStart date:06/07/2018
Priority:NormalDue date:
Assignee:okurz% Done:

0%

Category:Concrete Bugs
Target version:QA - future
Difficulty:
Duration:

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

log.txt Magnifier (1020 KB) szarate, 06/07/2018 12:09 pm


Related issues

Related to openQA Project - action #54032: flaky test: t/full-stack.t "not ok 44 - Cache tests", sub... Resolved 09/07/2019
Related to openQA Project - action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-sta... Workable 21/06/2018
Related to openQA Project - action #53858: flaky test: 25-cache-service.t Resolved 04/07/2019

History

#1 Updated by szarate over 1 year ago

  • 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

#2 Updated by okurz 8 months ago

  • Category set to Concrete Bugs

#3 Updated by okurz 7 months ago

  • 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

#4 Updated by okurz 7 months ago

  • Related to action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-stack.t added

#5 Updated by okurz 7 months ago

#6 Updated by okurz 7 months ago

  • Status changed from New to Feedback
  • Assignee set to okurz

https://github.com/os-autoinst/openQA/pull/2259 to remove "travis_retry" again after test stabilization – and proper testing in the PR

#7 Updated by tinita 6 months ago

I wonder why there isn't more output.
The test in question is is_deeply, which should at least report the difference...

#8 Updated by okurz 4 months ago

  • 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.

#9 Updated by okurz about 1 month ago

  • Status changed from Workable to Feedback
  • Assignee set to okurz

#10 Updated by okurz 2 days ago

  • 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