-
Bug
-
Resolution: Fixed
-
P3
-
10, 11
-
b14
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8233780 | 11.0.7-oracle | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8261026 | 8u301 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8258507 | 8u291 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8262682 | emb-8u291 | Sergey Bylokhov | P3 | Resolved | Fixed | team |
Lots of our automated tests in closed(~300) ws uses some kind of "standard instructions" machinery, which is just a copy pasted code to to show this message to the user:
"This is an AUTOMATIC test, simply wait until it is done."
In most cases it doubles the amount of code in the test, and make it difficult to update such tests.
Looks like not all tests assume that the instruction frame could be opened on top of the test frame, which make the test unstable.
"This is an AUTOMATIC test, simply wait until it is done."
In most cases it doubles the amount of code in the test, and make it difficult to update such tests.
Looks like not all tests assume that the instruction frame could be opened on top of the test frame, which make the test unstable.
- backported by
-
JDK-8233780 Delete "standard instructions" machinery in the closed automated tests
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
(1 links to)