Repository navigation
Backport metadata-first fixture discovery to rel/4.5 - #12291
Merged
Amaury Levé (Evangelink) merged 1 commit intoNov 9, 2026
Merged
Conversation
Amaury Levé (Evangelink)
deleted the
evangelink-rel-4-5-fixture-discovery
branch
November 9, 2026 18:39
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.
Backports metadata-first assembly fixture provider discovery from #12269 to
rel/4.5. Relates to #12287: this independently squashable PR contains only its fixture-discovery slice, not its Retry, cleanup, or IPC changes.Inspect PE metadata before loading unmarked dependencies, while preserving runtime binding/load-context authority, passive/transitive providers, diagnosed fallback, local-hook precedence, and duplicate-provider diagnostics. Retains the release's targets and public/shipped API baselines, with explicit
System.Reflection.Metadata8.0.0 dependency wiring.Provenance
127798de9bd5c3f7204dc8932cddf043bf4bd6c6.039c61b6c880b7a54b9bafb5cf9c6d67ab7005d0from Backport MSTest and MTP servicing fixes to rel/4.5 #12287 head826ef0f11a51e59861ceeb6e994917587add82d5.27c7271d8c8b50283e0cbbe16b953b6b45d25760; sole parent:a39964ce2cf09c4abcbaa7bb8f4e5818638a9de3.fb75cb075594600f191233eaf31a2181575c5fc7. All five affected C# files retain their UTF-8 BOMs.Standalone validation
Executed on this standalone commit on Windows x64, using repository-pinned SDK
12.0.100-alpha.1.26480.103. The build finished with the initially authorized borrowed SDK; subsequent test tooling used a private copy in this checkout. The existing net11.0 acceptance host uses its generated, pinned .NET 12 runtime configuration; no retargeting or .NET 11 runtime installation was needed.Passed, exit 0, 0 warnings / 0 errors.
$binaryLogwas the uniqueartifacts\log\Release\fixture-standalone\full-pack-c4538f12cdcd45df8b367ef934aa51d0.binlog. Full release assets, including classic/modern UWP and WinUI, compiled and packed; repository package-content/metadata validation passed. An initial scoped pack did not satisfy the repository-wide expected-package gate; this full pack resolved that setup failure without source changes.Focused provider unit execution used the following commands for all five existing targets:
Passed, all five exits 0: 13 per target, 65 executed/passed, 0 skipped. Fresh TRX results matched the exact source-derived method identities and counters.
Packaged-consumer discovery and execution:
Passed, discovery and execution exits 0. The independent source plan, discovery, and fresh outer TRX agree on 82 identities: 82 executed/passed, 0 skipped, including existing provider controls and real net8.0/net10.0/.NET Framework MTP/VSTest consumers. The execution verifier checked fresh timestamps, unique execution IDs, exact names, and report counters.
The 79 new consumer cases verified the restored PlatformServices payload against this checkout's freshly packed adapter; all 67 executing children also verified their loaded DLL bytes. Retained canonical attachments contain 79 resolved-assets reports and 79 child reports: 67 passing one-test children and 12 expected duplicate-provider failures with zero executed child results, not empty successes. All 316 retained package-content SHA-512 entries for the four packages below match the standalone nupkgs. The net10.0 consumer correctly selects the release's net9.0 adapter asset.
B6D4210BF719C3C19E9E25658B07DC74053C0455BD923ACC710D318C0E8673F5981D4FCDB2F72979C97A960612720DCC75CC1384ED21C499217F6CEDF0538266F3084D9A7B290C8DABFED705A9A51A6ED0336C593074A91B38E27C880E0EFB8D53A703E48AEA7A1F14680A464D892B58C330516C36314AEF397441B92B7797EFRaw TRX, attachments, source-plan identities, build logs/binlogs, and hash manifests are retained locally in the session's
fixture-standalone-proof.zip(SHA-25600BBF8CEE914BB8471172EE9C6828EAB87A4EBE79AEE01DC6B52CDA15E85226C). Normal assembly cleanup reclaimed the per-run package cache; only this checkout's 38 private-SDK workers were stopped, without a shared-server shutdown or cache clearing.Limits
The versioned decision record retains the original source-revision counterfactual evidence; that counterfactual was not rerun for this split PR. Real AppX/UWP activation, hosted UI/IDE behavior, and CI were not executed or validated here.