ci: classify native packaging failures#907
Closed
luoye520ww wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
This work is consolidated into #941, which contains the related CI diagnostics and packaged smoke fix as one tested PR. Closing this duplicate to avoid parallel review and PR noise. |
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
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.
Problem
Packaging failures currently require reading the full CI log to decide whether the cause is code, packaging, artifact layout, or a GitHub runner outage. This has already caused code changes to be blamed for infrastructure failures.
Scope
This PR adds a pure packaging-failure classifier and tests. It does not change CI workflows or rerun policy.
Changes
npm.cmdon Windows.Safety
Typecheck
Passed.
Tests
Passed: 5 classifier tests; root lint and build passed; diff check passed.
Review performed
Non-goals
Follow-ups
H2 can consume this classifier for path-based native smoke reporting, and H3 can expose the same reproduction commands locally.