On Fri, 9 Dec 2022 01:16:58 GMT, Chris Plummer wrote:
>> 3 things to cleanup in this area:
>>
>> (1) The JDWP agent uses `JNI GetEnv(JVMTI_VERSION_1)` to get a JVMTI
>> environment. If `GetEnv` fails the JDWP agent prints this:
>>
>> `ERROR: JDWP unable to access JVMTI Version 1 (0x3001),
On Fri, 9 Dec 2022 01:16:58 GMT, Chris Plummer wrote:
>> 3 things to cleanup in this area:
>>
>> (1) The JDWP agent uses `JNI GetEnv(JVMTI_VERSION_1)` to get a JVMTI
>> environment. If `GetEnv` fails the JDWP agent prints this:
>>
>> `ERROR: JDWP unable to access JVMTI Version 1 (0x3001),
On Tue, 6 Dec 2022 04:54:50 GMT, David Holmes wrote:
> This PR seems to be broken now - full of unexpected changes.
The PR changed files are correct now.
-
PR: https://git.openjdk.org/jdk/pull/11288
On Thu, 8 Dec 2022 12:37:17 GMT, Sergey Tsypanov wrote:
> Newer version of IntelliJ IDEA introduces new
> [inspection](https://youtrack.jetbrains.com/issue/IDEA-301797/IDEA-should-report-redundant-array-length-check-in-certain-cases)
> detecting redundant array length check in snippets like
>
On Thu, 8 Dec 2022 12:37:17 GMT, Sergey Tsypanov wrote:
> Newer version of IntelliJ IDEA introduces new
> [inspection](https://youtrack.jetbrains.com/issue/IDEA-301797/IDEA-should-report-redundant-array-length-check-in-certain-cases)
> detecting redundant array length check in snippets like
>
On Fri, 9 Dec 2022 14:35:47 GMT, Roger Riggs wrote:
>> Newer version of IntelliJ IDEA introduces new
>> [inspection](https://youtrack.jetbrains.com/issue/IDEA-301797/IDEA-should-report-redundant-array-length-check-in-certain-cases)
>> detecting redundant array length check in snippets like
>>
On Thu, 8 Dec 2022 12:37:17 GMT, Sergey Tsypanov wrote:
> Newer version of IntelliJ IDEA introduces new
> [inspection](https://youtrack.jetbrains.com/issue/IDEA-301797/IDEA-should-report-redundant-array-length-check-in-certain-cases)
> detecting redundant array length check in snippets like
>
On Fri, 9 Dec 2022 03:12:36 GMT, Chris Plummer wrote:
>> This fixes two separate CRs:
>>
>> [JDK-8241293](https://bugs.openjdk.org/browse/JDK-8241293)
>> CompressedClassSpaceSizeInJmapHeap.java time out after 8 minutes
>> [JDK-8298073](https://bugs.openjdk.org/browse/JDK-8298073)
>> gc/metaspa
On Thu, 8 Dec 2022 03:06:31 GMT, Chris Plummer wrote:
> This fixes two separate CRs:
>
> [JDK-8241293](https://bugs.openjdk.org/browse/JDK-8241293)
> CompressedClassSpaceSizeInJmapHeap.java time out after 8 minutes
> [JDK-8298073](https://bugs.openjdk.org/browse/JDK-8298073)
> gc/metaspace/Com
On Fri, 9 Dec 2022 03:00:36 GMT, Serguei Spitsyn wrote:
> Should we consider filing a CSR as potentially there is a minimal
> compatibility risk?
It don't think it should be necessary. I don't believe there are any known
compatibility issues here. Although we switched from requesting
`JVMTI_V
On Fri, 9 Dec 2022 01:16:58 GMT, Chris Plummer wrote:
>> 3 things to cleanup in this area:
>>
>> (1) The JDWP agent uses `JNI GetEnv(JVMTI_VERSION_1)` to get a JVMTI
>> environment. If `GetEnv` fails the JDWP agent prints this:
>>
>> `ERROR: JDWP unable to access JVMTI Version 1 (0x3001),
On Fri, 9 Dec 2022 01:16:58 GMT, Chris Plummer wrote:
>> 3 things to cleanup in this area:
>>
>> (1) The JDWP agent uses `JNI GetEnv(JVMTI_VERSION_1)` to get a JVMTI
>> environment. If `GetEnv` fails the JDWP agent prints this:
>>
>> `ERROR: JDWP unable to access JVMTI Version 1 (0x3001),
On Fri, 9 Dec 2022 19:39:16 GMT, Daniel D. Daugherty wrote:
> if you asked for JVMTI_VERSION_1, could you get back JVMTI_VERSION_1_2 or
> JVMTI_VERSION_9 or
JVMTI_VERSION_11 if the JVM in question supported each of those versions (and
no higher)?
Yes, but the debug agent does a version check
In the log for most SA tests on macos-aarch64-debug, you will see something
like:
STDOUT:
Executable=/System/Volumes/Data/mesos/work_dir/jib-master/install/2022-12-07-2219530.chris.plummer.jdk/macosx-aarch64-debug.jdk/jdk-20/fastdebug/bin/java
...
STDOUT: CodeDirectory v=20400 size=758 flags=0x
The fix updates the test to ignore ThreadDeathEvent event from non-test
threads waiting for breakpoint
-
Commit messages:
- Fixed suspendpolicy009 test
Changes: https://git.openjdk.org/jdk/pull/11620/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=11620&range=00
Issue: h
One more test fix to ignore ThreadDeathEvent event from non-test threads
waiting for breakpoint
-
Commit messages:
- Fixed thrdeathreq002 test
Changes: https://git.openjdk.org/jdk/pull/11621/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=11621&range=00
Issue: https://bug
On Fri, 9 Dec 2022 22:16:44 GMT, Chris Plummer wrote:
> In the log for most SA tests on macos-aarch64-debug, you will see something
> like:
>
>
> STDOUT:
> Executable=/System/Volumes/Data/mesos/work_dir/jib-master/install/2022-12-07-2219530.chris.plummer.jdk/macosx-aarch64-debug.jdk/jdk-20/fa
17 matches
Mail list logo