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

One of the test processes running forever #947

Open
bustikiller opened this issue Apr 17, 2024 · 1 comment
Open

One of the test processes running forever #947

bustikiller opened this issue Apr 17, 2024 · 1 comment

Comments

@bustikiller
Copy link

First thing first, thanks for this awesome project. It's been working pretty good for me for some time.

I'd like to report a situation I've been facing over the past weeks. I'm using GitHub Actions with 2 CPUs to run the tests, which splits the test suite into two groups of tests. However, I've seen that one of the groups finishes in a timely manner, while the other one:

  • Sometimes finishes approximately at the same time as the first group. Everything is good in this case.
  • Sometimes never ends (and times out after GitHub's default of 6h).

The last traces I can see in the GitHub Action are:

Finished in 11 minutes 3 seconds (files took 18.43 seconds to load)
6790 examples, 0 failures, 42 pending
JSON Coverage report generated for (1/2) to /home/runner/work/[REDACTED]/[REDACTED]/coverage.         36123 / 46854 LOC (77.1%) covered.

In case it's relevant, I'm using https://github.com/paambaati/codeclimate-action to wrap the execution of the tests and report the test coverage to CodeClimate.

Please, let me know if there is any other piece of information that could be useful to debug this issue.

Thanks!

@grosser
Copy link
Owner

grosser commented Apr 19, 2024

hard to tell what is going on, a few ideas to debug:

  • try removing the codeclimate and see if that helps (or print before it sends the report so see if it's stuck there)
  • run with -v or --format doc so you see each test as it executes ... maybe it stops at the same test every time
  • run without parallel and see if you can reproduce the issue
  • run with parallel but with 1 processor and see if you can reproduce the issue

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