adoptium / adoptium/run-aqa

System test TestJlmRemoteMemoryAuth_0 failed with hotspot jdk8 on Macos

Open
#67 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
4
Forks
27
Avg merge
2d 9h
Merged PRs (30d)
8

Description

System test TestJlmRemoteMemoryAuth_0 failed with hotspot jdk8 on Macos from Jan 8th.

```
CL2 stderr j> 2021/01/12 01:38:53.213 Peak usage smaller than current usage here:
CL2 stderr j> 2021/01/12 01:38:53.214 Memory Pool: Code Cache
CL2 stderr j> 2021/01/12 01:38:53.214 Memory Type: NON_HEAP
CL2 stderr j> 2021/01/12 01:38:53.214 Peak Usage: init = 2555904(2496K) used = 21268800(20770K) committed = 21430272(20928K) max = 251658240(245760K)
CL2 stderr j> 2021/01/12 01:38:53.214 Current Usage: init = 2555904(2496K) used = 21288384(20789K) committed = 21430272(20928K) max = 251658240(245760K)
CL2 stderr Exception in thread "main" java.lang.AssertionError: Peak Usage used memory smaller than Current Usage used memory
CL2 stderr at org.junit.Assert.fail(Assert.java:88)
CL2 stderr at net.adoptopenjdk.test.jlm.resources.MemoryData.checkPeakAndCurrentMemoryUsage(MemoryData.java:521)
CL2 stderr at net.adoptopenjdk.test.jlm.resources.MemoryData.writeData(MemoryData.java:401)
CL2 stderr at net.adoptopenjdk.test.jlm.remote.MemoryProfiler.getStatsViaServer(MemoryProfiler.java:251)
CL2 stderr at net.adoptopenjdk.test.jlm.remote.MemoryProfiler.main(MemoryProfiler.java:112)
STF 01:38:53.575 - **FAILED** Process CL2 ended with exit code (1) and not the expected exit code/s (0)
STF 01:38:53.575 - Monitoring Report Summary:
```

Both in github runner and AdoptOpenjdk:
https://github.com/AdoptOpenJDK/run-aqa/runs/1684000536?check_suite_focus=true
https://ci.adoptopenjdk.net/view/Test_system/job/Test_openjdk8_hs_sanity.system_x86-64_mac/405/consoleFull

@lumpfish @Mesbah-Alam any idea?

Contributor guide

Open the contributing guide

Research direction

Run TestJlmRemoteMemoryAuth_0 with HotSpot JDK 8 on macOS and review the linked runner logs. Start at MemoryData.checkPeakAndCurrentMemoryUsage and follow its call path from MemoryProfiler.getStatsViaServer, focusing on the Code Cache peak and current values. Done means the test completes with the expected exit code 0 on the affected environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.