Mac x64 test failure: java/lang/management/MemoryMXBean/LowMemoryTest2.sh
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Related to: #157
Described in detail by: [JDK-8209743](https://bugs.openjdk.org/browse/JDK-8209743) (test framework problem)
_Note: The fix for this issue was not backported to JDK11_
Here's the results of the run without altering the test on our end:
[jdk_management_0.tar.gz](https://github.com/adoptium/aqa-tests/files/14102466/jdk_management_0.tar.gz)
Here's the results of the run after applying the 'band-aid' of increasing memory to 24m:
[jdk_management_0.success.24m.tar.gz](https://github.com/adoptium/aqa-tests/files/14102465/jdk_management_0.success.24m.tar.gz)
Since the conclusion of the JDK TESTBUG is:
> In conclusion, this is a test bug. Increasing the metaspace space size can change the proportion (class and non-class allocation types) of the meta space usage and allow the test to pass, although it is not a real fix to the test issue.
...the fix on the Microsoft end will likely be to problemlist it.
Contributor guide
Research direction
Start with java/lang/management/MemoryMXBean/LowMemoryTest2.sh and review JDK-8209743 alongside the attached passing and failing run results. Confirm the JDK11 Mac x64 behavior, then update the relevant problem list so the test is excluded rather than changing its memory settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100