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
8202932: java/awt/Component/NativeInLightShow/NativeInLightShow.java fails #6056
Conversation
|
Webrevs
|
@@ -24,70 +24,69 @@ | |||
/* | |||
@test 1.0 04/05/20 | |||
@key headful | |||
@bug 4140484 | |||
@bug 4140484 8202932 |
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.
BTW it is not necessary to update bugid for the simple cleanups, this is for the bugs which can be verified by this test, or for some big logic rework in the test. So for every next test update, it will be easy to check that the old bugs still can be verified by the updated test. In the current case it is clear that the test should fail before 4140484 was fixed.
Did you check the possibility to verify JDK-4140484, I think it should be possible but just in case. |
Original test cases from JDK-4140484 description are still have no issues. Hundreds of runs of this test on mach5 has not a single failure(nor before nor after modification) However I've added delay after setVisible() call for extra safety. |
Please clarify, did the updated test fail before that fix, and pass after? |
Unfortunately I could not find a correct repo location for jdk6 containing the original fix changeset. All I've found is a bunch of mercurial repos IIRC it should be something other than mercurial(SVN or smth else), but still have no idea where to find it. The fix proposed in JDK-4140484 comments is too far away from current code. |
It was fixed in jdk6 but reported for the early release, so probably it can reproduce the bug in jdk5? |
Yes, it is reproducible with jdk1.5, and not reproducible with jdk1.6 at least on Windows(jdk1.5 on Linux won't launch) |
@azvegint 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 89 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.
|
/integrate |
Going to push as commit 7cf68b1.
Your commit was automatically rebased without conflicts. |
Looks like the test does not fail anymore.
However some cleanup was made:
setAutoDelay()
call (no key/mouse key events generated)Testing still green.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6056/head:pull/6056
$ git checkout pull/6056
Update a local copy of the PR:
$ git checkout pull/6056
$ git pull https://git.openjdk.java.net/jdk pull/6056/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6056
View PR using the GUI difftool:
$ git pr show -t 6056
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6056.diff