Include GWT version, commit in JFR output#10318
Merged
Merged
Conversation
Enhances the "manual, opt-in analytics" by allowing users to upload JFR dumps of a build and detect which particular version or build resulted in the dump. Deliberately omits command line args at this time - users can leave the default JVM events in place so these are detected or specify them manually. An automatic approach would need more code, able to remove details like paths and module names from the output. Fixes gwtproject#10269 Co-authored-by: Zbynek Konecny <zbynek1729@gmail.com>
zbynek
added
the
ready
zbynek
approved these changes
May 13, 2026
vegegoku
approved these changes
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enhances the "manual, opt-in analytics" by allowing users to upload JFR dumps of a build and detect which particular version or build resulted in the dump.
Deliberately omits command line args at this time - users can leave the default JVM events in place so these are detected or specify them manually. An automatic approach would need more code, able to remove details like paths and module names from the output.
Fixes #10269
Backport #10312