RFR: 8254042: gtest/GTestWrapper.java failed os.test_random

[Thomas Stüfe]

On Thu, Nov 26, 2020 at 12:51 AM Kim Barrett <kim.barrett at oracle.com> wrote:

> > On Nov 25, 2020, at 12:25 AM, Thomas Stuefe <stuefe at openjdk.java.net>
> wrote:
> > Why is someone concurrently changing the seed? I thought "TEST" tests do
> not start the VM? Or is it that some earlier test already did?
>
> I was surprised by this too.
>
> "TEST" tests and "TEST_VM" tests are collected in a single list and
> run sequentially.  The first "TEST_VM" test that gets run by that will
> trigger VM initialization, and all the remaining tests (whether "TEST"
> or "TEST_VM") get run in the resulting context.
>
> I don't much like that behavior.
>
>
I don't either. One of the problems I keep encountering is that I use TEST
only to later see that I accidentally used VM infrastructure; but you only
notice when executing the test in a different order.

googletests has all these nice options, eg --gtest_shuffle. Maybe we should
randomize the execution order of these tests to shake loose these errors.

Cheers, Thome