Actions
action #179563
opencoordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #179572: [epic] Improved test reviewer user experience - job dependencies and status
Provide a reason when tests end up in the skipped state
Start date:
2025-03-27
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
The reason why a job may end up skipped is not always clear. In our upstream openQA documentation we state the following:
skipped Dependencies failed so the job was not started.
So a job may be skipped because a dependency failed? In practice this may not be specific enough or not even true.
Suggestions¶
- Include a pointer in the reason when a job is skipped
- Link to documentation about job state
Updated by livdywan 4 days ago
- Copied from action #179545: Skipped dependencies with START_DIRECTLY_AFTER_TEST size:M added
Actions