-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
(X) This check failed - sometimes happens on macOS runner #841
Comments
Hello, it was related to temporary issue with our backend. It should be resolved for now. |
It looks like that it still happens: https://github.com/robotframework/robotframework/runs/673835994?check_suite_focus=true |
Hello everyone, thank you for your report. |
This seems to still be happening: https://github.com/SciNim/vectorize/pull/1/checks?check_run_id=723528967 |
Still running into this |
Can you share any estimates when this might be resolved please? |
Hello @tysonite ! |
Duplicate of #969? Already resolved for me now at least. |
@MaksimZhukov, I don't see for a couple of days that checks fail without a reason. Previously, this was very often. However, now checks get canceled unexpectedly (see here) - note that no one cancel them. |
Hello everyone, just re-post update from different thread: #736 (comment) . |
* Github Action CI (without GMP) * Deactivate MacOS, spurious failures: actions/runner-images#841 * force install with nimble * Add badge * Don"t include Nim 1.2.x #20 (comment) * Action branch mistake * Add back OSX? actions/runner-images#841, actions/runner-images#969 * fix MacOS target * comment out RDTSC on i386 * Add initialization canaries * Add more verbose output to debug windows failures * spurious windows i386 test * For now only activate Linux and mac * missed include
I can also confirm that jobs on MacOS are cancelled for no apparent reason: https://github.com/cytopia/pwncat/pull/80/checks?check_run_id=792119613 Additionally to say there are not logs or other info regarding why it had been cancelled |
@cytopia actually there are some logs in View Raw Logs tab https://pipelines.actions.githubusercontent.com/97gHSubSPCyarCaLrsiRsUG8bxJdfozAtomOlAWZ9DDbFzHfno/_apis/pipelines/1/runs/6283/signedlogcontent/3?urlExpires=2020-06-22T08%3A05%3A18.6503439Z&urlSigningMethod=HMACV1&urlSignature=HddomSJ2KiiXdKQt%2F5tN18vmqBQgbb4ooo5ojjrwQcI%3D
|
Team, I get the same issue now. Please resolve it |
@bhargav55 it was GitHub outage on Friday. Should be resolve by now |
This is happening again to our environment: https://github.com/ABenatti/network_symmetry (private repo) |
still happening |
Same issue |
also experiencing this in https://github.com/hexops/mach |
Make sure you are using |
We have experienced this on Ubuntu jobs as well: https://github.com/sillsdev/TheCombine/runs/3263385677 |
@johnterickson there was an issue with the pipelines at that time. |
Still occasionally happens on |
|
Hi Team, I am facing a |
Try checking your Github Actions quota from Settings > Billing & Plans, if it's full, wait till it renews. |
Having the same issue |
Having the same trouble. |
issue is back, Tests are not running using |
Having the same issue on self-hosted runners. Most often is happening on one of four matrixed jobs (all running in same env, just using matrix to provide unique seeds). |
actually found the issue. For self-hosted runners this is likely a problem with setting up the working directory, and in the "annotations" field of your actions summary, you'll see something like "access denied for ". In my case I had a typo in the workdir path when I registered the runner. |
We have the same issue, example run https://github.com/simulationcraft/simc/runs/5757150459?check_suite_focus=true |
Running into this issue as well: https://github.com/SwiftyLab/AsyncObjects/runs/7742876202?check_suite_focus=true |
Sometimes, only "(X) This check failed" message appears on the output for a particular macOS run, example is here: https://github.com/tysonite/robotframework/runs/650302841?check_suite_focus=true
This error message does not include other information to get details of what's going wrong in case it is not internal Github Actions issue. On the other hand, I expect it to do not happen.
Virtual environments affected
The text was updated successfully, but these errors were encountered: