Repository navigation
ci: retain native React unit failure diagnostics - #1247
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This branch was successfully deployed
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.
Native React cockpit unit failures currently reach CI as a failed Nx target without the failing assertion. Run those tests with an explicit default reporter, followed by the existing lint target, so CI retains the test name, expected value and received value while preserving failure status. Refresh only the workflow's existing inventory fingerprint.
A controlled failing fixture through the actual Nx executor exits with failure in both configurations; the explicit reporter exposes its assertion. The original Element failure on main remains unreproduced locally.
Validation: 100 workflow/matrix checks, all 984 unit tests across 19 native React examples on Node 22.14 (including all 28 Element tests), 726 React parity checks, Element lint, inventory ownership, workflow YAML and shell syntax, and diff checks passed. No application, timeout, retry, dependency or backend changes.