-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] Wasm.Build.Tests failing #53405
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
This commit might be the one responsible:
Looking at the checks on the PR #53231, This is a build before the PR was merged - https://dev.azure.com/dnceng/public/_build/results?buildId=1159218&view=logs&s=96ac2280-8cb4-5df5-99de-dd2da759617d And this is after: https://dev.azure.com/dnceng/public/_build/results?buildId=1159354&view=logs&j=108d2c4a-8a62-5a58-8dad-8e1042acc93c&t=568f884b-cc12-5fd3-e7fe-790b5ac403f4 cc @adamsitnik
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
…efore xharness run via SDK or powershell (#53280) Co-authored-by: Ankit Jain <[email protected]> Caused by #53180, #53225 - The original approach to install certificates didn't work because we don't have dotnet SDK, just runtime on Helix agents. - dotnet dev-certs https needs user interaction with a dialog. Instead, using powershelgl to install certs - Wasm.Build.Tests are being disabled here because of #53405 Fixes #53207
.. as dotnet#53405 is fixed.
@adamsitnik no worries. Thanks for the quick fix. I have opened #53433 to re-enable the tests. |
This commit might be the one responsible:
Looking at the checks on the PR #53231,
Wasm.Build.Tests
were failing.This is a build before the PR was merged - https://dev.azure.com/dnceng/public/_build/results?buildId=1159218&view=logs&s=96ac2280-8cb4-5df5-99de-dd2da759617d
And this is after: https://dev.azure.com/dnceng/public/_build/results?buildId=1159354&view=logs&j=108d2c4a-8a62-5a58-8dad-8e1042acc93c&t=568f884b-cc12-5fd3-e7fe-790b5ac403f4
@adamsitnik please correct me if I got this wrong
The text was updated successfully, but these errors were encountered: