Skip to content
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

LockFreeImmortalSpace is failing in CI #1015

Open
qinsoon opened this issue Nov 4, 2023 · 0 comments
Open

LockFreeImmortalSpace is failing in CI #1015

qinsoon opened this issue Nov 4, 2023 · 0 comments
Labels
P-normal Priority: Normal.

Comments

@qinsoon
Copy link
Member

qinsoon commented Nov 4, 2023

https://www.mmtk.io/ci-perf-result/master/mutator_history.html shows the results for both nogc plans using LockFreeImmortalSpace are 0. In the log, it panics with

thread '<unnamed>' panicked at 'Out of virtual address space at 0x40000000 (0x1f400040000000 > 0x800000000)', /home/gitlab-runner/actions-runner/_work/mmtk-core/mmtk-core/mmtk-openjdk/repos/mmtk-core/src/util/heap/heap_meta.rs:27:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5

I guess it might be related with compressed pointer.


LockFreeImmortalSpace was not running properly in our CI. It was built with LockFreeImmortalSpace, but was actually running the default plan (probably since the beginning), which was a mistake in the CI script. There were also some issues with LockFreeImmortalSpace so it did not actually run. but the issues were identified and fixed in #1003. When we moved to running-ng in our CI (#1005), the run configs for nogc plans are fixed. So those plans with LockFreeImmortalSpace are benchmarked properly, but the runs failed with the error message above.

@k-sareen k-sareen added the P-normal Priority: Normal. label Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-normal Priority: Normal.
Projects
None yet
Development

No branches or pull requests

2 participants