From djelinski1 at gmail.com  Thu Oct  2 18:40:39 2025
From: djelinski1 at gmail.com (=?UTF-8?Q?Daniel_Jeli=C5=84ski?=)
Date: Thu, 2 Oct 2025 20:40:39 +0200
Subject: How to pass javatest.maxOutputSize to make test?
In-Reply-To: <CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com>
References: <CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com>
Message-ID: <CAMrH03KWJQytzmOOeTgLQ+t3bH9+iLoKFzNvdkL8HEO=r5vkAg@mail.gmail.com>

Hi Pavel,
JTREG=MAX_OUTPUT=999999999 is what you're looking for.
Cheers,
Daniel

czw., 2 pa? 2025 o 20:37 Pavel Rappo <pavel.rappo at gmail.com> napisa?(a):
>
> Hello,
>
> This has been probably asked multiple times, but I cannot quickly find
> anything. I'm running a set of tests as follows:
>
>     make test TEST="test/jdk/java/time/"
>
> If a test fails, sometimes I get this output:
>
>     ...
>     Output overflow:
>     JT Harness has limited the test output to the text
>     at the beginning and the end, so that you can see how the
>     test began, and how it completed.
>
>     If you need to see more of the output from the test,
>     set the system property javatest.maxOutputSize to a higher
>     value. The current value is 100000
>     ...
>
> I know there's even an FAQ item [^1] addressing this property. But I
> cannot easily see how to translate jtreg syntax to that of `make
> test`. Whatever I tried hasn't worked. As a workaround, I added this
> to the nearest TEST.properties:
>
>     maxOutputSize=99999999
>
> [^1]: https://openjdk.org/jtreg/faq.html#how-to-set-javatest.maxOutputSize

From pavel.rappo at gmail.com  Thu Oct  2 17:09:29 2025
From: pavel.rappo at gmail.com (Pavel Rappo)
Date: Thu, 2 Oct 2025 18:09:29 +0100
Subject: How to pass javatest.maxOutputSize to make test?
Message-ID: <CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com>

Hello,

This has been probably asked multiple times, but I cannot quickly find
anything. I'm running a set of tests as follows:

    make test TEST="test/jdk/java/time/"

If a test fails, sometimes I get this output:

    ...
    Output overflow:
    JT Harness has limited the test output to the text
    at the beginning and the end, so that you can see how the
    test began, and how it completed.

    If you need to see more of the output from the test,
    set the system property javatest.maxOutputSize to a higher
    value. The current value is 100000
    ...

I know there's even an FAQ item [^1] addressing this property. But I
cannot easily see how to translate jtreg syntax to that of `make
test`. Whatever I tried hasn't worked. As a workaround, I added this
to the nearest TEST.properties:

    maxOutputSize=99999999

[^1]: https://openjdk.org/jtreg/faq.html#how-to-set-javatest.maxOutputSize

From pavel.rappo at gmail.com  Thu Oct  2 19:00:21 2025
From: pavel.rappo at gmail.com (Pavel Rappo)
Date: Thu, 2 Oct 2025 20:00:21 +0100
Subject: How to pass javatest.maxOutputSize to make test?
In-Reply-To: <CAMrH03KWJQytzmOOeTgLQ+t3bH9+iLoKFzNvdkL8HEO=r5vkAg@mail.gmail.com>
References: <CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com>
 <CAMrH03KWJQytzmOOeTgLQ+t3bH9+iLoKFzNvdkL8HEO=r5vkAg@mail.gmail.com>
Message-ID: <CAChcVum8aakWmc5rOk2Y1fX=Ci+j0G0rf0zK40nVh_i4F5y6+w@mail.gmail.com>

It works, thanks!

I found a JBS issue that mentions this:
https://bugs.openjdk.org/browse/JDK-8220639. I wonder if this
parameter can be mentioned in these documents, so it could be easily
found by the next person:

  - https://openjdk.org/groups/build/doc/testing.html
  - https://github.com/openjdk/jdk/blob/master/doc/testing.md
  - https://openjdk.org/guide/#testing-the-jdk

On Thu, Oct 2, 2025 at 7:40?PM Daniel Jeli?ski <djelinski1 at gmail.com> wrote:
>
> Hi Pavel,
> JTREG=MAX_OUTPUT=999999999 is what you're looking for.
> Cheers,
> Daniel
>
> czw., 2 pa? 2025 o 20:37 Pavel Rappo <pavel.rappo at gmail.com> napisa?(a):
> >
> > Hello,
> >
> > This has been probably asked multiple times, but I cannot quickly find
> > anything. I'm running a set of tests as follows:
> >
> >     make test TEST="test/jdk/java/time/"
> >
> > If a test fails, sometimes I get this output:
> >
> >     ...
> >     Output overflow:
> >     JT Harness has limited the test output to the text
> >     at the beginning and the end, so that you can see how the
> >     test began, and how it completed.
> >
> >     If you need to see more of the output from the test,
> >     set the system property javatest.maxOutputSize to a higher
> >     value. The current value is 100000
> >     ...
> >
> > I know there's even an FAQ item [^1] addressing this property. But I
> > cannot easily see how to translate jtreg syntax to that of `make
> > test`. Whatever I tried hasn't worked. As a workaround, I added this
> > to the nearest TEST.properties:
> >
> >     maxOutputSize=99999999
> >
> > [^1]: https://openjdk.org/jtreg/faq.html#how-to-set-javatest.maxOutputSize

From alan.bateman at oracle.com  Fri Oct  3 05:55:55 2025
From: alan.bateman at oracle.com (Alan Bateman)
Date: Fri, 3 Oct 2025 06:55:55 +0100
Subject: How to pass javatest.maxOutputSize to make test?
In-Reply-To: <CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com>
References: <CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com>
Message-ID: <87dd3b16-df02-413d-b3ca-d7190a6d67cb@oracle.com>



On 02/10/2025 18:09, Pavel Rappo wrote:
> Hello,
>
> This has been probably asked multiple times, but I cannot quickly find
> anything. I'm running a set of tests as follows:
>
>      make test TEST="test/jdk/java/time/"
>
> If a test fails, sometimes I get this output:
>
>      ...
>      Output overflow:
>      JT Harness has limited the test output to the text
>      at the beginning and the end, so that you can see how the
>      test began, and how it completed.
>
>      If you need to see more of the output from the test,
>      set the system property javatest.maxOutputSize to a higher
>      value. The current value is 100000
>      ...
>
At some point I think we need to think again about having maxOutputSize 
set to a very large value in the TEST.ROOT for least the test/jdk test. 
There are many parameterized tests that result in lot of output but it 
very important output for diagnosing failures, even the "STARTED" and 
"SUCCESSFUL" messages for JUnit tests as they give you the execution 
time for specific tests when trying to diagnose timeouts and slow downs. 
Right now, we have TEST.properties in some areas overriding the value of 
maxOutputSize because of this issue. So while it might mean a test run 
retains large .jtr that is truncated today, it seems a reasonable trade 
off when comparing to the frustrating of finding which test has failed.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jtreg-dev/attachments/20251003/6707a567/attachment-0001.htm>

From cstein at openjdk.org  Wed Oct  8 14:11:12 2025
From: cstein at openjdk.org (Christian Stein)
Date: Wed, 8 Oct 2025 14:11:12 GMT
Subject: RFR: 7904094: Release jtreg 8.1
Message-ID: <wNit1O_lTeCMEagJ6DvDULSZ1OfEJPUSED5BFXfJkuk=.478b2d15-d4f9-4717-a02f-1785e9964d19@github.com>

Please review this change to update the `CHANGELOG.md` file to include a section about jtreg 8.1

This change also increases the working number to 8.2

-------------

Commit messages:
 - Start with development of jtreg 8.2
 - 7904094: Release jtreg 8.1

Changes: https://git.openjdk.org/jtreg/pull/294/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=294&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904094
  Stats: 15 lines in 2 files changed: 13 ins; 0 del; 2 mod
  Patch: https://git.openjdk.org/jtreg/pull/294.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/294/head:pull/294

PR: https://git.openjdk.org/jtreg/pull/294

From jpai at openjdk.org  Wed Oct  8 14:11:13 2025
From: jpai at openjdk.org (Jaikiran Pai)
Date: Wed, 8 Oct 2025 14:11:13 GMT
Subject: RFR: 7904094: Release jtreg 8.1
In-Reply-To: <wNit1O_lTeCMEagJ6DvDULSZ1OfEJPUSED5BFXfJkuk=.478b2d15-d4f9-4717-a02f-1785e9964d19@github.com>
References: <wNit1O_lTeCMEagJ6DvDULSZ1OfEJPUSED5BFXfJkuk=.478b2d15-d4f9-4717-a02f-1785e9964d19@github.com>
Message-ID: <fhfgBmiI_uOmeSdX9AYfXHuT5WAG673zx_v7yvIt0uY=.08554bd6-334d-4b45-a872-7d4f2e1fbc80@github.com>

On Wed, 8 Oct 2025 13:59:31 GMT, Christian Stein <cstein at openjdk.org> wrote:

> Please review this change to update the `CHANGELOG.md` file to include a section about jtreg 8.1
> 
> This change also increases the working number to 8.2

Looks good to me

-------------

Marked as reviewed by jpai (Reviewer).

PR Review: https://git.openjdk.org/jtreg/pull/294#pullrequestreview-3314994211

From cstein at openjdk.org  Wed Oct  8 14:51:31 2025
From: cstein at openjdk.org (Christian Stein)
Date: Wed, 8 Oct 2025 14:51:31 GMT
Subject: Integrated: 7904094: Release jtreg 8.1
In-Reply-To: <wNit1O_lTeCMEagJ6DvDULSZ1OfEJPUSED5BFXfJkuk=.478b2d15-d4f9-4717-a02f-1785e9964d19@github.com>
References: <wNit1O_lTeCMEagJ6DvDULSZ1OfEJPUSED5BFXfJkuk=.478b2d15-d4f9-4717-a02f-1785e9964d19@github.com>
Message-ID: <EmxbTNbYP_rZP-3H058FLA9tvkoj5tOxrj_1Fvk5T9g=.3b84af31-bf99-47ca-af05-533bbef5ce8d@github.com>

On Wed, 8 Oct 2025 13:59:31 GMT, Christian Stein <cstein at openjdk.org> wrote:

> Please review this change to update the `CHANGELOG.md` file to include a section about jtreg 8.1
> 
> This change also increases the working number to 8.2

This pull request has now been integrated.

Changeset: 34ccc66e
Author:    Christian Stein <cstein at openjdk.org>
URL:       https://git.openjdk.org/jtreg/commit/34ccc66ec89651637811678a17d3f810b4ac0780
Stats:     15 lines in 2 files changed: 13 ins; 0 del; 2 mod

7904094: Release jtreg 8.1

Reviewed-by: jpai

-------------

PR: https://git.openjdk.org/jtreg/pull/294

From vpetko at openjdk.org  Wed Oct 22 02:43:16 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Wed, 22 Oct 2025 02:43:16 GMT
Subject: RFR: 7904101: intermittent failure in StreamsTest.agentvm.ok
Message-ID: <QbzFya1bkj9PVpOVTW7jITjrSa_aKqR6hdlZYb9nniY=.a9ad023a-0829-4b43-8fc7-dd9f8a867d86@github.com>

FileDescriptor test intermittently fails because the agent's process output capture lacks synchronisation. 

This PR fixes the issue:
- Agent VM prints the "process output separator" to stderr and stdout before and after action
- The main vm uses the marker to stop reading the stream for the current test result section (or a general agent log)
- The main vm restarts reading the log after updating the test section (or clearing it) until the next marker or the process is shut down.

Alternative:
 -Disable the test and make no assumptions about contents of the agent vm process output.

Testing: tier1 and tier2 tests on mainline jdk (Ubuntu Linux) in agentvm mode.


make test TEST=":tier1 :tier2" JTREG="TEST_MODE=agentvm"

....

==============================
Test summary
==============================
   TEST                                              TOTAL  PASS  FAIL ERROR  SKIP   
   jtreg:test/hotspot/jtreg:tier1                     3124  2837     0     0   287   
   jtreg:test/jdk:tier1                               2519  2480     0     0    39   
   jtreg:test/langtools:tier1                         4670  4660     0     0    10   
   jtreg:test/jaxp:tier1                                 0     0     0     0     0   
   jtreg:test/lib-test:tier1                            38    38     0     0     0   
   jtreg:test/hotspot/jtreg:tier2                      960   913     0     0    47   
>> jtreg:test/jdk:tier2                               4455  4220     1     0   234 <<
   jtreg:test/langtools:tier2                           14    12     0     0     2   
   jtreg:test/jaxp:tier2                               517   516     0     0     1   
   jtreg:test/docs:tier2                                 4     0     0     0     4   
==============================
TEST FAILURE


Unrelated failure: test/jdk/java/nio/channels/DatagramChannel/SendReceiveMaxSize.java




---------System.out:(98/7409)----------
Seed from RandomFactory = 7590698091695474155L
[15:02:42.244] config SendReceiveMaxSize.setUp(): success [0ms]
[15:02:42.272] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x00000000450736f8 at 8d234b9, 65507, /10.201.67.1): success [7ms]
[15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045073920 at 449629ff, 65507, /10.201.67.1): success [0ms]
[15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045078000 at 2b071f3f, 65527, java.net.Inet6Address at 22212892): success [0ms]
[15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045078228 at 298b6c94, 65527, java.net.Inet6Address at 22212892): success [0ms]
testSendReceiveMaxSize: sender: /10.201.67.1:50670 -> receiver: /10.201.67.1:49236
sendBuf:    java.nio.HeapByteBuffer[pos=0 lim=65507 cap=65507]
receiveBuf: java.nio.HeapByteBuffer[pos=0 lim=65507 cap=65507]
sendBuf:    java.nio.HeapByteBuffer[pos=0 lim=65506 cap=65506]
receiveBuf: java.nio.HeapByteBuffer[pos=0 lim=65506 cap=65506]
[15:02:42.286] test SendReceiveMaxSize.testSendReceiveMaxSize(SendReceiveMaxSize$$Lambda/0x00000000450736f8 at 8d234b9, 65507, /10.201.67.1): success [11ms]
testSendReceiveMaxSize: sender: /10.201.67.1:48168 -> receiver: /10.201.67.1:52274
sendBuf:    java.nio.HeapByteBuffer[pos=0 lim=65507 cap=65507]
receiveBuf: java.nio.HeapByteBuffer[pos=0 lim=65507 cap=65507]
sendBuf:    java.nio.HeapByteBuffer[pos=0 lim=65506 cap=65506]
receiveBuf: java.nio.HeapByteBuffer[pos=0 lim=65506 cap=65506]
[15:02:42.288] test SendReceiveMaxSize.testSendReceiveMaxSize(SendReceiveMaxSize$$Lambda/0x0000000045073920 at 449629ff, 65507, /10.201.67.1): success [2ms]
testSendReceiveMaxSize: sender: /[fe80:0:0:0:fc54:ff:fe24:9197%17]:46562 -> receiver: /[fe80:0:0:0:fc54:ff:fe24:9197%17]:58635
[15:02:42.289] test SendReceiveMaxSize.testSendReceiveMaxSize(SendReceiveMaxSize$$Lambda/0x0000000045078000 at 2b071f3f, 65527, java.net.Inet6Address at 8959069): failure [1ms]
java.net.SocketException: Message too long
	at java.base/sun.nio.ch.DatagramChannelImpl.send0(Native Method)
	at java.base/sun.nio.ch.DatagramChannelImpl.sendFromNativeBuffer(DatagramChannelImpl.java:914)
	at java.base/sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:886)
	at java.base/sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:798)
	at SendReceiveMaxSize.testSendReceiveMaxSize(SendReceiveMaxSize.java:155)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
	at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:599)
	at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:174)
	at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
	at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822)
	at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1604)
	at org.testng.TestRunner.privateRun(TestRunner.java:764)
	at org.testng.TestRunner.run(TestRunner.java:585)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
	at org.testng.SuiteRunner.run(SuiteRunner.java:286)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1218)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
	at org.testng.TestNG.runSuites(TestNG.java:1069)
	at org.testng.TestNG.run(TestNG.java:1037)
	at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:109)
	at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:65)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1474)
testSendReceiveMaxSize: sender: /[fe80:0:0:0:fc54:ff:fe24:9197%17]:39368 -> receiver: /[fe80:0:0:0:fc54:ff:fe24:9197%17]:38228
[15:02:42.291] test SendReceiveMaxSize.testSendReceiveMaxSize(SendReceiveMaxSize$$Lambda/0x0000000045078228 at 298b6c94, 65527, java.net.Inet6Address at 8959069): failure [0ms]
java.net.SocketException: Message too long
	at java.base/sun.nio.ch.DatagramChannelImpl.send0(Native Method)
	at java.base/sun.nio.ch.DatagramChannelImpl.sendFromNativeBuffer(DatagramChannelImpl.java:914)
	at java.base/sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:886)
	at java.base/sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:798)
	at SendReceiveMaxSize.testSendReceiveMaxSize(SendReceiveMaxSize.java:155)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
	at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:599)
	at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:174)
	at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
	at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822)
	at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1604)
	at org.testng.TestRunner.privateRun(TestRunner.java:764)
	at org.testng.TestRunner.run(TestRunner.java:585)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
	at org.testng.SuiteRunner.run(SuiteRunner.java:286)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1218)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
	at org.testng.TestNG.runSuites(TestNG.java:1069)
	at org.testng.TestNG.run(TestNG.java:1037)
	at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:109)
	at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:65)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1474)

===============================================
java/nio/channels/DatagramChannel/SendReceiveMaxSize.java
Total tests run: 8, Passes: 6, Failures: 2, Skips: 0
===============================================

-------------

Commit messages:
 - feat: synchronize agent's stdout/stderr logging

Changes: https://git.openjdk.org/jtreg/pull/295/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=295&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904101
  Stats: 219 lines in 3 files changed: 180 ins; 29 del; 10 mod
  Patch: https://git.openjdk.org/jtreg/pull/295.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/295/head:pull/295

PR: https://git.openjdk.org/jtreg/pull/295

From vpetko at openjdk.org  Wed Oct 22 05:16:57 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Wed, 22 Oct 2025 05:16:57 GMT
Subject: RFR: 7904101: intermittent failure in StreamsTest.agentvm.ok [v2]
In-Reply-To: <QbzFya1bkj9PVpOVTW7jITjrSa_aKqR6hdlZYb9nniY=.a9ad023a-0829-4b43-8fc7-dd9f8a867d86@github.com>
References: <QbzFya1bkj9PVpOVTW7jITjrSa_aKqR6hdlZYb9nniY=.a9ad023a-0829-4b43-8fc7-dd9f8a867d86@github.com>
Message-ID: <bTduJf7gdg_Ct9OCQfXfzGTHcLZgOGH2XnqzYy8pZfI=.9b643d38-2cab-45fd-9801-c2068feff776@github.com>

> FileDescriptor test intermittently fails because the agent's process output capture lacks synchronisation. 
> 
> This PR fixes the issue:
> - Agent VM prints the "process output separator" to stderr and stdout before and after action
> - The main vm uses the marker to stop reading the stream for the current test result section (or a general agent log)
> - The main vm restarts reading the log after updating the test section (or clearing it) until the next marker or the process is shut down.
> 
> Alternative:
>  -Disable the test and make no assumptions about contents of the agent vm process output.
> 
> Testing: tier1 and tier2 tests on mainline jdk (Ubuntu Linux) in agentvm mode.
> 
> 
> make test TEST=":tier1 :tier2" JTREG="TEST_MODE=agentvm"
> 
> ....
> 
> ==============================
> Test summary
> ==============================
>    TEST                                              TOTAL  PASS  FAIL ERROR  SKIP   
>    jtreg:test/hotspot/jtreg:tier1                     3124  2837     0     0   287   
>    jtreg:test/jdk:tier1                               2519  2480     0     0    39   
>    jtreg:test/langtools:tier1                         4670  4660     0     0    10   
>    jtreg:test/jaxp:tier1                                 0     0     0     0     0   
>    jtreg:test/lib-test:tier1                            38    38     0     0     0   
>    jtreg:test/hotspot/jtreg:tier2                      960   913     0     0    47   
>>> jtreg:test/jdk:tier2                               4455  4220     1     0   234 <<
>    jtreg:test/langtools:tier2                           14    12     0     0     2   
>    jtreg:test/jaxp:tier2                               517   516     0     0     1   
>    jtreg:test/docs:tier2                                 4     0     0     0     4   
> ==============================
> TEST FAILURE
> 
> 
> Unrelated failure: test/jdk/java/nio/channels/DatagramChannel/SendReceiveMaxSize.java
> 
> 
> 
> 
> ---------System.out:(98/7409)----------
> Seed from RandomFactory = 7590698091695474155L
> [15:02:42.244] config SendReceiveMaxSize.setUp(): success [0ms]
> [15:02:42.272] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x00000000450736f8 at 8d234b9, 65507, /10.201.67.1): success [7ms]
> [15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045073920 at 449629ff, 65507, /10.201.67.1): success [0ms]
> [15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045078000 at 2b071f3f, 65527, java.net.Inet6Address at 22212892): success [0ms]
> [15:0...

Vladimir Petko has refreshed the contents of this pull request, and previous commits have been removed. The incremental views will show differences compared to the previous content of the PR. The pull request contains two new commits since the last revision:

 - fix: always call stopLogging()
 - feat: synchronize agent's stdout/stderr logging
   
   How it works:
    - The agent vm emits separator text before and after the text.
    - The main vm send the action and waits for the separator text line from
      the agent vm.
    - After the result have been read by the main vm it expects another separator
      text line. After consuming the line it redirects output to the agent log.
   
   Edge cases:
    - Timeouts and Agent VM crashes:
      - The main vm's stdout and stderr tasks will exit due to the
        closed stream. The main vm is supposed to dispose the failed agent.

-------------

Changes:
  - all: https://git.openjdk.org/jtreg/pull/295/files
  - new: https://git.openjdk.org/jtreg/pull/295/files/49d53afa..1b37e559

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jtreg&pr=295&range=01
 - incr: https://webrevs.openjdk.org/?repo=jtreg&pr=295&range=00-01

  Stats: 6 lines in 1 file changed: 0 ins; 2 del; 4 mod
  Patch: https://git.openjdk.org/jtreg/pull/295.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/295/head:pull/295

PR: https://git.openjdk.org/jtreg/pull/295

From vpetko at openjdk.org  Fri Oct 24 01:36:35 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Fri, 24 Oct 2025 01:36:35 GMT
Subject: RFR: 7904101: intermittent failure in StreamsTest.agentvm.ok [v2]
In-Reply-To: <bTduJf7gdg_Ct9OCQfXfzGTHcLZgOGH2XnqzYy8pZfI=.9b643d38-2cab-45fd-9801-c2068feff776@github.com>
References: <QbzFya1bkj9PVpOVTW7jITjrSa_aKqR6hdlZYb9nniY=.a9ad023a-0829-4b43-8fc7-dd9f8a867d86@github.com>
 <bTduJf7gdg_Ct9OCQfXfzGTHcLZgOGH2XnqzYy8pZfI=.9b643d38-2cab-45fd-9801-c2068feff776@github.com>
Message-ID: <tPCgwPQfyhgcyEve8Ez-IGNaVlPKi_D8d1ghslvYibo=.ad5bf64a-e8ae-423b-bb16-98c16a2bcddc@github.com>

On Wed, 22 Oct 2025 05:16:57 GMT, Vladimir Petko <vpetko at openjdk.org> wrote:

>> FileDescriptor test intermittently fails because the agent's process output capture lacks synchronisation. 
>> 
>> This PR fixes the issue:
>> - Agent VM prints the "process output separator" to stderr and stdout before and after action
>> - The main vm uses the marker to stop reading the stream for the current test result section (or a general agent log)
>> - The main vm restarts reading the log after updating the test section (or clearing it) until the next marker or the process is shut down.
>> 
>> Alternative:
>>  -Disable the test and make no assumptions about contents of the agent vm process output.
>> 
>> Testing: tier1 and tier2 tests on mainline jdk (Ubuntu Linux) in agentvm mode.
>> 
>> 
>> make test TEST=":tier1 :tier2" JTREG="TEST_MODE=agentvm"
>> 
>> ....
>> 
>> ==============================
>> Test summary
>> ==============================
>>    TEST                                              TOTAL  PASS  FAIL ERROR  SKIP   
>>    jtreg:test/hotspot/jtreg:tier1                     3124  2837     0     0   287   
>>    jtreg:test/jdk:tier1                               2519  2480     0     0    39   
>>    jtreg:test/langtools:tier1                         4670  4660     0     0    10   
>>    jtreg:test/jaxp:tier1                                 0     0     0     0     0   
>>    jtreg:test/lib-test:tier1                            38    38     0     0     0   
>>    jtreg:test/hotspot/jtreg:tier2                      960   913     0     0    47   
>>>> jtreg:test/jdk:tier2                               4455  4220     1     0   234 <<
>>    jtreg:test/langtools:tier2                           14    12     0     0     2   
>>    jtreg:test/jaxp:tier2                               517   516     0     0     1   
>>    jtreg:test/docs:tier2                                 4     0     0     0     4   
>> ==============================
>> TEST FAILURE
>> 
>> 
>> Unrelated failure: test/jdk/java/nio/channels/DatagramChannel/SendReceiveMaxSize.java
>> 
>> 
>> 
>> 
>> ---------System.out:(98/7409)----------
>> Seed from RandomFactory = 7590698091695474155L
>> [15:02:42.244] config SendReceiveMaxSize.setUp(): success [0ms]
>> [15:02:42.272] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x00000000450736f8 at 8d234b9, 65507, /10.201.67.1): success [7ms]
>> [15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045073920 at 449629ff, 65507, /10.201.67.1): success [0ms]
>> [15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lamb...
>
> Vladimir Petko has refreshed the contents of this pull request, and previous commits have been removed. The incremental views will show differences compared to the previous content of the PR. The pull request contains two new commits since the last revision:
> 
>  - fix: always call stopLogging()
>  - feat: synchronize agent's stdout/stderr logging
>    
>    How it works:
>     - The agent vm emits separator text before and after the text.
>     - The main vm send the action and waits for the separator text line from
>       the agent vm.
>     - After the result have been read by the main vm it expects another separator
>       text line. After consuming the line it redirects output to the agent log.
>    
>    Edge cases:
>     - Timeouts and Agent VM crashes:
>       - The main vm's stdout and stderr tasks will exit due to the
>         closed stream. The main vm is supposed to dispose the failed agent.

Still getting intermittent failure in StreamsTest. moving to draft.

-------------

PR Comment: https://git.openjdk.org/jtreg/pull/295#issuecomment-3440292558

From vpetko at openjdk.org  Mon Oct 27 22:00:06 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Mon, 27 Oct 2025 22:00:06 GMT
Subject: RFR: 7904101: intermittent failure in StreamsTest.agentvm.ok [v3]
In-Reply-To: <QbzFya1bkj9PVpOVTW7jITjrSa_aKqR6hdlZYb9nniY=.a9ad023a-0829-4b43-8fc7-dd9f8a867d86@github.com>
References: <QbzFya1bkj9PVpOVTW7jITjrSa_aKqR6hdlZYb9nniY=.a9ad023a-0829-4b43-8fc7-dd9f8a867d86@github.com>
Message-ID: <-1mS9h0WdPH0_kP6iNltA57oDfdmDUn2EsSTJeWSi_U=.58e1bb75-0e71-46fd-b6e6-0fd4052e1d6c@github.com>

> FileDescriptor test intermittently fails because the agent's process output capture lacks synchronisation. 
> 
> This PR fixes the issue:
> - Agent VM prints the "process output separator" to stderr and stdout before and after action
> - The main vm uses the marker to stop reading the stream for the current test result section (or a general agent log)
> - The main vm restarts reading the log after updating the test section (or clearing it) until the next marker or the process is shut down.
> 
> Alternative:
>  -Disable the test and make no assumptions about contents of the agent vm process output.
> 
> Testing: tier1 and tier2 tests on mainline jdk (Ubuntu Linux) in agentvm mode.
> 
> 
> make test TEST=":tier1 :tier2" JTREG="TEST_MODE=agentvm"
> 
> ....
> 
> ==============================
> Test summary
> ==============================
>    TEST                                              TOTAL  PASS  FAIL ERROR  SKIP   
>    jtreg:test/hotspot/jtreg:tier1                     3124  2837     0     0   287   
>    jtreg:test/jdk:tier1                               2519  2480     0     0    39   
>    jtreg:test/langtools:tier1                         4670  4660     0     0    10   
>    jtreg:test/jaxp:tier1                                 0     0     0     0     0   
>    jtreg:test/lib-test:tier1                            38    38     0     0     0   
>    jtreg:test/hotspot/jtreg:tier2                      960   913     0     0    47   
>>> jtreg:test/jdk:tier2                               4455  4220     1     0   234 <<
>    jtreg:test/langtools:tier2                           14    12     0     0     2   
>    jtreg:test/jaxp:tier2                               517   516     0     0     1   
>    jtreg:test/docs:tier2                                 4     0     0     0     4   
> ==============================
> TEST FAILURE
> 
> 
> Unrelated failure: test/jdk/java/nio/channels/DatagramChannel/SendReceiveMaxSize.java
> 
> 
> 
> 
> ---------System.out:(98/7409)----------
> Seed from RandomFactory = 7590698091695474155L
> [15:02:42.244] config SendReceiveMaxSize.setUp(): success [0ms]
> [15:02:42.272] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x00000000450736f8 at 8d234b9, 65507, /10.201.67.1): success [7ms]
> [15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045073920 at 449629ff, 65507, /10.201.67.1): success [0ms]
> [15:02:42.273] test SendReceiveMaxSize.testGetOption(SendReceiveMaxSize$$Lambda/0x0000000045078000 at 2b071f3f, 65527, java.net.Inet6Address at 22212892): success [0ms]
> [15:0...

Vladimir Petko has updated the pull request incrementally with four additional commits since the last revision:

 - fix: create sections in the main thread
 - chore: propagate timeouts and exceptions
 - fix: do not synchronize section output
 - fix: allow marker to appear at the end of the line

-------------

Changes:
  - all: https://git.openjdk.org/jtreg/pull/295/files
  - new: https://git.openjdk.org/jtreg/pull/295/files/1b37e559..541b71ec

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jtreg&pr=295&range=02
 - incr: https://webrevs.openjdk.org/?repo=jtreg&pr=295&range=01-02

  Stats: 71 lines in 2 files changed: 29 ins; 19 del; 23 mod
  Patch: https://git.openjdk.org/jtreg/pull/295.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/295/head:pull/295

PR: https://git.openjdk.org/jtreg/pull/295

From vpetko at openjdk.org  Tue Oct 28 04:13:48 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Tue, 28 Oct 2025 04:13:48 GMT
Subject: RFR: 7904106: TestNativePath: intermittent test failures due to
 different test targets using same work dir
Message-ID: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>

Both agentvm and othervm targets use the same work path `$(BUILDTESTDIR)/nativepath.othervm/work`. This causes intermittent test failures when the tests are run in parallel. 

---------
### Progress
- [ ] Change must be properly reviewed (1 review required, with at least 1 [Reviewer](https://openjdk.org/bylaws#reviewer))
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue

### Error
&nbsp;?? The pull request body must not be empty.



### Reviewing
<details><summary>Using <code>git</code></summary>

Checkout this PR locally: \
`$ git fetch https://git.openjdk.org/jtreg.git pull/298/head:pull/298` \
`$ git checkout pull/298`

Update a local copy of the PR: \
`$ git checkout pull/298` \
`$ git pull https://git.openjdk.org/jtreg.git pull/298/head`

</details>
<details><summary>Using Skara CLI tools</summary>

Checkout this PR locally: \
`$ git pr checkout 298`

View PR using the GUI difftool: \
`$ git pr show -t 298`

</details>
<details><summary>Using diff file</summary>

Download this PR as a diff file: \
<a href="https://git.openjdk.org/jtreg/pull/298.diff">https://git.openjdk.org/jtreg/pull/298.diff</a>

</details>

-------------

Commit messages:
 - fix: use unique test output paths

Changes: https://git.openjdk.org/jtreg/pull/298/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=298&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904106
  Stats: 19 lines in 1 file changed: 0 ins; 1 del; 18 mod
  Patch: https://git.openjdk.org/jtreg/pull/298.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/298/head:pull/298

PR: https://git.openjdk.org/jtreg/pull/298

From vpetko at openjdk.org  Tue Oct 28 04:13:57 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Tue, 28 Oct 2025 04:13:57 GMT
Subject: RFR: 7904107: AgentOut.othervm.ok should not access
 $(BUILDTESTDIR)/AgentOut.agentvm
Message-ID: <cBCzo8OLvIMbrVdSIdLY5zod7PnZY8fnqSzfO14mcJE=.2628f12d-7d4d-4ba1-8b61-f064e3a29cb8@github.com>

AgentOut.othervm.ok tries to access $(BUILDTESTDIR)/AgentOut.agentvm. This should only happen in AgentOut.agentvm.ok. 
Add a new target to filter log lines that depends on AgentOut.agentvm.ok.

Note: tests pass on retry[1]. The test failure is caused by [2]

[1] https://github.com/vpa1977/jtreg/actions/runs/18863066182
[2] https://github.com/openjdk/jtreg/pull/297

---------
### Progress
- [ ] Change must be properly reviewed (1 review required, with at least 1 [Reviewer](https://openjdk.org/bylaws#reviewer))
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue

### Error
&nbsp;?? The pull request body must not be empty.



### Reviewing
<details><summary>Using <code>git</code></summary>

Checkout this PR locally: \
`$ git fetch https://git.openjdk.org/jtreg.git pull/299/head:pull/299` \
`$ git checkout pull/299`

Update a local copy of the PR: \
`$ git checkout pull/299` \
`$ git pull https://git.openjdk.org/jtreg.git pull/299/head`

</details>
<details><summary>Using Skara CLI tools</summary>

Checkout this PR locally: \
`$ git pr checkout 299`

View PR using the GUI difftool: \
`$ git pr show -t 299`

</details>
<details><summary>Using diff file</summary>

Download this PR as a diff file: \
<a href="https://git.openjdk.org/jtreg/pull/299.diff">https://git.openjdk.org/jtreg/pull/299.diff</a>

</details>

-------------

Commit messages:
 - fix: filter agent output after agent target

Changes: https://git.openjdk.org/jtreg/pull/299/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=299&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904107
  Stats: 8 lines in 1 file changed: 4 ins; 2 del; 2 mod
  Patch: https://git.openjdk.org/jtreg/pull/299.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/299/head:pull/299

PR: https://git.openjdk.org/jtreg/pull/299

From vpetko at openjdk.org  Tue Oct 28 04:15:51 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Tue, 28 Oct 2025 04:15:51 GMT
Subject: RFR: 7904105: intermittent test failure in
 CleanupDirTests.agentvm.conc
Message-ID: <WGEdviTCuQCt8O-OUUOVew_mEFVLKn09nQc76y6yEY8=.618db97c-c19f-4181-afdc-33773a508144@github.com>

jtharness does not synchronize calls to Observer. Synchronized keyword needs to be added when processing shared state.

---------
### Progress
- [ ] Change must be properly reviewed (1 review required, with at least 1 [Reviewer](https://openjdk.org/bylaws#reviewer))
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue

### Error
&nbsp;?? The pull request body must not be empty.



### Reviewing
<details><summary>Using <code>git</code></summary>

Checkout this PR locally: \
`$ git fetch https://git.openjdk.org/jtreg.git pull/297/head:pull/297` \
`$ git checkout pull/297`

Update a local copy of the PR: \
`$ git checkout pull/297` \
`$ git pull https://git.openjdk.org/jtreg.git pull/297/head`

</details>
<details><summary>Using Skara CLI tools</summary>

Checkout this PR locally: \
`$ git pr checkout 297`

View PR using the GUI difftool: \
`$ git pr show -t 297`

</details>
<details><summary>Using diff file</summary>

Download this PR as a diff file: \
<a href="https://git.openjdk.org/jtreg/pull/297.diff">https://git.openjdk.org/jtreg/pull/297.diff</a>

</details>

-------------

Commit messages:
 - fix: synchronize the test result callbacks

Changes: https://git.openjdk.org/jtreg/pull/297/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=297&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904105
  Stats: 3 lines in 3 files changed: 0 ins; 0 del; 3 mod
  Patch: https://git.openjdk.org/jtreg/pull/297.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/297/head:pull/297

PR: https://git.openjdk.org/jtreg/pull/297

From vpetko at openjdk.org  Tue Oct 28 04:18:08 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Tue, 28 Oct 2025 04:18:08 GMT
Subject: RFR: 7904104: intermittent test failure in TimeoutDefaultSecondsWaiter
Message-ID: <bEk97nwTTIjbzyV9jzY48pgTfsPk5NSLaFJvpw1hn6M=.26aa577b-1604-44ba-bf7a-5f94ee2f2bc7@github.com>

`victim.interrupt()` is not needed if the process exits  after the kill signal. 
This PR only calls interrupt() if the process fails to exit or the wait is interrupted for some reason. 

This allows TimeoutDefaultSecondsWaiter tests to pass. 

Alternative: update assertion in TimeoutDefaultSecondsWaiter test.

---------
### Progress
- [ ] Change must be properly reviewed (1 review required, with at least 1 [Reviewer](https://openjdk.org/bylaws#reviewer))
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue

### Error
&nbsp;?? The pull request body must not be empty.



### Reviewing
<details><summary>Using <code>git</code></summary>

Checkout this PR locally: \
`$ git fetch https://git.openjdk.org/jtreg.git pull/296/head:pull/296` \
`$ git checkout pull/296`

Update a local copy of the PR: \
`$ git checkout pull/296` \
`$ git pull https://git.openjdk.org/jtreg.git pull/296/head`

</details>
<details><summary>Using Skara CLI tools</summary>

Checkout this PR locally: \
`$ git pr checkout 296`

View PR using the GUI difftool: \
`$ git pr show -t 296`

</details>
<details><summary>Using diff file</summary>

Download this PR as a diff file: \
<a href="https://git.openjdk.org/jtreg/pull/296.diff">https://git.openjdk.org/jtreg/pull/296.diff</a>

</details>

-------------

Commit messages:
 - chore: remove whitespace
 - fix: interrupt the main thread if the process fails to exit
 - fix: do not interrupt the main thread

Changes: https://git.openjdk.org/jtreg/pull/296/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=296&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904104
  Stats: 11 lines in 1 file changed: 8 ins; 0 del; 3 mod
  Patch: https://git.openjdk.org/jtreg/pull/296.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/296/head:pull/296

PR: https://git.openjdk.org/jtreg/pull/296

From jpai at openjdk.org  Tue Oct 28 08:39:42 2025
From: jpai at openjdk.org (Jaikiran Pai)
Date: Tue, 28 Oct 2025 08:39:42 GMT
Subject: RFR: 7904106: TestNativePath: intermittent test failures due to
 different test targets using same work dir
In-Reply-To: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>
References: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>
Message-ID: <YwVVo9BxtCIVNnY08Xfnza9uBN6UeyoIb6khK6FFQ9A=.6f8c238f-8da9-41bf-8b62-3aecbd2e618a@github.com>

On Tue, 28 Oct 2025 03:19:54 GMT, Vladimir Petko <vpetko at openjdk.org> wrote:

> Both agentvm and othervm targets use the same work path `$(BUILDTESTDIR)/nativepath.othervm/work`. This causes intermittent test failures when the tests are run in parallel. 
> 
> ---------
> ### Progress
> - [ ] Change must be properly reviewed (1 review required, with at least 1 [Reviewer](https://openjdk.org/bylaws#reviewer))
> - [x] Change must not contain extraneous whitespace
> - [x] Commit message must refer to an issue
> 
> ### Error
> &nbsp;?? The pull request body must not be empty.
> 
> 
> 
> ### Reviewing
> <details><summary>Using <code>git</code></summary>
> 
> Checkout this PR locally: \
> `$ git fetch https://git.openjdk.org/jtreg.git pull/298/head:pull/298` \
> `$ git checkout pull/298`
> 
> Update a local copy of the PR: \
> `$ git checkout pull/298` \
> `$ git pull https://git.openjdk.org/jtreg.git pull/298/head`
> 
> </details>
> <details><summary>Using Skara CLI tools</summary>
> 
> Checkout this PR locally: \
> `$ git pr checkout 298`
> 
> View PR using the GUI difftool: \
> `$ git pr show -t 298`
> 
> </details>
> <details><summary>Using diff file</summary>
> 
> Download this PR as a diff file: \
> <a href="https://git.openjdk.org/jtreg/pull/298.diff">https://git.openjdk.org/jtreg/pull/298.diff</a>
> 
> </details>

This looks OK to me.

-------------

Marked as reviewed by jpai (Reviewer).

PR Review: https://git.openjdk.org/jtreg/pull/298#pullrequestreview-3387353215

From jpai at openjdk.org  Tue Oct 28 08:48:40 2025
From: jpai at openjdk.org (Jaikiran Pai)
Date: Tue, 28 Oct 2025 08:48:40 GMT
Subject: RFR: 7904105: intermittent test failure in
 CleanupDirTests.agentvm.conc
In-Reply-To: <WGEdviTCuQCt8O-OUUOVew_mEFVLKn09nQc76y6yEY8=.618db97c-c19f-4181-afdc-33773a508144@github.com>
References: <WGEdviTCuQCt8O-OUUOVew_mEFVLKn09nQc76y6yEY8=.618db97c-c19f-4181-afdc-33773a508144@github.com>
Message-ID: <__CbDxfnNzwKsBo_guhAt2RDiTdY42Hc2D-EbKuF5CI=.b4400934-6b56-4829-9bcd-b3bee89d9831@github.com>

On Tue, 28 Oct 2025 03:12:34 GMT, Vladimir Petko <vpetko at openjdk.org> wrote:

> jtharness does not synchronize calls to Observer. Synchronized keyword needs to be added when processing shared state.
> 
> ---------
> ### Progress
> - [ ] Change must be properly reviewed (1 review required, with at least 1 [Reviewer](https://openjdk.org/bylaws#reviewer))
> - [x] Change must not contain extraneous whitespace
> - [x] Commit message must refer to an issue
> 
> ### Error
> &nbsp;?? The pull request body must not be empty.
> 
> 
> 
> ### Reviewing
> <details><summary>Using <code>git</code></summary>
> 
> Checkout this PR locally: \
> `$ git fetch https://git.openjdk.org/jtreg.git pull/297/head:pull/297` \
> `$ git checkout pull/297`
> 
> Update a local copy of the PR: \
> `$ git checkout pull/297` \
> `$ git pull https://git.openjdk.org/jtreg.git pull/297/head`
> 
> </details>
> <details><summary>Using Skara CLI tools</summary>
> 
> Checkout this PR locally: \
> `$ git pr checkout 297`
> 
> View PR using the GUI difftool: \
> `$ git pr show -t 297`
> 
> </details>
> <details><summary>Using diff file</summary>
> 
> Download this PR as a diff file: \
> <a href="https://git.openjdk.org/jtreg/pull/297.diff">https://git.openjdk.org/jtreg/pull/297.diff</a>
> 
> </details>

Hello Vladimir, we have seen intermittent failure in this test too, but i haven't had a chance to look deeper.

`TestStats` deals with counts in several different methods, so I'm not completely sure the proposed change is enough or the best way to address this. It may be that the code in `TestStats` itself might need to be addressed in some manner.

-------------

PR Comment: https://git.openjdk.org/jtreg/pull/297#issuecomment-3455233085

From vpetko at openjdk.org  Tue Oct 28 19:49:58 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Tue, 28 Oct 2025 19:49:58 GMT
Subject: RFR: 7904105: intermittent test failure in
 CleanupDirTests.agentvm.conc
In-Reply-To: <__CbDxfnNzwKsBo_guhAt2RDiTdY42Hc2D-EbKuF5CI=.b4400934-6b56-4829-9bcd-b3bee89d9831@github.com>
References: <WGEdviTCuQCt8O-OUUOVew_mEFVLKn09nQc76y6yEY8=.618db97c-c19f-4181-afdc-33773a508144@github.com>
 <__CbDxfnNzwKsBo_guhAt2RDiTdY42Hc2D-EbKuF5CI=.b4400934-6b56-4829-9bcd-b3bee89d9831@github.com>
Message-ID: <PpWO5O6ZIWbFh9WWNNUxY-rjXucaQaHTPPKKf50l5xk=.91e11bfd-fef1-4233-b4b7-84033883fd23@github.com>

On Tue, 28 Oct 2025 08:45:47 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:

> Hello Vladimir, we have seen intermittent failure in this test too, but i haven't had a chance to look deeper.
> 
> `TestStats` deals with counts in several different methods, so I'm not completely sure the proposed change is enough or the best way to address this. It may be that the code in `TestStats` itself might need to be addressed in some manner.

Hi, 

I have tried using atomics in TestStats and the implementation looked ugly / required a lot of refactoring. 

We already use `synchonzied` keyword in Observer callbacks[1] as the TestRunner may spawn multiple threads if we specify concurrency > 1. I have used Intellij Idea to find all inheritors of BasicObserver and added synchronization. 

Maybe the better way would be to synchronize in jtharness itself to avoid  doing it in the client code?

[1] https://github.com/openjdk/jtreg/blob/34ccc66ec89651637811678a17d3f810b4ac0780/src/share/classes/com/sun/javatest/regtest/report/ElapsedTimeHandler.java#L64

-------------

PR Comment: https://git.openjdk.org/jtreg/pull/297#issuecomment-3458212429

From duke at openjdk.org  Tue Oct 28 19:50:58 2025
From: duke at openjdk.org (duke)
Date: Tue, 28 Oct 2025 19:50:58 GMT
Subject: RFR: 7904106: TestNativePath: intermittent test failures due to
 different test targets using same work dir
In-Reply-To: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>
References: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>
Message-ID: <ZsEjhMHue5QEtUIOQvGMHGAYyQkJQFQejlECZkhofjo=.04e00fff-ca97-41b6-beab-369bd5372135@github.com>

On Tue, 28 Oct 2025 03:19:54 GMT, Vladimir Petko <vpetko at openjdk.org> wrote:

> Both agentvm and othervm targets use the same work path `$(BUILDTESTDIR)/nativepath.othervm/work`. This causes intermittent test failures when the tests are run in parallel.

@vpa1977 
Your change (at version dbb8108bd0edcf56fb326f5c71bf3dc248036538) is now ready to be sponsored by a Committer.

-------------

PR Comment: https://git.openjdk.org/jtreg/pull/298#issuecomment-3458218656

From vpetko at openjdk.org  Wed Oct 29 01:33:43 2025
From: vpetko at openjdk.org (Vladimir Petko)
Date: Wed, 29 Oct 2025 01:33:43 GMT
Subject: Integrated: 7904106: TestNativePath: intermittent test failures due to
 different test targets using same work dir
In-Reply-To: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>
References: <OFrCzSi5vYiX1cuCPdAzqz0SzZkbBMGIe4i5PkqVpRI=.d58b9dd0-bd62-44db-9073-aa7c14728c0f@github.com>
Message-ID: <-PUm7lQgdrawgnv28iA5OtFIxtb2F9DuKheiYxSnYEc=.028a7fed-8c88-4ed9-a303-94588c4cbe6a@github.com>

On Tue, 28 Oct 2025 03:19:54 GMT, Vladimir Petko <vpetko at openjdk.org> wrote:

> Both agentvm and othervm targets use the same work path `$(BUILDTESTDIR)/nativepath.othervm/work`. This causes intermittent test failures when the tests are run in parallel.

This pull request has now been integrated.

Changeset: da877fc8
Author:    Vladimir Petko <vpetko at openjdk.org>
Committer: Jaikiran Pai <jpai at openjdk.org>
URL:       https://git.openjdk.org/jtreg/commit/da877fc8b06d3326eff5c4830600765063513bab
Stats:     19 lines in 1 file changed: 0 ins; 1 del; 18 mod

7904106: TestNativePath: intermittent test failures due to different test targets using same work dir

Reviewed-by: jpai

-------------

PR: https://git.openjdk.org/jtreg/pull/298

From jvernee at openjdk.org  Fri Oct 31 18:13:20 2025
From: jvernee at openjdk.org (Jorn Vernee)
Date: Fri, 31 Oct 2025 18:13:20 GMT
Subject: RFR: 7904110: IDEA plugin: Update plugin for new message format
Message-ID: <d-0QgpPbWNAMQ9UxvMXFEyzW_Vdxhbu8ZJN5n0QdVvU=.81923932-98e4-4776-b535-c1bcd648d649@github.com>

The JUnit output was updated to include a timestamp in https://github.com/openjdk/jtreg/commit/470718a0637fbfd9a883de66e7955a4c26e05760

This patch updates the parser in the idea plugin to be able to handle the timestamps.

-------------

Commit messages:
 - Adapt JUnit result parser for timestamps in output

Changes: https://git.openjdk.org/jtreg/pull/300/files
  Webrev: https://webrevs.openjdk.org/?repo=jtreg&pr=300&range=00
  Issue: https://bugs.openjdk.org/browse/CODETOOLS-7904110
  Stats: 5 lines in 1 file changed: 1 ins; 0 del; 4 mod
  Patch: https://git.openjdk.org/jtreg/pull/300.diff
  Fetch: git fetch https://git.openjdk.org/jtreg.git pull/300/head:pull/300

PR: https://git.openjdk.org/jtreg/pull/300

From cstein at openjdk.org  Fri Oct 31 19:04:41 2025
From: cstein at openjdk.org (Christian Stein)
Date: Fri, 31 Oct 2025 19:04:41 GMT
Subject: RFR: 7904110: IDEA plugin: Update plugin for new message format
In-Reply-To: <d-0QgpPbWNAMQ9UxvMXFEyzW_Vdxhbu8ZJN5n0QdVvU=.81923932-98e4-4776-b535-c1bcd648d649@github.com>
References: <d-0QgpPbWNAMQ9UxvMXFEyzW_Vdxhbu8ZJN5n0QdVvU=.81923932-98e4-4776-b535-c1bcd648d649@github.com>
Message-ID: <5hOQLT48S1xKTbw4Wp0UArATLZfTqq76mW7QFmzPGM4=.9f07381d-af12-43b0-a670-53d18bd2ae1b@github.com>

On Fri, 31 Oct 2025 18:08:52 GMT, Jorn Vernee <jvernee at openjdk.org> wrote:

> The JUnit output was updated to include a timestamp in https://github.com/openjdk/jtreg/commit/470718a0637fbfd9a883de66e7955a4c26e05760
> 
> This patch updates the parser in the idea plugin to be able to handle the timestamps.

This might be a bit too lenient in some cases, but also supports the new message format.

-------------

Marked as reviewed by cstein (Reviewer).

PR Review: https://git.openjdk.org/jtreg/pull/300#pullrequestreview-3405750234