-
-
Notifications
You must be signed in to change notification settings - Fork 437
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
Process hangs in Github workflows with coverage 7.1.0/7.0.5 #1559
Comments
I've run the test command through
The full log is 98MB and too large for Github - if earlier output is relevant, I can send it if needed. |
The CI pipeline is hanging - see nedbat/coveragepy#1559 for details. Disabling coverage.py completely for now at least let's us run tests for ongoing work.
We managed to narrow it down to the use of |
Closing this as we're fairly certain it can be pinned to a regression from Python 3.10.9 to 3.10.10, see python/cpython#102126 |
Describe the bug
Similarly to #1310, the coverage process seems to hang on Github Workflow actions/jobs when running tests.
This has started occurring over the weekend, and from what I can see it looks like the Github runner version was recently changed and Python 3.10.10 became available. See also actions/runner#2454
To Reproduce
Reproducing this seems hard - so far I haven't been able to reproduce this on my local machine (admittedly, not Ubuntu 22.04 either so probably comparing apples and oranges).
This is occurring in the https://github.com/open-formulieren/open-forms repository, on all branches/PRs. A job that was passing before but was re-run now also fails without any changes made to our code (so only Github infrastructure can have changed).
pip freeze
is helpful. -> See https://github.com/open-formulieren/open-forms/blob/09e724bf9d60451cb3dc2f260ca00890eee9afe0/requirements/ci.txt-> The coverage run invocation never seems to exit.
coverage
at all makes the problem go away: commit and CI runcoverage run src/manage.py test src --exclude-tag=e2e
(removed the--parallel
and multiprocessing options) -> problem persistcoverage combine
but keptcoverage run
- problem persistsExpected behavior
coverage run
exits, both with and without multiprocessing mode.Additional context
Per #1310 I've also enabled some debug logging:
COVERAGE_DEBUG=process,pid
. The output from that is taken from this run-> the job timed out after the configured 30 minutes. Normally these tests (in parallel) complete in under 10 minutes.
edit: I seem to be able to reproduce this using https://github.com/nektos/act, let's see if I can find a minimum reproducible example
The text was updated successfully, but these errors were encountered: