action #47453
closed[qam][functional][y][fast] test fails in first_boot
0%
Description
Observation¶
openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xa6f4a78) fails in
first_boot
Reproducible¶
Fails since (at least) Build :10281:nginx
Expected result¶
Last good: :10308:openssl-1_1 (or more recent)
Further details¶
Previous tests goes directly to console screen (https://openqa.suse.de/tests/2451846#step/first_boot/1), current one gets to x11 login screen and fails.
Always latest result in this scenario: latest
Updated by bfilho about 5 years ago
Do you guys things this is related to the changes from https://progress.opensuse.org/issues/46682 ?
Updated by riafarov about 5 years ago
Indeed, we haven't un-selected all other patterns. We'll fix that as part of #46682
Updated by bfilho about 5 years ago
- Related to action #46682: [functional][y] lvm test need more than 2 hours to run - optimize select_patterns_and_packages added
Updated by JERiveraMoya about 5 years ago
PR: Exit earlier only when default in pattern selection -> merged
Updated by okurz about 5 years ago
- Subject changed from [qam] test fails in first_boot to [qam][functional][y][fast] test fails in first_boot
- Due date set to 2019-02-26
- Status changed from New to Feedback
- Assignee set to JERiveraMoya
- Target version set to Milestone 23
Please assign the ticket to yourself then. PR merged.
Updated by JERiveraMoya about 5 years ago
- Status changed from Feedback to Resolved
It should be fine now.
Updated by bfilho about 5 years ago
- Status changed from Resolved to Closed
Latest results seems fine on OSD. Thank you
Updated by JERiveraMoya about 5 years ago
- Status changed from Closed to Workable
Updated by JERiveraMoya about 5 years ago
- Status changed from Workable to In Progress
Updated by JERiveraMoya about 5 years ago
- Status changed from In Progress to Resolved
Sorry for the mail notifications, we don't use that work-flow, we use status resolved instead of closed to account for the work and for our automation as well. I hope it is ok.
Updated by okurz about 5 years ago
For further information regarding the ticket workflow: https://progress.opensuse.org/projects/openqav3/wiki/Wiki#ticket-workflow is what should be followed. Thanks JERiveraMoya for the explanation as well as the fast reaction and fast fix to the original issue :)