Skip to content
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

Closed
safern opened this issue Jan 19, 2022 · 5 comments · Fixed by #64065
Closed

Browser wasm on windows CI builds broken #63987

safern opened this issue Jan 19, 2022 · 5 comments · Fixed by #64065
Labels

Comments

@safern
Copy link
Member

safern commented Jan 19, 2022

While adding a new pipeline for the "extra" platforms (#62564) I've hit an issue with the browser wasm windows build legs:

HEAD is now at f44b841 2.0.23 (#828)
  Error: Downloading URL 'https://storage.googleapis.com/webassembly/emscripten-releases-builds/deps/node-v14.15.5-win-x64.zip': <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123)>
  Warning: Possibly SSL/TLS issue. Update or install Python SSL root certificates (2048-bit or greater) supplied in Python folder or https://pypi.org/project/certifi/ and try again.
  Installation failed!
  Installing SDK 'sdk-releases-upstream-77b065ace39e6ab21446e13f92897f956c80476a-64bit'..
  Installing tool 'node-14.15.5-64bit'..
D:\a\_work\1\s\src\mono\mono.proj(153,5): error MSB3073: The command "git checkout 2.0.23 && powershell -NonInteractive -command "& ./emsdk.ps1 install 2.0.23; Exit $LastExitCode " && powershell -NonInteractive -command "& ./emsdk.ps1 activate 2.0.23; Exit $LastExitCode "" exited with code 1.
##[error]src\mono\mono.proj(153,5): error MSB3073: (NETCORE_ENGINEERING_TELEMETRY=Build) The command "git checkout 2.0.23 && powershell -NonInteractive -command "& ./emsdk.ps1 install 2.0.23; Exit $LastExitCode " && powershell -NonInteractive -command "& ./emsdk.ps1 activate 2.0.23; Exit $LastExitCode "" exited with code 1.

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.

@dotnet-issue-labeler
Copy link

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.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jan 19, 2022
@safern safern added arch-wasm WebAssembly architecture area-Infrastructure-mono labels Jan 19, 2022
@ghost
Copy link

ghost commented Jan 19, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

While adding a new pipeline for the "extra" platforms (#62564) I've hit an issue with the browser wasm windows build legs:

HEAD is now at f44b841 2.0.23 (#828)
  Error: Downloading URL 'https://storage.googleapis.com/webassembly/emscripten-releases-builds/deps/node-v14.15.5-win-x64.zip': <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123)>
  Warning: Possibly SSL/TLS issue. Update or install Python SSL root certificates (2048-bit or greater) supplied in Python folder or https://pypi.org/project/certifi/ and try again.
  Installation failed!
  Installing SDK 'sdk-releases-upstream-77b065ace39e6ab21446e13f92897f956c80476a-64bit'..
  Installing tool 'node-14.15.5-64bit'..
D:\a\_work\1\s\src\mono\mono.proj(153,5): error MSB3073: The command "git checkout 2.0.23 && powershell -NonInteractive -command "& ./emsdk.ps1 install 2.0.23; Exit $LastExitCode " && powershell -NonInteractive -command "& ./emsdk.ps1 activate 2.0.23; Exit $LastExitCode "" exited with code 1.
##[error]src\mono\mono.proj(153,5): error MSB3073: (NETCORE_ENGINEERING_TELEMETRY=Build) The command "git checkout 2.0.23 && powershell -NonInteractive -command "& ./emsdk.ps1 install 2.0.23; Exit $LastExitCode " && powershell -NonInteractive -command "& ./emsdk.ps1 activate 2.0.23; Exit $LastExitCode "" exited with code 1.

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.

Author: safern
Assignees: -
Labels:

arch-wasm, untriaged, area-Infrastructure-mono

Milestone: -

@radical
Copy link
Member

radical commented Jan 19, 2022

The step that installs the certs is added based on nameSuffix containing Windows_wasm. That check would need to be updated.

@radical radical removed the untriaged New issue has not been triaged by the area owner label Jan 19, 2022
@radekdoulik
Copy link
Member

Yes, as @radical says, the certs step needs to be updated to run in the affected builds.

@safern
Copy link
Member Author

safern commented Jan 19, 2022

Ah I see. I'll put up a subsequent PR to fix that. Thanks!

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jan 20, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jan 21, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Feb 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants