-
Notifications
You must be signed in to change notification settings - Fork 740
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
jdk_util_1 sun/util/calendar/zi/TestZoneInfo310.java.TestZoneInfo310 RuntimeException on AIX with -Xgcpolicy:balanced #19367
Comments
We'll have to figure out if it's a gc or jit issue. |
The reason for failure might be unexpected using of Arraylet (by JIT). We can check this by specifying region size large enough, for example 128m |
I couldn't reproduce it on amac. Attempting to capture a system core when the exception is thrown. |
Issue eclipse-openj9/openj9#19367 Signed-off-by: Peter Shipton <[email protected]>
Creating a system dump on RuntimeException is not feasible. There are too many tests throwing this exception and the file system is filled up, plus the resulting diagnostics would be too big. I've modified the test to throw a different exception, which may be more viable. https://openj9-jenkins.osuosl.org/view/Test/job/Grinder/3524/ - passed |
Issue eclipse-openj9/openj9#19367 Signed-off-by: Peter Shipton <[email protected]>
This seems like a scenario where when we add Reproduce failure |
I can't cause the failure any more. Last reproduced in https://openj9-jenkins.osuosl.org/view/Test/job/Grinder/3516/ Perhaps because of my modification to the test, replacing RuntimeException with, in this case, java.time.DateTimeException. More grinders without this update. Reproduce failure For the record, the test that fails with |
Doesn't seem like any of the changes would have fixed the failure, but it's not reproducible any more on the latest build. |
internal link
sun/util/calendar/zi/TestZoneInfo310.java
Same issue in JDK11, 17 and 21 AIX.
The test passed without
-Xgcpolicy:balanced
on JDK21 AIX (link)The text was updated successfully, but these errors were encountered: