Getting kill signal during Actions CI
See original GitHub issueDescription: Hi,
I am getting a weird kill signal error when performing CI for this PR with the following error [ref]:
pytest --cov=. --cov-report=xml
shell: /usr/bin/bash -e {0}
env:
pythonLocation: /opt/hostedtoolcache/Python/3.7.12/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.7.12/x64/lib
============================= test session starts ==============================
platform linux -- Python 3.7.12, pytest-7.0.1, pluggy-1.0.0
rootdir: /home/runner/work/GaNDLF/GaNDLF
plugins: cov-3.0.0
collected 30 items
/home/runner/work/_temp/0dbe16bb-3052-4a6e-9755-00561fed9f22.sh: line 1: 2930 Killed pytest --cov=. --cov-report=xml
testing/test_full.py .......
Error: Process completed with exit code 137.
I have also tried updating setup-python
to v3.0.0
but I am getting the same error. Any help would be greatly appreciated!
Action version: 2 and 3
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Tools version:
Python 3.7
Repro steps:
- Repo: https://github.com/CBICA/GaNDLF
- Workflow: https://github.com/CBICA/GaNDLF/blob/master/.github/workflows/python-test.yml
- PR in question: https://github.com/CBICA/GaNDLF/pull/327
Expected behavior: The weird thing is that no other PR for this repo is getting affected [1,2,3], and the error is coming when pytest is collecting tests, not when it is executing them. I am able to run the tests without issue on my local machine.
Actual behavior: The CI build is failing while trying to collect the targets for pytest.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
CI or CD process does not receive SIGTERM on termination
When the CI job is cancelled on the Web UI, the job process doesn't receive the SIGTERM signal. 10 minutes later SIGKILL is...
Read more >GitHub Actions randomly kill a test program - help
gets randomly killed with SIGKILL (signal 9) when I run it from a Rust testsuite. I can't reproduce it on macOS by hand,...
Read more >kill() — Send a signal to a process - IBM
You can use either signal() or sigaction() to specify how a signal will be handled when kill() is invoked. A process can use...
Read more >When is mandatory send SIGINT programmatically?
The default action of both SIGINT and SIGTERM (as well as that of many other signals) is to terminate the process. That's documented...
Read more >Sending Signals in C? - linux - Stack Overflow
Per POSIX-1.2017 General Information §2.4.3 Signal Actions , a signal may have one of three different dispositions or "actions taken" when ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The commit I mentioned fixed this error on our end. Unsure if it fixed the actual issue or just the symptom but since we did not face it afterwards, we have not explored further. All the best!
Oh, no, I have fixed it. Thanks!