Fix client UUID printing in verbose log #10209
Merged
Conversation
This file contains 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
On the client-side, the uuid appeared truncated to 32 bits, as described in eclipse-openj9#9962. This is due to custom OMR print function and `PRI` format specifiers not interacting correctly. Fix it by using `%llu` specifier instead of `%OMR_PRIu64`. Signed-off-by: Dmitry Ten <Dmitry.Ten@ibm.com>
mpirvu
approved these changes
Jul 24, 2020
|
jenkins test sanity xlinuxjit jdk11 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On the client-side, the uuid appeared truncated
to 32 bits, as described in #9962.
This is due to custom OMR print function and
PRIformat specifiers not interacting correctly.
Fix it by using
%lluspecifier instead of%OMR_PRIu64.