-
Bug
-
Resolution: Fixed
-
P4
-
11, 13, 14
-
b07
-
x86
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8228797 | 13.0.2 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
| JDK-8229071 | 13.0.1 | Matthias Baesken | P4 | Resolved | Fixed | b05 |
| JDK-8228483 | 13 | Matthias Baesken | P4 | Resolved | Fixed | b31 |
| JDK-8335538 | 11.0.25-oracle | Ramesh Gangadhar | P4 | Resolved | Fixed | b01 |
| JDK-8228893 | 11.0.5 | Matthias Baesken | P4 | Resolved | Fixed | b02 |
On Windows (especially on slower virtualized machines) the langtools test tools/sjavac/IdleShutdown.java shows sporadic failures.
The error we see is :
IdleShutdown.java: java.lang.AssertionError: Error too big
Reason is that the "timeout error" is larger than the allowed error of 300 ms :
if (error > TIMEOUT_MS * .1)
throw new AssertionError("Error too big");
We see sometimes errors in the range of 300-900 ms .
For example :
After 16166 ms: Timeout error: 609 ms
Idea is to increase the allowed timeout error to make the test more stable.
The error we see is :
IdleShutdown.java: java.lang.AssertionError: Error too big
Reason is that the "timeout error" is larger than the allowed error of 300 ms :
if (error > TIMEOUT_MS * .1)
throw new AssertionError("Error too big");
We see sometimes errors in the range of 300-900 ms .
For example :
After 16166 ms: Timeout error: 609 ms
Idea is to increase the allowed timeout error to make the test more stable.
- backported by
-
JDK-8228483 tools/sjavac/IdleShutdown.java fails with AssertionError: Error too big on windows
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-