On Thu, 19 May 2022 09:38:06 GMT, Alan Bateman wrote:
> This change is mostly test infrastructure and improvements to the testing of
> thread dumps in JSON format. It also tweaks the thread dump format so that
> the process identifier and thread identifiers are a type string rather than
> numb
It was a typo when the original CLEARING_MASK was initially introduced:
// Mask to clear normal event bits.
const jlong CLEARING_MASK = (1L >> (TOTAL_MIN_EVENT_TYPE_VAL -
TOTAL_MIN_EVENT_TYPE_VAL)) - 1L;
// Avoid cleaning extension event bits.
jlong enabled_bits = CLEARING_MASK &
env->en
On Mon, 23 May 2022 19:33:31 GMT, Alan Bateman wrote:
>> This change is mostly test infrastructure and improvements to the testing of
>> thread dumps in JSON format. It also tweaks the thread dump format so that
>> the process identifier and thread identifiers are a type string rather than
>>
> Replaces usages of articles that follow each other in all combinations:
> a/the, an?/an?, the/the…
>
> It's the last issue in the series, and it still touches different areas of
> the code.
Alexey Ivanov has updated the pull request with a new target base due to a
merge or a rebase. The pull
> Replaces usages of articles that follow each other in all combinations:
> a/the, an?/an?, the/the…
>
> Also, I fixed a couple of spelling mistakes.
Alexey Ivanov has updated the pull request incrementally with one additional
commit since the last revision:
Update copyright to 2022
---
> This change is mostly test infrastructure and improvements to the testing of
> thread dumps in JSON format. It also tweaks the thread dump format so that
> the process identifier and thread identifiers are a type string rather than
> number.
>
> The tests for thread dumps added by JEP 425 are
On Mon, 23 May 2022 09:24:19 GMT, Severin Gehwolf wrote:
>> Also, I think the current PR could produce the wrong answer, if systemd is
>> indeed running inside the container, and we have:
>>
>>
>> "/user.slice/user-1000.slice/session-50.scope",// root_path
>> "/user.slice/user-1000.slice/s
On Mon, 23 May 2022 02:52:38 GMT, David Holmes wrote:
>> I was really trying to emphasize that the flag is preview, and therefore may
>> change or go away. If I change as you suggest, the reader could imply that
>> as long as virtual threads support is in place, then the flag will be also
>>
Adding hotspot-gc-dev.
On 5/21/22 12:49 AM, Volker Simonis wrote:
This sounds very interesting. Does this feature work with every GC or
does the implementation depend on specific GCs (and if the latter,
which GCs does your prototype currently support).
Kemper, William schrieb am Fr., 20. Ma
On Mon, 23 May 2022 07:52:58 GMT, Alan Bateman wrote:
>> test/jdk/com/sun/management/HotSpotDiagnosticMXBean/DumpThreads.java line
>> 115:
>>
>>> 113:
>>> 114: // find the thread container that corresponds to the
>>> executor
>>> 115: String name = Objects.toId
On Mon, 23 May 2022 16:44:12 GMT, Chris Plummer wrote:
>> Alan Bateman has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Use string rater than number for process/thread identifiers
>
> test/lib/jdk/test/lib/threaddump/ThreadDump.java line
On Mon, 23 May 2022 07:53:09 GMT, Alan Bateman wrote:
>> test/lib/jdk/test/lib/threaddump/ThreadDump.java line 179:
>>
>>> 177: return this;
>>> 178: if (name().startsWith(name + "/"))
>>> 179: return this;
>>
>> It's not clear to me why this is here.
On Mon, 23 May 2022 08:30:51 GMT, Alan Bateman wrote:
>> This change is mostly test infrastructure and improvements to the testing of
>> thread dumps in JSON format. It also tweaks the thread dump format so that
>> the process identifier and thread identifiers are a type string rather than
>>
On Mon, 9 May 2022 01:36:39 GMT, Leonid Mesnik wrote:
> The fix disables EscapeBarrier and EscapeAnalysis when certain JVMTI
> capabilities are enabled and --enable-preview.
>
> It restores the same behavior as it was before
> https://bugs.openjdk.java.net/browse/JDK-8227745 "Enable Escape Ana
On Fri, 20 May 2022 22:27:29 GMT, Leonid Mesnik wrote:
> Sync improved in test
This pull request has now been integrated.
Changeset: 110d9064
Author:Leonid Mesnik
URL:
https://git.openjdk.java.net/jdk/commit/110d906432761482acd2899be1314e075bc21bec
Stats: 7 lines in 1 file chang
On Mon, 23 May 2022 10:20:39 GMT, Richard Reingruber wrote:
> Could it be that you mean
> [JDK-8264699](https://bugs.openjdk.java.net/browse/JDK-8264699)?
>
Yes, you are right.
> I'm ok with this version of your fix. I'd suggest to change title/synopsis of
> the bug report to better match it t
On Sat, 21 May 2022 16:34:32 GMT, Leonid Mesnik wrote:
>> Sync improved in test
>
> Leonid Mesnik has updated the pull request incrementally with one additional
> commit since the last revision:
>
> fix
Looks good!
-
Marked as reviewed by kevinw (Committer).
PR: https://git.op
On Mon, 23 May 2022 09:58:46 GMT, David Holmes wrote:
> Sorry but I can't agree with this change as presented. By definition the
> total non-heap memory is the sum of all pools which identify as non-heap as
> per the specification:
>
> "The non-heap memory consists of one or more memory pools.
> Please review this patch adding new lint option, **lossy-conversions**, to
> javac to warn about type casts in compound assignments with possible lossy
> conversions.
>
> The new lint warning is shown if the type of the right-hand operand of a
> compound assignment is not assignment compatibl
> Please review this patch adding new lint option, **lossy-conversions**, to
> javac to warn about type casts in compound assignments with possible lossy
> conversions.
>
> The new lint warning is shown if the type of the right-hand operand of a
> compound assignment is not assignment compatibl
On Sat, 21 May 2022 16:09:17 GMT, Leonid Mesnik wrote:
> > Hi Leonid, if EscapeAnalysis is not disabled, then local objects cannot be
> > read per JVMTI if they are scalarized in compiled frames on the heap,
> > right? This would be a problem I'd think. Thanks, Richard.
>
> Yes, the fix restor
On Mon, 23 May 2022 07:28:41 GMT, Yi Yang wrote:
> It seems that calculation of
> MemoryMXBean.getNonHeapMemoryUsage(jmm_GetMemoryUsage) is wrong.
>
> Currently, NonHeapUsage = CodeCache + Metaspace + CompressedClassSpace
>
> ==> CodeHeap 'non-nmethods' 1532544 (Used)
> ==> CodeHeap 'profiled
On Thu, 19 May 2022 20:18:50 GMT, Ioi Lam wrote:
>> I am wondering if the problem is this:
>>
>> We have systemd running on the host, and a different copy of systemd that
>> runs inside the container.
>>
>> - They both set up `/user.slice/user-1000.slice/session-??.scope` within
>> their own
On Mon, 23 May 2022 08:30:51 GMT, Alan Bateman wrote:
>> This change is mostly test infrastructure and improvements to the testing of
>> thread dumps in JSON format. It also tweaks the thread dump format so that
>> the process identifier and thread identifiers are a type string rather than
>>
> This change is mostly test infrastructure and improvements to the testing of
> thread dumps in JSON format. It also tweaks the thread dump format so that
> the process identifier and thread identifiers are a type string rather than
> number.
>
> The tests for thread dumps added by JEP 425 are
On Mon, 23 May 2022 06:09:58 GMT, Chris Plummer wrote:
>> Alan Bateman has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Remove spurious colon
>
> test/jdk/com/sun/management/HotSpotDiagnosticMXBean/DumpThreads.java line 115:
>
>> 113:
>
It seems that calculation of
MemoryMXBean.getNonHeapMemoryUsage(jmm_GetMemoryUsage) is wrong.
Currently, NonHeapUsage = CodeCache + Metaspace + CompressedClassSpace
==> CodeHeap 'non-nmethods' 1532544 (Used)
==> CodeHeap 'profiled nmethods' 0
==> CodeHeap 'non-profiled nmethods' 13952
==> Metasp
27 matches
Mail list logo
