Actions
action #30646
closed[s390x][functional][fast][hard] Investigate why stress-tests fail starting with build 422.1
Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2018-01-22
Due date:
2018-02-13
% Done:
0%
Estimated time:
Difficulty:
Description
Description¶
- https://openqa.suse.de/tests/1405572
- https://openqa.suse.de/tests/1405076
- https://openqa.suse.de/tests/1405077
All of them fail while preparing the SUT. However, the previous runs where all successful but without further investigation I struggle to find a suitable product issue I can blame.
Hypothesis:¶
- REJECTED okurz mentioned a hypothesis about an not properly escaped asterisk in the sed-command. A first quick look of mine in the previous runs couln't confirm this no, but to get rid of the warnings -> https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4260
- ACCEPTED Did the network environment of this s390 instance change? -> might be, but found no evidence for this
- REJECTED test changed -> no test changes
- REJECTED Product bug -> crosschecked with different build/worker configurations - issue persists
- ACCEPTED s390p8 received an upgrade shortly before failing - there was a qemu update which might be the cause -> still we only could reproduce it sporadicly
- ACCEPTED s390p8 had a temporary hiccup - needs long-term statistics
Acceptance criteria:¶
Find out if this is a product bug (1) or test related (2).
(1): REJECTED Create a suitable bug report on bsc and try to relabel jobs pointing on this issue here -> no product bug, see H4
(2): REJECTED Fix the test so they can continue like before -> no test issue - see H3
Actions