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

CI failure in "Build Browser wasm Release AllSubsets_Mono" leg #59736

Closed
tarekgh opened this issue Sep 29, 2021 · 3 comments
Closed

CI failure in "Build Browser wasm Release AllSubsets_Mono" leg #59736

tarekgh opened this issue Sep 29, 2021 · 3 comments

Comments

@tarekgh
Copy link
Member

tarekgh commented Sep 29, 2021

https://dev.azure.com/dnceng/public/_build/results?buildId=1391502&view=logs&j=2c1bc6b5-3ed2-590f-6f2c-e4b87c1ec8e3&t=99af3e6b-57ff-5563-f33d-f3cc56be1bd5&l=5666

##[error]Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000  -w /home/cloudtest_azpcontainer f01df44dbb38245987588e5a60e5369c4b5d275f03cfdc0cf2e29100ee42f710 /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.
Finishing: Build product

@dotnet-issue-labeler dotnet-issue-labeler bot added area-Infrastructure-mono untriaged New issue has not been triaged by the area owner labels Sep 29, 2021
@ghost
Copy link

ghost commented Sep 29, 2021

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

https://dev.azure.com/dnceng/public/_build/results?buildId=1391502&view=logs&j=2c1bc6b5-3ed2-590f-6f2c-e4b87c1ec8e3&t=99af3e6b-57ff-5563-f33d-f3cc56be1bd5&l=5666

##[error]Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000  -w /home/cloudtest_azpcontainer f01df44dbb38245987588e5a60e5369c4b5d275f03cfdc0cf2e29100ee42f710 /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.
Finishing: Build product

Author: tarekgh
Assignees: -
Labels:

untriaged, area-Infrastructure-mono

Milestone: -

@steveisok
Copy link
Member

@radical I'm pretty sure this is from one of the libraries that would cause OOM and is no longer an issue. Confirming with you first before closing.

@radical
Copy link
Member

radical commented Jul 5, 2022

Yep, that's correct.

@radical radical closed this as completed Jul 5, 2022
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jul 5, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Aug 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants