Repository navigation
test(release): bound slow Windows signer fixtures - #117
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
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.
Summary
A Windows matrix job exceeded the 10-second per-test setup deadline and the 5-second end-to-end proof deadline. The same fixtures passed on the other platforms.
Write the three Git configuration values into the fixture’s isolated config file in one operation. That removes 27 Git processes across nine cases. Give only the setup hook and the multi-process seal/admit case 30 seconds on Windows. Every test still gets a fresh repository, and each signature, provenance and rejection assertion still runs.
Validation