git: openjdk/loom: fibers: 3 new changesets

[duke]

Changeset: 4418e905
Author:    Chris Plummer <chris.plummer at oracle.com>
Date:      2021-09-26 06:36:53 +0000
URL:       https://git.openjdk.java.net/loom/commit/4418e905a59cbc807ff7f4a17746d2495aa60dec

The SunCommandLineLauncher was explicitly passing notifyvthreads=n even though the normal default for the flag (when not specified) is false. This was causing at least one JDI test to fail in vthread mode (probably more).

! src/jdk.jdi/share/classes/com/sun/tools/jdi/SunCommandLineLauncher.java

Changeset: e96e458e
Author:    Chris Plummer <chris.plummer at oracle.com>
Date:      2021-09-26 06:38:27 +0000
URL:       https://git.openjdk.java.net/loom/commit/e96e458e212111c71e6527cb60585a8550db84c5

Add fixme comment to eventually run tests without using enumeratevthreads=y

! test/hotspot/jtreg/vmTestbase/nsk/share/jdi/Binder.java

Changeset: eb361618
Author:    Chris Plummer <chris.plummer at oracle.com>
Date:      2021-09-26 06:42:15 +0000
URL:       https://git.openjdk.java.net/loom/commit/eb361618a677885fb2b987e6a148d9d42c22f047

Initial problems with this test were fixed when the fix for 8273909 was brought over from jdk, but then it immediately broke again with the new support to run all JDI debuggee threads as vthreads. I then fixed this issue with the SunCommandLineLauncher.java change to pass in notifyvthreads=y.

! test/hotspot/jtreg/ProblemList-vthread.txt