-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8273361: InfoOptsTest is failing in tier1 #5381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
I'm not a Reviewer, nor an expert in this area, but this change looks OK to me. |
|
Thanks for review, @jaikiran. Any formal Reviewer wants to chime in? Would be nice to get GHA all green again. |
|
@shipilev 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: 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 29 new commits pushed to the
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 |
|
It would seem better to me if the test didn't depend on hardcoded localized strings (e.g. by printing the content of e.g. |
Oh, I like that idea. See new commit. |
lahodaj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
|
GHA checks are green, I am integrating. /integrate |
|
Going to push as commit 267c61a.
Your commit was automatically rebased without conflicts. |
Current test checks that informational messages are not printed twice. The failing tests verifies that by checking
java.specification.versionis not present twice in the version string. Effectively, it searches for18. But a second18could get to version string from anywhere: the Git hash, the user name, etc. It is failing in current GHA due to Git hash containing18.I believe the test should be more conservative: look for more unique strings, and check that the lines start with it. "javac" and "javac full version" seem unique enough. Checking that lines start with "javac" handles the case of accidental version strings that includes that string (think username that includes "javac" for some reason, who are we to judge...).
Additional testing:
--with-version-opt=javacProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5381/head:pull/5381$ git checkout pull/5381Update a local copy of the PR:
$ git checkout pull/5381$ git pull https://git.openjdk.java.net/jdk pull/5381/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5381View PR using the GUI difftool:
$ git pr show -t 5381Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5381.diff