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

Travis CI: Remove sudo usage while building #8755

Closed
smitpatel opened this issue Jun 7, 2017 · 1 comment
Closed

Travis CI: Remove sudo usage while building #8755

smitpatel opened this issue Jun 7, 2017 · 1 comment
Assignees
Labels
area-test closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@smitpatel
Copy link
Member

With #8749 , we are moving to sudo: required on travis build.

Investigating into issue while travis fails with

MSBUILD : error MSB4166: Child node "19" exited prematurely. Shutting down. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt.
  1. Trying to reproducing using docker image of travis did not help much. It was able to build. Though it had more than 100% CPU usage and hardly any RAM left from 2GB available memory. Also it did not utilize any swap memory.
  2. Trying to mimic the environment travis have in local Ubuntu VM, it still passes. But when dropping RAM to 512MB, it hangs. MSBuild is certainly having issues with low memory available.

There are few related issues
dotnet/msbuild#2168 - this one talks about high memory usage in MSBuild.

dotnet/msbuild#2164 - is the issue we have filed about travis build.

At present, by enabling sudo which gives us higher machine specs, we have got build passing.
Ideally we should not need sudo usage. We can safely remove it once MSBuild figures out & resolves the underlying issue.

@smitpatel
Copy link
Member Author

2ba1dc0 removed sudo usage for testing.

@smitpatel smitpatel added closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. and removed area-external labels Jun 8, 2017
@smitpatel smitpatel self-assigned this Jun 8, 2017
@smitpatel smitpatel added this to the 2.0.0 milestone Jun 8, 2017
@ajcvickers ajcvickers modified the milestones: 2.0.0-preview2, 2.0.0 Jun 9, 2017
@ajcvickers ajcvickers modified the milestones: 2.0.0-preview2, 2.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Development

No branches or pull requests

2 participants