Repository navigation
test(package): trim and time consumer Git fixture setup - #118
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
The Windows package-consumer run reported 73 seconds for fixture setup, three installs and generated-file checks together. Give each operation its own elapsed time on stderr.
Initialize the three fixture repositories and their clones with an empty, test-owned Git template. Commit the one tracked file changed by the rollback test directly. The repositories, commits, installed npm shim and late failure remain real.
Compatibility
This changes only the consumer proof. The installed packages, app order, compiler pins, isolated consumer, byte-for-byte comparisons and release assertions are the same.
Verification