On Mon, 13 Dec 2021 04:19:39 GMT, David Holmes wrote:
> Investigation showed this test was experiencing interference from threads
> created by other tests in agentvm mode. The simple solution is to run this
> test isolated using othervm mode. Also added some diagnostics to the test
> incase we
On Mon, 13 Dec 2021 04:19:39 GMT, David Holmes wrote:
> Investigation showed this test was experiencing interference from threads
> created by other tests in agentvm mode. The simple solution is to run this
> test isolated using othervm mode. Also added some diagnostics to the test
> incase we
On Fri, 10 Dec 2021 19:49:48 GMT, Harold Seigel wrote:
>> Please review this change to obsolete deprecated CDS options
>> UseSharedSpaces, RequireSharedSpaces, DynamicDumpSharedSpaces, and
>> DumpSharedSpaces. The change was tested by running Mach5 tiers 1-2 on
>> Linux, Mac OS, and Windows a
On Fri, 10 Dec 2021 15:01:29 GMT, Harold Seigel wrote:
> Please review this change to obsolete deprecated CDS options UseSharedSpaces,
> RequireSharedSpaces, DynamicDumpSharedSpaces, and DumpSharedSpaces. The
> change was tested by running Mach5 tiers 1-2 on Linux, Mac OS, and Windows
> and M
On Mon, 13 Dec 2021 04:19:39 GMT, David Holmes wrote:
> Investigation showed this test was experiencing interference from threads
> created by other tests in agentvm mode. The simple solution is to run this
> test isolated using othervm mode. Also added some diagnostics to the test
> incase we
On Fri, 10 Dec 2021 07:00:10 GMT, Chris Plummer wrote:
> The test searches for "JShellToolProvider" in the main thread's stack trace,
> which is pulled from an SA heap dump. Typically the main thread is blocked in
> Object.wait(), so SA can determine its stack trace. However, the wait has a
>
On Mon, 13 Dec 2021 04:19:39 GMT, David Holmes wrote:
> Investigation showed this test was experiencing interference from threads
> created by other tests in agentvm mode. The simple solution is to run this
> test isolated using othervm mode. Also added some diagnostics to the test
> incase we
On Mon, 13 Dec 2021 04:19:39 GMT, David Holmes wrote:
> Investigation showed this test was experiencing interference from threads
> created by other tests in agentvm mode. The simple solution is to run this
> test isolated using othervm mode. Also added some diagnostics to the test
> incase we
On Mon, 13 Dec 2021 04:19:39 GMT, David Holmes wrote:
> Investigation showed this test was experiencing interference from threads
> created by other tests in agentvm mode. The simple solution is to run this
> test isolated using othervm mode. Also added some diagnostics to the test
> incase we
This change makes VM_Version_Ext part of VM_Version (the platform dependent
part) and moves some duplicated code. x86 had the most code in VM_Version_Ext,
so the most code moved there. There might be some unneeded functions but I
didn't want to remove them with this change.
Tier1 (tier2-4 test
This changes removes (most) Attach API tests from exclusiveAccess.dirs so the
tests can be run in parallel. I haven't seen any issues with this change,
except the jstatd tests can fail due to an RMI issue. I filed
https://bugs.openjdk.java.net/browse/JDK-8278625 to cover that issue.
---
On Mon, 13 Dec 2021 21:00:02 GMT, Chris Plummer wrote:
> This changes removes (most) Attach API tests from exclusiveAccess.dirs so the
> tests can be run in parallel. I haven't seen any issues with this change,
> except the jstatd tests can fail due to an RMI issue. I filed
> https://bugs.open
Include the size of the core file when printing a message that it was found.
-
Commit messages:
- Print the size of the core file found
Changes: https://git.openjdk.java.net/jdk/pull/6822/files
Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=6822&range=00
Issue: https://bug
On Tue, 14 Dec 2021 01:14:45 GMT, Chris Plummer wrote:
> Include the size of the core file when printing a message that it was found.
Marked as reviewed by amenkov (Reviewer).
-
PR: https://git.openjdk.java.net/jdk/pull/6822
Forwardport JDK 18 -> JDK 19
-
Commit messages:
- Merge
- 8132785: java/lang/management/ThreadMXBean/ThreadLists.java fails
intermittently
- 8273108: RunThese24H crashes with SEGV in markWord::displaced_mark_helper()
after JDK-8268276
- 8278580: ProblemList javax/swing/JTree/490
On Tue, 14 Dec 2021 01:14:45 GMT, Chris Plummer wrote:
> Include the size of the core file when printing a message that it was found.
Marked as reviewed by lmesnik (Reviewer).
-
PR: https://git.openjdk.java.net/jdk/pull/6822
> Forwardport JDK 18 -> JDK 19
Jesper Wilhelmsson has updated the pull request with a new target base due to a
merge or a rebase. The incremental webrev excludes the unrelated changes
brought in by the merge/rebase. The pull request contains 29 additional commits
since the last revision:
- Me
On Tue, 14 Dec 2021 01:35:43 GMT, Jesper Wilhelmsson
wrote:
> Forwardport JDK 18 -> JDK 19
This pull request has now been integrated.
Changeset: 8401a059
Author:Jesper Wilhelmsson
URL:
https://git.openjdk.java.net/jdk/commit/8401a059bd01b32e3532f806d3d8b60e851c468a
Stats: 119 l
On Mon, 13 Dec 2021 23:14:43 GMT, Coleen Phillimore wrote:
> This change makes VM_Version_Ext part of VM_Version (the platform dependent
> part) and moves some duplicated code. x86 had the most code in
> VM_Version_Ext, so the most code moved there. There might be some unneeded
> functions bu
ArrayTypeImp::newInstance() was returning false instead of true for one error
condition, resulting in a failure to send a reply packet containing the error.
See the bug description for details.
-
Commit messages:
- ArrayTypeImp::newInstance() should always return true, even if ther
SA had a bunch of vtable related code that searched for the vtable pointer of a
hotspot object in a few places. This was all related to weird ways that Solaris
would store the vtable pointer. In the case of
https://bugs.openjdk.java.net/browse/JDK-8269830, this extra vtable searching
code intro
21 matches
Mail list logo
