-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Browser wasm on windows CI builds broken #63987
Comments
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. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsWhile adding a new pipeline for the "extra" platforms (#62564) I've hit an issue with the browser wasm windows build legs:
The build pipeline is: https://dev.azure.com/dnceng/public/_build/results?buildId=1559642&view=logs&jobId=854f6d42-496e-5e8c-a1c9-7f7194a94a83&j=bce77159-c177-5da3-02f5-74ccd320a9d5&t=55fcbaba-323b-59bd-3ce8-039d98ed8365 @radekdoulik can you please take a look? I will comment the build legs out with a reference to this issue.
|
The step that installs the certs is added based on |
Yes, as @radical says, the certs step needs to be updated to run in the affected builds. |
Ah I see. I'll put up a subsequent PR to fix that. Thanks! |
While adding a new pipeline for the "extra" platforms (#62564) I've hit an issue with the browser wasm windows build legs:
The build pipeline is: https://dev.azure.com/dnceng/public/_build/results?buildId=1559642&view=logs&jobId=854f6d42-496e-5e8c-a1c9-7f7194a94a83&j=bce77159-c177-5da3-02f5-74ccd320a9d5&t=55fcbaba-323b-59bd-3ce8-039d98ed8365
@radekdoulik can you please take a look? I will comment the build legs out with a reference to this issue.
The text was updated successfully, but these errors were encountered: