Skip to content

partest: run tests with -Xms64M -Xmx1024M instead of JVM defaults #1076

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

Merged
merged 1 commit into from
Feb 12, 2016

Conversation

smarter
Copy link
Member

@smarter smarter commented Feb 11, 2016

This is the same settings that scalac uses, this should help use avoid
using too much memory (the default on 64 bits Linux seems to be
-Xms248M -Xmx3938M).

Review by @DarkDimius

@smarter smarter force-pushed the fix/run-tests-memory branch from 9988c09 to ef60a94 Compare February 11, 2016 12:38
This is the same settings that scalac uses, this should help use avoid
using too much memory (the default on 64 bits Linux seems to be
-Xms248M -Xmx3938M).
@smarter smarter force-pushed the fix/run-tests-memory branch from ef60a94 to d57fd8b Compare February 11, 2016 12:40
@DarkDimius
Copy link
Contributor

LGTM

DarkDimius added a commit that referenced this pull request Feb 12, 2016
partest: run tests with -Xms64M -Xmx1024M instead of JVM defaults
@DarkDimius DarkDimius merged commit d04e704 into scala:master Feb 12, 2016
smarter added a commit to dotty-staging/dotty that referenced this pull request Mar 1, 2016
This should be safe now that run tests do not take so much memory
anymore (cf scala#1033 and  scala#1076).

It would be even better if we could figure out why we're using so much
memory, but that's less important than avoiding spurious test failures.
@allanrenucci allanrenucci deleted the fix/run-tests-memory branch December 14, 2017 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants