-
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][xharness] install development SSL certificate on Helix agent before xharness run via SDK or powershell #53280
Conversation
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
Browser windows:
|
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
Not sure if this PR will fix it, but noticing lots of failures of the form:
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-53212-merge-53c30b46d5f14dc0b0/XsltCompiler.Tests/console.a4a5589c.log?sv=2019-07-07&se=2021-06-16T04%3A55%3A12Z&sr=c&sp=rl&sig=ZTsowdh4FokJOmTDEzlrz04dVXOJpWfNSu0XOkzmOmA%3D |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope this doesn't bite anyone because there will be a different SDK/runtime but I guess we only use it to start XHarness, right?
1cd915c
to
802d62c
Compare
e85867a
to
dfba946
Compare
Last failure was in
|
dfba946
to
eba9934
Compare
.. because `dotnet dev-certs https` shows a dialog on windows, which would require user interaction.
Installer test failure:
Tracked at #43316 . This seems to be an intermittent error, and unrelated to this PR. Merging. |
Caused by #53180, #53225
dotnet dev-certs https
needs user interaction with a dialog. Instead, using powershelgl to install certsWasm.Build.Tests
are being disabled here because of [wasm] Wasm.Build.Tests failing #53405Fixes #53207