-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/7.0] Update dependencies from dotnet/xharness #83828
[release/7.0] Update dependencies from dotnet/xharness #83828
Conversation
…30313.1 Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 1.0.0-prerelease.22411.1 -> To Version 1.0.0-prerelease.23163.1
@lewing or @steveisok - Would you mind helping with the merge conflict?
|
…/7.0-e0c22b06-a5e0-4836-b07a-f7b966c36308
Done! |
@steveisok @lewing There's a failure that seems related to this PR. It's affecting mainly wasm linux queues, but also MacCatalyst. The two key error messages are:
Affected queues:
Full error message:
|
@akoeplinger where does arcade pick up what sdk version to install? |
Reminder: Code complete is on April 10th to ensure this change gets included in the May Servicing Release. |
From here if I remember correctly https://github.com/dotnet/arcade/blob/d7b5c2c026141e80abf3acca2f957c52949929cc/src/Microsoft.DotNet.Helix/Sdk/tools/dotnet-cli/DotNetCli.props#L6 But I think we should wait for the xharness branch: dotnet/xharness#1010 |
Per the conversation in the 6.0 xharness dependency flow PR, I have disabled runtime's darc subscriptions to xharness in 6.0 and 7.0, and we can close the PRs. |
This pull request updates the following dependencies
From https://github.com/dotnet/xharness