On Wed, 14 Jul 2021 04:00:39 GMT, xpbob
wrote:
>> …ocess cpu usage in containers
>
> xpbob has updated the pull request incrementally with one additional commit
> since the last revision:
>
> Add comments
Will sponsor it tomorrow if there is no objection.
Thanks.
-
PR: https:
On Tue, 27 Jul 2021 09:24:38 GMT, Nick Gasson wrote:
> This test fails reliably with `-XX:TieredStopAtLevel=1` since JDK-8251462.
> MDOs are no longer allocated in this mode so the clhsdb `printmdo -a` command
> prints nothing. The failure is basically the same as JDK-8236042 which
> happened
On Fri, 16 Jul 2021 10:24:56 GMT, Nick Gasson wrote:
> The clhsdb jstack command crashes when the debugged program is run with
> `-Xcomp -XX:+StressGCM -XX:StressSeed=2` on AArch64:
>
>
> sun.jvm.hotspot.utilities.AssertionFailure: sanity check
> at jdk.hotspot.agent/sun.jvm.hotspot.utilit
Thanks for the help Chris. With the JBS ticket set up are we ready for a PR to
be opened, or should I wait for the CSR review?
Jakob
On 7/27/21 4:38 PM, Jakob Cornell wrote:
Hi all,
I've prepared a patch that makes JDB rerun the previous command when
nothing is entered at the prompt. Looks like the next step is to open
a JBS issue so I can submit a PR, but as a new contributor I don't
have credentials to open a JBS issue.
Oops, the mailman didn't link this to the previous thread:
https://mail.openjdk.java.net/pipermail/serviceability-dev/2021-June/038226.html
Hi all,
I've prepared a patch that makes JDB rerun the previous command when nothing is
entered at the prompt. Looks like the next step is to open a JBS issue so I
can submit a PR, but as a new contributor I don't have credentials to open a
JBS issue. Is anybody willing to sponsor my change?
On Tue, 27 Jul 2021 09:24:38 GMT, Nick Gasson wrote:
> This test fails reliably with `-XX:TieredStopAtLevel=1` since JDK-8251462.
> MDOs are no longer allocated in this mode so the clhsdb `printmdo -a` command
> prints nothing. The failure is basically the same as JDK-8236042 which
> happened
On Tue, 27 Jul 2021 09:24:38 GMT, Nick Gasson wrote:
> This test fails reliably with `-XX:TieredStopAtLevel=1` since JDK-8251462.
> MDOs are no longer allocated in this mode so the clhsdb `printmdo -a` command
> prints nothing. The failure is basically the same as JDK-8236042 which
> happened
On Fri, 16 Jul 2021 10:24:56 GMT, Nick Gasson wrote:
> The clhsdb jstack command crashes when the debugged program is run with
> `-Xcomp -XX:+StressGCM -XX:StressSeed=2` on AArch64:
>
>
> sun.jvm.hotspot.utilities.AssertionFailure: sanity check
> at jdk.hotspot.agent/sun.jvm.hotspot.utilit
This test fails reliably with `-XX:TieredStopAtLevel=1` since JDK-8251462. MDOs
are no longer allocated in this mode so the clhsdb `printmdo -a` command prints
nothing. The failure is basically the same as JDK-8236042 which happened with
`-Xcomp -XX:TieredStopAtLevel=1` so the workaround for th
11 matches
Mail list logo
