8339869: [21u] Test CreationTime.java fails with UnsatisfiedLinkError after 8334339

[GoeLin]

Running one test as /othervm makes sure the lib is not loaded twice in the same VM

Testing:
The failure was sporadic, but we saw it in our 4 daily test runs (21u, 21u-dev, 17u, 17u-dev) about once a day. Since adding this fix temporary to the four test setups on September 3rd, we have not encountered the problem again.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8339869 needs maintainer approval

Issue

• JDK-8339869: [21u] Test CreationTime.java fails with UnsatisfiedLinkError after 8334339 (Bug - P4 - Approved)

Reviewers

• Severin Gehwolf (@jerboaa - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u.git pull/453/head:pull/453
$ git checkout pull/453

Update a local copy of the PR:
$ git checkout pull/453
$ git pull https://git.openjdk.org/jdk21u.git pull/453/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 453

View PR using the GUI difftool:
$ git pr show -t 453

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u/pull/453.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back goetz! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@GoeLin This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8339869: [21u] Test CreationTime.java fails with UnsatisfiedLinkError after 8334339

Reviewed-by: sgehwolf

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@GoeLin Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

[mlbridge]

Webrevs

• 00: Full (bba647ae)

[jerboaa]

Seems fine.

[jerboaa]

FWIW, wrong bug in PR title. The JBS issue has it correct.

[GoeLin]

Thanks! Fixed the bugID.

[openjdk]

⚠️ @GoeLin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[GoeLin]

GHA failure: well known ClhsdbFindPC issue, unrelated

[GoeLin]

/integrate

[openjdk]

Going to push as commit 34b4bd4.

[openjdk]

@GoeLin Pushed as commit 34b4bd4.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.