Uh oh!
There was an error while loading. Please reload this page.
[release/8.0-staging] Update dependencies from dotnet/xharness - #123123
[release/8.0-staging] Update dependencies from dotnet/xharness#123123dotnet-maestro[bot] wants to merge 1 commit into
Conversation
…60112.2 On relative base path root Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 8.0.0-prerelease.25516.2 -> To Version 11.0.0-prerelease.26062.2
jeffhandley
commented
Jan 13, 2026
@mmitche / @hoyosjs - These errors are unusual. Do you have guidance on this? |
mmitche
commented
Jan 15, 2026
Xharness jumped forward to 11.0 in this PR. which seems wrong. |
mmitche
commented
Jan 15, 2026
All the xharness subscriptions are currently set to "Eng - Latest" for all runtime branches. |
mmitche
commented
Jan 15, 2026
@jeffhandley 3 weeks ago, the 9.0 staging branch appeared to have been pulling from .NET 9 Eng. Now it's pulling from Eng - Latest. DOes that update ring any bells? |
steveisok
commented
Jan 26, 2026
@jeffhandley@mmitche @dotnet/runtime-infrastructure what should we do here? |
mmitche
commented
Jan 26, 2026
I think close this and then fix the input channel. |
kotlarmilos
commented
Feb 18, 2026
All branches use the latest Apple mobile queues, which require the latest XHarness. Since we don’t test Apple mobile on older versions, we should keep the latest channel for all branches, as it is now. |
kotlarmilos
commented
Feb 18, 2026
Triggered the subscription again #124544 |
This pull request updates the following dependencies
From https://github.com/dotnet/xharness