You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modern UWP projects targeting .NET 10 can build successfully, but InvokeTestingPlatform rejects their AppX recipe because the .NET 10 tooling packages obj\...\apphost.exe under the published application executable name instead of using the bin\...\<Assembly>.exe path as the recipe source.
Changes
Preserve exact recipe source matching, then fall back to the unique executable package path declared by the AppX manifest.
Select the packaged net9 app-model controller for net10 UWP consumers, matching the package asset fallback.
Retarget the real Modern UWP acceptance asset to net10 and stage its registration inputs in a short physical path so AppX path canonicalization does not make the test depend on checkout length.
The new fallback’s safety depends on rejecting ambiguous manifest matches, but the added test only covers a single application. A package with Apps1\Host.exe and Apps2\Host.exe produces two candidates for a requested Host.exe; if this guard regresses to selecting either candidate, the current unit and acceptance tests still pass while the launcher can activate the wrong AUMID. Please add a materialization test that constructs this shape and asserts that it is rejected.
Triggering check: microsoft.testfx (Build Linux Release). This is partial (early) evidence, and other build legs may still change the conclusion.
Failures on the Linux Release leg (net11.0, MSTest.Acceptance.IntegrationTests)
MSTestSdk_UnpackagedWinUIWithExplicitPackagedAppExtension_KeepsDirectLaunch (SdkTests.cs line 1070)
MSTestSdk_ConsoleWithExplicitPackagedAppExtension_KeepsDirectLaunch (SdkTests.cs line 1084)
Both fail with the same signature. AssertOutputContains reports "Expected string to contain the specified substring" on the output of dotnet build -restore -t:PrintWindowsTestContract. That command exited with code 0, so the build succeeded. The expected text is missing from its output.
Related signal, different leg (Windows App Model Diagnostics)
PackagedWinUI.PackagedWinUITestCases.RetryTestMethod_PassesOnSecondAppContainerHost failed with "The first AppContainer host fails so Retry must activate a second host."
I have not confirmed that this is related to the two failures above.
Assessment
Confidence: medium-high that this PR causes the two Linux failures. It changes src/Package/MSTest.Sdk/Sdk/Runner/Common.targets, PackagedAppTestHostLauncher.cs, SdkTests.cs and WindowsApplicationModelTestTools.cs. The failing tests sit in the changed area, and a build succeeding while the expected PrintWindowsTestContract output is missing points to a targets/property-condition mismatch.
I have no evidence that a retry recovered either failure, so I am not calling them flaky.
History coverage is incomplete (early-analysis), so I make no claim about earlier occurrences on main.
Next step
Inspect the PrintWindowsTestContract output in the .binlog for the two failing test assets. Check whether the explicit packaged-app extension case now emits different contract text under net11.0 on Linux.
Update either the expected substrings in SdkTests.cs or the target logic in Common.targets.
Wait for the final resolution once the full build completes.
🤖 Automated content by GitHub Copilot. Generated by the Pipeline Test Triage workflow. · copilot · auto · 36.5 AIC · ⌖ 6.2 AIC · ⊞ 9.6K
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Note
This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.
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
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.
Modern UWP projects targeting .NET 10 can build successfully, but
InvokeTestingPlatformrejects their AppX recipe because the .NET 10 tooling packagesobj\...\apphost.exeunder the published application executable name instead of using thebin\...\<Assembly>.exepath as the recipe source.Changes
Validation
InvokeTestingPlatform.Fixes: #11601