action #95721
closed
[Sporadic] containers: tests fail with "Test died: no candidate needle with tag(s) 'inst-console' matched" size:M
Added by ilausuch over 3 years ago.
Updated over 3 years ago.
Category:
Regressions/Crashes
- Priority changed from Normal to High
- Target version set to Ready
The test is switching to tty3 and waits for it by looking for the needle inst-console. After the assert_screen fails tty3 shows up. So was the SUT just too slow (slower than the timeout of 30 seconds)?
- Subject changed from [Sporadic] containers: tests fail with "Test died: no candidate needle with tag(s) 'inst-console' matched" to [Sporadic] containers: tests fail with "Test died: no candidate needle with tag(s) 'inst-console' matched" size:M
- Description updated (diff)
- Description updated (diff)
- Status changed from New to Workable
I found that since now (in one month) we had 8 occurrences, and more o less one per day
- Status changed from Workable to In Progress
- Due date set to 2021-08-19
Setting due date based on mean cycle time of SUSE QE Tools
I want to probe that this solution is good enough launching 40 tests.
If we have all en green we could assume that the solution is ok (but not with all garnaties). On the other hand, if we have a red one failing in this point we can say that 1 minute is enough to change to the terminal screen and therefore the solution is not good and we have to find an other one
I launched these tests
1884704, 1884706 - 1884725, 1884733 - 1884753 (exclue 1884705)
- Status changed from In Progress to Resolved
Thanks. With this information we can regard the initial problem as something temporary that we do not want to fix right now. Although I assume the very same could come back and then we should look into extending the initial timeout.
Also available in: Atom
PDF