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

circleci: limit resource use to stay within limits #25045

Merged
merged 1 commit into from
Dec 15, 2017
Merged

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Dec 12, 2017

We have 2 vCPUs and 4 GB memory in the container.

@ararslan ararslan added the ci Continuous integration label Dec 12, 2017
@ararslan
Copy link
Member

Looks like Julia isn't picking up those environment variables when they're defined outside of the Docker block. If I'm not mistaken, specifying them outside like that only affects machine builds rather than Docker builds, but I'm not 100% on that.

This is also causing both Circle builds to time out (10 minutes with no output), and x86-64 still gets an EOFError.

@ararslan
Copy link
Member

As an aside, to skip the FreeBSD CI you need [bsd skip]. Travis has never had Travis-specific skipping, and AppVeyor seems to have stopped recognizing any kind of skipping.

@vtjnash vtjnash merged commit 193f763 into master Dec 15, 2017
@vtjnash vtjnash deleted the jn/circle_limits branch December 15, 2017 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants