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

init-pants intermittent FATAL: exception not rethrown Aborted (core dumped) #19

Open
nickderobertis opened this issue Apr 19, 2023 · 2 comments

Comments

@nickderobertis
Copy link

nickderobertis commented Apr 19, 2023

Hi, first thank you for the helpful actions!

I am trying to use init-pants@main and sometimes it works successfully and other times I get the following output from pants --version:

Run pants --version
Bootstrapping Pants 2.14.1 using cpython 3.9.15
Installing pantsbuild.pants==2.14.1 into a virtual environment at /home/runner/.cache/nce/6621291ed4120fa45607b367abf7786ce496f389f27240712a63c31f1c438c21/bindings/venvs/2.14.1
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 41.7 MB/s eta 0:00:00
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 819.3/819.3 KB 108.8 MB/s eta 0:00:00
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.5/64.5 KB 22.0 MB/s eta 0:00:00
New virtual environment successfully created at /home/runner/.cache/nce/6621291ed4120fa45607b367abf7786ce496f389f27240712a63c31f1c438c21/bindings/venvs/2.14.1.
20:17:51.72 [INFO] Initializing scheduler...
20:17:51.93 [INFO] Scheduler initialized.
2.14.1
FATAL: exception not rethrown
/home/runner/work/_temp/ec994eaa-ce00-453c-936d-273c1589d131.sh: line 1:  1906 Aborted                 (core dumped) pants --version
Error: Process completed with exit code 134.

Considering it is intermittent, the vague nature of the error, the 134 error code, and that it still prints the version, my best guess would be that it is close to a system resource limit. I am not running anything else at the same time.

Is there any way to limit the memory usage? Why would this be exhausting the 7GB actions runner limit?

Let me know if you need additional information. Curious if anyone else is seeing this.

@nickderobertis
Copy link
Author

Perhaps setting process_total_child_memory_usage could help? But it still seems odd that it would be using so much memory just initializing.

@stuhood
Copy link
Member

stuhood commented Apr 20, 2023

Assuming this is what I think it is, the fix(es) were backported to 2.15.0 and greater, but not to 2.14.x: are you able to try upgrading to 2.15.0?

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

No branches or pull requests

2 participants