Actions
action #60209
closedflaky/unstable test in OBS t/17-labels_carry_over.t
Status:
Resolved
Priority:
Low
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2019-11-24
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
Visit https://build.opensuse.org/package/live_build_log/devel:openQA:tested/openQA/openSUSE_Tumbleweed/x86_64
Package devel:openQA:tested/openQA failed to build in openSUSE_Tumbleweed/x86_64
Check out the package for editing:
osc checkout devel:openQA:tested openQA
Last lines of build log:
[ 1353s] ok 4 - no (unexpected) warnings (via done_testing)
[ 1353s] 1..4
[ 1353s] ok
[ 1353s]
[ 1353s] Test Summary Report
[ 1353s] -------------------
[ 1353s] ./t/17-labels_carry_over.t (Wstat: 512 Tests: 9 Failed: 2)
[ 1353s] Failed tests: 6, 8
Reproducible¶
Happened multiple times in OBS projects devel:openQA and devel:openQA:tested so far but not in circleci AFAIK (okurz) so most likely can only be reproduced in OBS.
Workaround¶
Retrigger
Updated by okurz almost 5 years ago
happened again. https://github.com/os-autoinst/openQA/pull/2662 to exclude from OBS tests
Updated by livdywan almost 5 years ago
- Status changed from New to In Progress
- Assignee set to okurz
- Target version changed from future to Current Sprint
Updated by okurz almost 5 years ago
- Status changed from In Progress to New
- Assignee deleted (
okurz) - Target version changed from Current Sprint to future
merged the PR to exclude the test but I don't plan further steps right now. This is why I haven't even assigned myself to the ticket.
Updated by okurz almost 5 years ago
- Related to action #53498: [sporadic] openQA CI tests fail on master in flaky/unstable t/ui/26-jobs_restart.t added
Updated by okurz almost 5 years ago
- Status changed from New to Feedback
- Assignee set to okurz
Checking stability in https://github.com/os-autoinst/openQA/pull/2496
Updated by okurz almost 5 years ago
- Status changed from Feedback to Blocked
waiting for #59043 , need to understand if make variables are properly passed into the scope for "stability_test"
Updated by okurz almost 5 years ago
- Status changed from Blocked to Resolved
Despite my experiments I could not see this module as failing easily. I decide to keep it excluded from OBS tests but not plan further actions.
Actions