You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
The last traces I can see in the GitHub Action are:
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!
The text was updated successfully, but these errors were encountered: