Open
Conversation
Instead of having OUTCOME_SKIP for manually skipped jobs and OUTCOME_NOT_SUPPORTED for any job that is skipped for a specific reason (failed dependencies, failed resources, unmet manifest), 3 new outcomes are created: - OUTCOME_SKIPPED_DEPENDENCY - OUTCOME_SKIPPED_RESOURCE - OUTCOME_SKIPPED_MANIFEST And OUTCOME_NOT_SUPPORTED is deprecated. Then the reason why the job was automatically skipped is indicated in the JSON report in the `skip_reason` section. Fix CHECKBOX-1337
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2509 +/- ##
==========================================
+ Coverage 58.92% 58.96% +0.04%
==========================================
Files 476 477 +1
Lines 48043 48085 +42
Branches 8578 8589 +11
==========================================
+ Hits 28308 28354 +46
+ Misses 18842 18835 -7
- Partials 893 896 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
pieqq
commented
Apr 27, 2026
Comment on lines
+276
to
+281
| # Add skip_reason if present | ||
| if job_state.result.skip_reason: | ||
| data["result_map"][job_id][ | ||
| "skip_reason" | ||
| ] = job_state.result.skip_reason | ||
|
|
Collaborator
Author
There was a problem hiding this comment.
I've run some tests without these lines (running a test plan and exporting as text, HTML, tar.xz), and it seems to work. I'm not sure if these are needed at all (except maybe with the old XLS exporter?).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Instead of having OUTCOME_SKIP for manually skipped jobs and OUTCOME_NOT_SUPPORTED for any job that is skipped for a specific reason (failed dependencies, failed resources, unmet manifest), 3 new outcomes are created:
OUTCOME_SKIPPED_DEPENDENCYOUTCOME_SKIPPED_RESOURCEOUTCOME_SKIPPED_MANIFESTAnd OUTCOME_NOT_SUPPORTED is deprecated but kept for backward compatibility (when using
merge-submissionswith subs made with older versions of Checkbox, for instance).Then the reason why the job was automatically skipped is indicated in the JSON report in the
skip_reasonsection.The HTML report is also updated to take these modifications into account.
Important: the "status" is still mapped to
skipfor all of these new outcomes, so that we don't break C3 processing for the moment.For more information, see the original specification document CR139.
Resolved issues
Fix CHECKBOX-1337
Documentation
Tests