On Fri, 2 Jun 2023 20:08:15 GMT, Chris Plummer wrote:
> The following two tests no longer seem to be failing with the virtual thread
> test factory:
>
> com/sun/jdi/RedefineG.java 8285422 generic-all
> com/sun/jdi/RedefineTTYLineNumber.java 8285422 generic-all
>
> They can be removed from the
On Fri, 2 Jun 2023 21:30:46 GMT, Chris Plummer wrote:
> Normally when a virtual thread wrapper is used to run a test, the main thread
> is renamed to "old-m-a-i-n" and the new virtual thread that will act as the
> main thread is named "main". Neither is being done by `ProcessTools.main()`.
> T
On Fri, 2 Jun 2023 20:08:15 GMT, Chris Plummer wrote:
> The following two tests no longer seem to be failing with the virtual thread
> test factory:
>
> com/sun/jdi/RedefineG.java 8285422 generic-all
> com/sun/jdi/RedefineTTYLineNumber.java 8285422 generic-all
>
> They can be removed from the
On Fri, 2 Jun 2023 21:47:47 GMT, Chris Plummer wrote:
> JdbMethodExitTest.java tries to determine the jdb threadID for the "main"
> thread, and then later use it in jdb commands that require a threadID. It
> does this by first having the debuggee execute the following:
>
> System.out.p
On Fri, 2 Jun 2023 21:30:46 GMT, Chris Plummer wrote:
> Normally when a virtual thread wrapper is used to run a test, the main thread
> is renamed to "old-m-a-i-n" and the new virtual thread that will act as the
> main thread is named "main". Neither is being done by `ProcessTools.main()`.
> T
The following two tests no longer seem to be failing with the virtual thread
test factory:
com/sun/jdi/RedefineG.java 8285422 generic-all
com/sun/jdi/RedefineTTYLineNumber.java 8285422 generic-all
They can be removed from the problem list. I also updated a couple of entries
to refer to existing
On Tue, 30 May 2023 22:58:58 GMT, Alex Menkov wrote:
> The change fixes regression from JDK-8299414.
> There is a deadlock between JvmtiVTMSTransitionDisabler and EscapeBarrier
> when virtual threads are in mount/unmount transition:
> EscapeBarrier requests deoptimization which requires thread s
JdbMethodExitTest.java tries to determine the jdb threadID for the "main"
thread, and then later use it in jdb commands that require a threadID. It does
this by first having the debuggee execute the following:
System.out.println("threadid="+Thread.currentThread().getId());
And then late
The com/sun/jdi/JdbXXX tests rely on the jdb "threads" command output to find
the main thread. If it is a virtual thread, it will not be included in the
"threads" output unless the debuggee is run with -Djdk.trackAllThreads, so we
need to make sure to include this option when launching the debug
The com/sun/jdi/JdbXXX tests rely on the jdb "threads" command output to find
the main thread. If it is a virtual thread, it will not be included in the
"threads" output unless the debuggee is run with -Djdk.trackAllThreads, so we
need to make sure to include this option when launching the debug
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>> `-XX:+UnlockExp
On Fri, 2 Jun 2023 19:23:23 GMT, Alex Menkov wrote:
>> Serguei Spitsyn has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains six additional
>> commits
On Fri, 2 Jun 2023 03:44:48 GMT, Serguei Spitsyn wrote:
>> The VM option EnableDynamicAgentLoading was added in JDK 9, default true, to
>> allow deployment to choose whether to allow agents to be loaded/started in
>> the VM. The VM option does the right thing for tools using the Attach API
>>
On Fri, 2 Jun 2023 04:29:16 GMT, Chris Plummer wrote:
>> Virtual threads are always daemon threads, so tests that previously did not
>> explicitly wait for test threads to exit sometimes fail with virtual threads
>> due to the test exiting before the test threads have exited. A join() for
>> e
On Thu, 1 Jun 2023 23:03:47 GMT, Chris Plummer wrote:
> Virtual threads are always daemon threads, so tests that previously did not
> explicitly wait for test threads to exit sometimes fail with virtual threads
> due to the test exiting before the test threads have exited. A join() for
> each
On Fri, 2 Jun 2023 04:29:16 GMT, Chris Plummer wrote:
>> Virtual threads are always daemon threads, so tests that previously did not
>> explicitly wait for test threads to exit sometimes fail with virtual threads
>> due to the test exiting before the test threads have exited. A join() for
>> e
On Fri, 2 Jun 2023 18:24:16 GMT, Y. Srinivas Ramakrishna
wrote:
>> Kelvin Nilsen has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Force PLAB sizes to align on card-table size
>
> src/hotspot/cpu/riscv/gc/shenandoah/c1/shenandoahBarrierSe
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>> `-XX:+UnlockExp
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>> `-XX:+UnlockExp
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>> `-XX:+UnlockExp
On Fri, 2 Jun 2023 04:29:16 GMT, Chris Plummer wrote:
>> Virtual threads are always daemon threads, so tests that previously did not
>> explicitly wait for test threads to exit sometimes fail with virtual threads
>> due to the test exiting before the test threads have exited. A join() for
>> e
This pr is a split off from JDK-8308288: Fix xlc17 clang warnings in shared
code https://github.com/openjdk/jdk/pull/14146
It handles the part in security and servicability.
Compiling on AIX with xlc17 which contains the new clang 15 frontend shows the
following warnings:
src/java.security.jgss
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>> `-XX:+UnlockExp
On Tue, 23 May 2023 09:04:11 GMT, Severin Gehwolf wrote:
>> Please review these test changes which implement automatic testing of
>> container resource updates without JVM restart. Note that this merely tests
>> container detection code handling this case. It doesn't do anything special
>> for
On Mon, 22 May 2023 16:40:40 GMT, Severin Gehwolf wrote:
> Please review these test changes which implement automatic testing of
> container resource updates without JVM restart. Note that this merely tests
> container detection code handling this case. It doesn't do anything special
> for the
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>> `-XX:+UnlockExp
On Tue, 30 May 2023 19:15:38 GMT, Johan Sjölen wrote:
>> A final sweep of Hotspot to remove all re-added NULLs. With only 110 changes
>> I'd appreciate if this was considered trivial.
>
> Johan Sjölen has updated the pull request incrementally with two additional
> commits since the last revisi
27 matches
Mail list logo
