Skip to content

Conversation

@som-snytt
Copy link
Contributor

This test relies on testing the message of a
ClassCastException, but if the method that throws
it is JIT-compiled, the message is null. This was
observed when an unrelated test was added to the
in-process suite which over-exercised the method
and caused it to be compiled.

Adding .javaopts causes the test to run out-of-
process, and the supplied option also turns off
compilation for the method in question.

This test relies on testing the message of a
ClassCastException, but if the method that throws
it is JIT-compiled, the message is null. This was
observed when an unrelated test was added to the
in-process suite which over-exercised the method
and caused it to be compiled.

Adding `.javaopts` causes the test to run out-of-
process, and the supplied option also turns off
compilation for the method in question.
@som-snytt
Copy link
Contributor Author

som-snytt commented Mar 6, 2019

On second thought, it would be nicer not to rely on -XX; possibly an empty .javaopts is enough; but no, it must be non-empty, albeit any benign option would work.

@SethTisue
Copy link
Member

😍

@SethTisue SethTisue modified the milestones: 2.13.1, 2.13.0-RC1 Mar 6, 2019
@SethTisue
Copy link
Member

giving this a workout now over at #7817

@SethTisue
Copy link
Member

seriously, I'm so glad you figured this out

@SethTisue SethTisue merged commit e126138 into scala:2.13.x Mar 6, 2019
@som-snytt som-snytt deleted the issue/t6411-failure branch March 6, 2019 15:56
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