Repository navigation
Batch, merge and shard the package integration tests to cut PR time - #622
Merged
Merged
Conversation
…de requirement from archive checks
botoddly
force-pushed
the
faster-package-tests
branch
from
October 5, 2026 13:49
44de3b8 to
cd33ab4
Compare
stanoddly
enabled auto-merge (squash)
October 5, 2026 13:50
|
📦 Development package |
|
✅ Development package validation passed on all platforms. |
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.
The package integration job decided PR time: 9 m 24 s for 66 tests run one at a time, against under 4 minutes for the validation job.
BrowserBuildRejectsInvalidTargetPathbuilds are 5, one perPIXELY0011check, because the first failing check stops the target. Each build declares its paths through an items file the fixture imports (BrowserContentConsumerExtraItems). The test now asserts that the error names every rejected path, not only the code._framework/y.pakbeside_Framework/x.pak: MSBuild batches ignoring case, so two spellings of one path would share a batch and only one would reach the pattern. The error must name each path as a whole word, soC:/abs.pakdoes not stand in for/abs.pak.HostedConsumerPublishesABrowserBundle, which now publishes with--runtimeand its implicit restore.dotnet buildordotnet publishwith its implicit restore instead of a separatedotnet restore. NU restore warnings still appear in that output.package-integration (1/2)and(2/2), each packing Pixely. A[SetUp]readsPIXELY_PACKAGE_TEST_SHARD, orders the test methods by name and deals them out in turn, so every test runs in exactly one job. A test filter cannot split them: NUnit does not select an explicit test through a negated filter. Onlypull-request-validationis a required check, so the renamed jobs do not block merging.Verification