Skip to content

Remove test that triggers an OutOfMemoryError #10072

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
Oct 23, 2020

Conversation

smarter
Copy link
Member

@smarter smarter commented Oct 22, 2020

This lead to timeouts on the Windows CI, and in any case this test has
nothing to do here: it tests the library, not the compiler, so it should
be a JUnit test in scala-library.

This lead to timeouts on the Windows CI, and in any case this test has
nothing to do here: it tests the library, not the compiler, so it should
be a JUnit test in scala-library.
@som-snytt
Copy link
Contributor

The test is suboptimal, but as written, the failure case was a hang, so nominally it should be tested out-of-process.

Copy link
Contributor

@liufengyun liufengyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@liufengyun liufengyun merged commit 3ea4e0e into scala:master Oct 23, 2020
@liufengyun liufengyun deleted the remove-oom-test branch October 23, 2020 07:37
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