On Thu, 24 Feb 2022 15:02:40 GMT, Kevin Walls wrote:
>> Test fails occasionally due to a port clash.
>> Presumably the port that was returned by Utils.getFreePort(), is no longer
>> free.
>> The test creates a ProcessBuilder with the parameters for JMX, including
>> port number, and uses that t
On Thu, 24 Feb 2022 12:17:54 GMT, Kevin Walls wrote:
>> Test fails occasionally due to a port clash.
>> Presumably the port that was returned by Utils.getFreePort(), is no longer
>> free.
>> The test creates a ProcessBuilder with the parameters for JMX, including
>> port number, and uses that t
> Test fails occasionally due to a port clash.
> Presumably the port that was returned by Utils.getFreePort(), is no longer
> free.
> The test creates a ProcessBuilder with the parameters for JMX, including port
> number, and uses that to create a new Process.
> It should retry with a new port if
On Mon, 21 Feb 2022 14:43:27 GMT, Johannes Bechberger
wrote:
> Fixes the mentioned bug by replacing the check in AsyncGetCallTrace using the
> newly introduced method `JavaThread::thread_from_jni_environment`.
This pull request has now been integrated.
Changeset: 231e48fa
Author:Johannes
On Thu, 24 Feb 2022 12:44:18 GMT, Alex Menkov wrote:
> The fix adds workaround in hs201t001a class like we have in hs201t001 test to
> avoid class loading while the test do single stepping/pop frame.
> Also fixed a number of issues in the test.
test/hotspot/jtreg/vmTestbase/nsk/jvmti/scenarios/
The fix adds workaround in hs201t001a class like we have in hs201t001 test to
avoid class loading while the test do single stepping/pop frame.
Also fixed a number of issues in the test.
-
Commit messages:
- trailing whitespace
- JDK-8267796
Changes: https://git.openjdk.java.net/jd
On Thu, 24 Feb 2022 12:17:54 GMT, Kevin Walls wrote:
>> Test fails occasionally due to a port clash.
>> Presumably the port that was returned by Utils.getFreePort(), is no longer
>> free.
>> The test creates a ProcessBuilder with the parameters for JMX, including
>> port number, and uses that t
On Thu, 24 Feb 2022 12:17:54 GMT, Kevin Walls wrote:
>> Test fails occasionally due to a port clash.
>> Presumably the port that was returned by Utils.getFreePort(), is no longer
>> free.
>> The test creates a ProcessBuilder with the parameters for JMX, including
>> port number, and uses that t
> Test fails occasionally due to a port clash.
> Presumably the port that was returned by Utils.getFreePort(), is no longer
> free.
> The test creates a ProcessBuilder with the parameters for JMX, including port
> number, and uses that to create a new Process.
> It should retry with a new port if
On Wed, 23 Feb 2022 17:42:35 GMT, Alex Menkov wrote:
> The test uses warm-up predicate in a strange way
Thanks Alex - yes so that's why we only see one line in the predicate, it
contains the word "exception" and the predicate returns true, signalling that
the process is done starting up. 8-)
B
On Wed, 23 Feb 2022 17:19:16 GMT, Mark Sheppard wrote:
> An alternative is to use a fixed port 1098
Thanks Mark - I will avoid that fixed slot as we no doubt run tests
concurrently, and also in case these get backported far enough that it's not
free. 8-)
Utils.getFreePort() lets new ServerSoc
On Wed, 23 Feb 2022 21:59:35 GMT, Johannes Bechberger
wrote:
>> Fixes the mentioned bug by replacing the check in AsyncGetCallTrace using
>> the newly introduced method `JavaThread::thread_from_jni_environment`.
>
> Johannes Bechberger has updated the pull request incrementally with one
> addi
On Wed, 23 Feb 2022 21:59:35 GMT, Johannes Bechberger
wrote:
>> Fixes the mentioned bug by replacing the check in AsyncGetCallTrace using
>> the newly introduced method `JavaThread::thread_from_jni_environment`.
>
> Johannes Bechberger has updated the pull request incrementally with one
> addi
13 matches
Mail list logo