Open engnatha opened 1 year ago
@engnatha can you try with 2.16.0.dev7 or higher? (Preferably 2.16.0rc1). This sounds like a bug @stuhood fixed.
We still found this issue in the 2.17.0rc1_py39
Here are the logs:
timestamp: 2023-07-08T05:13:43.183791
process title: pantsd [/var/lib/buildkite-agent/builds/buildkite-agent-rippling-main-tests-batches-green-stack-i-01ab64de5614ee8b9-1/rippling/rippling-main-pr-tests]
sys.argv: ['/var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.17.0rc1_py39/bin/pants', '--pants-bin-name=./pants', '--pants-version=2.17.0rc1', '--spec-files=changed-files.txt', 'test-selection-method', '--output-file=selection-method.txt']
pid: 32055
Signal 15 (SIGTERM) was raised. Exiting with failure.
File "/var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.17.0rc1_py39/bin/pants", line 8, in
Fatal Python error: Aborted
Thread 0x00007fbc3b77f680 (most recent call first):
Describe the bug I can run the following command and the pants logs look great and everything happens fast.
If I add
--level=error
to the last command to change the log level, I get exceptions in the pants logs.Unfortunately, no amount of
RUST_BACKTRACE=1
setting in my environment was able to show the full details (maybe an issue with xargs?).Both variants of the command produce the same result, but the latter causes some performance issues since it kills something for pants (maybe the daemon?).
Pants version 2.15.0
OS Ubuntu 20.04
Additional info Here are the logs when the command throws the error.