Uh oh!
There was an error while loading. Please reload this page.
[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
matouskozak
commented
Apr 8, 2025
@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
akoeplinger
commented
Apr 16, 2025
yeah the wasm failures are unrelated so we can merge |
akoeplinger
commented
Apr 16, 2025
/ba-g wasm failures are not related to xharness changes |
matouskozak
commented
Apr 17, 2025
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 |
matouskozak
commented
Apr 17, 2025
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