Repository navigation
Publish specification timing reports and shard browser specs in CI - #271
Merged
Merged
Conversation
Vitest writes JUnit reports only when SPEC_REPORTS_DIR is set, so local runs are unchanged. .NET specification results are now uploaded on every run with a 3-day retention and summarized in the job summary.
Shards are assigned from the discovered browser workspaces and run against the built artifacts, uploading their JUnit reports for the summary.
A zero-test JUnit suite or TRX counter, or a non-numeric count, used to summarize successfully and let a shard report green without evidence. Counts must now be non-negative integers, durations finite, and every report must record at least one test.
Contributor
Author
|
Reviewer notes (not release notes)
|
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.
Added
Changed