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

deep_random.json Interop test goes OOM #187

Open
OtaK opened this issue Mar 16, 2024 · 0 comments
Open

deep_random.json Interop test goes OOM #187

OtaK opened this issue Mar 16, 2024 · 0 comments

Comments

@OtaK
Copy link

OtaK commented Mar 16, 2024

Hi,

I tried a test run of the interop deep_random.json test and it OOMs pretty reliably after taking more than 30GB of RAM:

5006   │ Mar 16 15:07:21 localhost kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=3,mems_
       │ allowed=0,global_oom,task_memcg=/docker/f86b435b10037000fe30a62a0137bd84e5a7aa7a6ff0411fc980dd6dfee6
       │ ff42,task=test-runner,pid=12491,uid=1000
5007   │ Mar 16 15:07:23 localhost kernel: oom_reaper: reaped process 12491 (test-runner), now anon-rss:3172k
       │ B, file-rss:0kB, shmem-rss:0kB

Here's the command I use to run it:

docker compose run spec-runner -suite 1 -client c1:50875 -client c2:50052 -config=../configs/deep_random.json | jq '[.scripts[][] | select(.error) | {cs: .cipher_suite, actors: .actors,error: .error,failed_step: .failed_step,failed_step_json: .failed_step_json | fromjson}]'

Seems like the Go GC isn't doing its job there, what can we do to allow it to run?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant