Skip to content

Conversation

egahlin
Copy link
Member

@egahlin egahlin commented Oct 3, 2025

Could I get a review of a test fix that emits events with unique timestamps, so the contextual information is printed in chronological order?

Testing: 500 * jdk/jfr/tool/TestPrintContextual.java

Thanks
Erik


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

Issue

  • JDK-8365630: jdk/jfr/tool/TestPrintContextual.java fails with wrong spanId (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27626

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27626.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 3, 2025

👋 Welcome back egahlin! 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
Copy link

openjdk bot commented Oct 3, 2025

@egahlin 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:

8365630: jdk/jfr/tool/TestPrintContextual.java fails with wrong spanId

Reviewed-by: shade

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 20 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this 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
Copy link

openjdk bot commented Oct 3, 2025

@egahlin The following label will be automatically applied to this pull request:

  • hotspot-jfr

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@egahlin egahlin marked this pull request as ready for review October 3, 2025 21:15
@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 3, 2025
@mlbridge
Copy link

mlbridge bot commented Oct 3, 2025

Webrevs

try {
Thread.sleep(1);
} catch (InterruptedException e) {
// ignore
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why ignore, though? This would make the thread stuck even if someone actively tries to interrupt it. A common practice in these non-critical methods is to restore the interrupt status and return.

} catch (InterruptedException e) {
    Thread.currentThread().interrupt();
    return;
}

Copy link
Member Author

@egahlin egahlin Oct 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The purpose is to save CPU cycles instead of spinning. I'm not sure how returning would help? The test would become unreliable, since two timestamps may be the same.

I could let the method throw an InterruptedException so the test fails, but it would result in a false positive. Perhaps, if jtreg for some reason wanted to shut down the test early, it could serve a purpose.

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks better, thanks!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 6, 2025
@egahlin
Copy link
Member Author

egahlin commented Oct 6, 2025

Thanks for the review.

/integrate

@openjdk
Copy link

openjdk bot commented Oct 6, 2025

Going to push as commit 2376a9e.
Since your change was applied there have been 24 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 6, 2025
@openjdk openjdk bot closed this Oct 6, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 6, 2025
@openjdk
Copy link

openjdk bot commented Oct 6, 2025

@egahlin Pushed as commit 2376a9e.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot-jfr [email protected] integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants