jdk17+: java/util/regex/NegativeArraySize.java intermittently failed on linux-all
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
jdk17: java/util/regex/NegativeArraySize.java intermittently failed on linux-x64
https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_sanity.openjdk_x86-64_linux/187/console
```
08:49:33 ACTION: testng -- Failed. Unexpected exit from test [exit code: 137]
08:49:33 REASON: User specified action: run testng/othervm -Xms5G -Xmx5G NegativeArraySize
08:49:33 TIME: 8.376 seconds
08:49:33 messages:
08:49:33 command: testng -Xms5G -Xmx5G NegativeArraySize
08:49:33 reason: User specified action: run testng/othervm -Xms5G -Xmx5G NegativeArraySize
08:49:33 Mode: othervm [/othervm specified]
08:49:33 elapsed time (seconds): 8.376
```
History shows it only happened to [test-docker-ubuntu1804-x64-1](https://ci.adoptopenjdk.net/computer/test-docker-ubuntu1804-x64-1)
https://trss.adoptium.net/deepHistory?testId=62b8b5d7250c3c428c48a119
Rerun 10X, didn't reproduce.
https://ci.adoptopenjdk.net/job/Grinder/5073/
Contributor guide
Research direction
Start with java/util/regex/NegativeArraySize.java and the linked CI console output, then compare the test history for test-docker-ubuntu1804-x64-1. The Grinder rerun did not reproduce the failure; done means identifying the cause of the intermittent exit code 137 and verifying the test no longer fails unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100