-
Notifications
You must be signed in to change notification settings - Fork 5k
[main] Update dependencies from dotnet/xharness #114057
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
[main] Update dependencies from dotnet/xharness #114057
Conversation
…50326.1 Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 10.0.0-prerelease.25167.4 -> To Version 10.0.0-prerelease.25176.1
…50402.1 Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 10.0.0-prerelease.25167.4 -> To Version 10.0.0-prerelease.25202.1
@lewing what are the usual steps to merging updates from xharness? I see there are some wasm issues (one is still hanging) but these appear to be tracked. |
…50411.1 Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 10.0.0-prerelease.25167.4 -> To Version 10.0.0-prerelease.25211.1
yeah the wasm failures are unrelated so we can merge |
/ba-g wasm failures are not related to xharness changes |
It looks like my change to xharness (dotnet/xharness#1383) broke the mobile runtime tests build https://dev.azure.com/dnceng-public/public/_build/results?buildId=1018649
|
The range of commits when the regression happened is d97ad23...bdd0dae . Looking at the error message I think it might be caused by dotnet/xharness#1388 cc: @pavelsavara |
Looks like you already have a fix #114746 merged. I'll wait for next |
This pull request updates the following dependencies
From https://github.com/dotnet/xharness