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
8270609: [TESTBUG] java/awt/print/Dialog/DialogCopies.java does not show instruction #4850
Conversation
|
@lawrence-andrew 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. |
Webrevs
|
@lawrence-andrew This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Commenting to keep the PR open |
The test is semi-automatic: it is able to determine whether it passes or fails depending on whether the number of copies in the print dialog is modified or not. Is it possible to complete the test as soon as either OK or Cancel button is clicked on the Print dialog? |
/label remove awt |
@aivanov-jdk The label
|
@aivanov-jdk The label
|
The Then if the If There's one thing though… I don't have a real printer installed but I have a PDF printer which doesn't allow increasing the number of copies. What should the test do in this case? If I click OK without modifying the number of copies, the test will fail; if I click Cancel, the test will also fail. However, this particular case falls into a category where the prerequisites aren't met. Probably, the standard machinery with |
I rewrote the test case to close the test ui if user click the OK or Cancel button & check for job.getCopies() value and make the testcase pass or fail. |
@lawrence-andrew This change now passes all automated pre-integration checks. 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 670 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) but any other Committer may sponsor as well.
|
/integrate |
@lawrence-andrew |
/sponsor |
Going to push as commit 4da45c4.
Your commit was automatically rebased without conflicts. |
@aivanov-jdk @lawrence-andrew Pushed as commit 4da45c4. |
@shurymury
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4850/head:pull/4850
$ git checkout pull/4850
Update a local copy of the PR:
$ git checkout pull/4850
$ git pull https://git.openjdk.java.net/jdk pull/4850/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4850
View PR using the GUI difftool:
$ git pr show -t 4850
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4850.diff