-
Notifications
You must be signed in to change notification settings - Fork 6.2k
JDK-8333360 : PrintNullString.java doesn't use float arguments #19540
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 rkannathpari! A progress list of the required criteria for merging this PR into |
|
@Renjithkannath 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 102 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@aivanov-jdk, @kumarabhi006, @alisenchung) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@Renjithkannath The following label will be automatically applied to this pull request:
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. |
|
/integrate |
|
@Renjithkannath |
|
|
||
| try { | ||
| g2d.drawString(emptyIterator, 20, 180); | ||
| g2d.drawString(emptyIterator, 20.0f, 180.0f); |
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.
Does the line below also need to change ?
g2d.drawString("FAILURE: No IAE for empty iterator, float", 20.0f 180.0f);
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.
No, it does not. It may though.
The test declares it verifies drawString(Iterator, float, float) — the test does it now. How the error message is output on the screen isn't important: either int or float version will do the same thing.
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.
@aivanov-jdk Thank you for clarification.
kumarabhi006
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.
Ran the updated test and looks good to me.
alisenchung
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.
Maybe outside the scope of this issue, but could this test be automated?
I've been thinking about it, too. No, it can't be automated completely: the tester has to click Print / OK button in the Print dialog. Yes, other aspects of the test can be automated. The test code already detects a failure and reports it on the screen or on paper, thus the test can fail automatically if a failure condition is found. However, the first part where it paints on the screen can be fully automated. It could be moved to an independent test. These improvements to the test can be combined with fixing JDK-8333026, or the test can be updated separately. I'll submit a new bug to track this activity. Thank you for bringing it up. |
alisenchung
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.
small typo and typing change, LGTM
|
/sponsor |
|
Going to push as commit aaaa86b.
Your commit was automatically rebased without conflicts. |
|
@aivanov-jdk @Renjithkannath Pushed as commit aaaa86b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I've submitted JDK-8334016: Make |
Hi Reviewers,
I have updated the test case with passing float value for evaluation and a typo. Please review and let me know your suggestions if any.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19540/head:pull/19540$ git checkout pull/19540Update a local copy of the PR:
$ git checkout pull/19540$ git pull https://git.openjdk.org/jdk.git pull/19540/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19540View PR using the GUI difftool:
$ git pr show -t 19540Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19540.diff
Webrev
Link to Webrev Comment