Giters

actions / runner-images

GitHub Actions runner images

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

(X) This check failed - sometimes happens on macOS runner

tysonite opened this issue · comments

commented

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

image

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

  • macOS 10.15
  • Ubuntu 16.04 LTS
  • Ubuntu 18.04 LTS
  • Windows Server 2016 R2
  • Windows Server 2019
commented

Hello, it was related to temporary issue with our backend. It should be resolved for now.
Could you please double check?

commented

Hello everyone, thank you for your report.
It is known problem with our backend and we are working to fix it and deploy the fix.
I will post update as soon as I have it

commented

Still running into this

commented

Can you share any estimates when this might be resolved please?

commented

Hello @tysonite !
This issue is still being investigating and unfortunately, we can't provide any ETA for now. We will post update as soon as we have it.
How often do you see repro for this issue?

commented

Duplicate of #969? Already resolved for me now at least.

commented

@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.

commented

Hello everyone, just re-post update from different thread: #736 (comment) .
Sorry for inconvenience.

commented

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

commented

@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
We'll continue investigation

2020-06-21T06:53:29.0057556Z ##[section]Starting: Request a runner to run this job
2020-06-21T06:53:29.8506380Z Can't find any online and idle self-hosted runner in current repository that matches the required labels: 'macos-latest'
2020-06-21T06:53:29.8506421Z Can't find any online and idle self-hosted runner in current repository's account/organization that matches the required labels: 'macos-latest'
2020-06-21T06:53:29.8506450Z Found online and idle hosted runner in current repository's account/organization that matches the required labels: 'macos-latest'
2020-06-21T06:53:29.9640234Z ##[section]Finishing: Request a runner to run this job
commented

@cytopia actually there are some logs in View Raw Logs tab

I probably did not express that very well. Logs are generally available for all jobs that succeeded. There are however now logs for the one that has been cancelled - only logs for everything before that.

commented

Re-post to this issue: we have done some improvements for this recently.
Could you please let us know if you still see the same issues (fix was deployed yesterday)

commented

We're getting this issue and also The request: X was abandoned due to an infrastructure failure. Notification of assignment to a runner was never received. over at https://github.com/FirebaseExtended/flutterfire/actions/runs/175866454

image

commented

@caixw @zhanghongtong apologies for the delay looking, is the issue still occurring?

commented

@TobKed, @Salakar, @tysonite, @cytopia, @mratsim (and others I might have missed) - sorry for the delay. are your projects still experiencing this issue? We've done some work to minimize the cases where this can happen, note that this happens when sometimes the runner running your workflow stops communicating with the service so logs and other artifacts might become unavailable.

commented

Hi, @alepauly
For me, this issue has not happened again, thank you

commented

@alepauly, somehow strangely failed just yesterday. However not sure if it is related to this issue.

commented

@alepauly, somehow strangely failed just yesterday. However not sure if it is related to this issue.

Thanks @tysonite, we'll look into it and let you know.

commented

This is happening for me as well, for the past two days.

commented

@tysonite, the run you link seems to be a different problem - we'll dig a bit deeper to see what happened.

This is happening for me as well, for the past two days.

@nuttycom do you mind sharing run url so we can check?

commented

Thanks @alepauly, for me, this issue has not happened again.

commented

I feel #736 has been closed too early as it still happens, e.g. : https://github.com/robotframework/robotframework/runs/1230597278

commented

I'm seeing the same issue over on our side: https://github.com/apache/maven/runs/1232918625 which occurred yesterday.

commented

This is still happening quite frequently in this two days

commented

This is still happening quite frequently in this two days

@shwuhk macos only? can you link an instance so we can look?

commented

Hi @leseb, I believe the failure you encountered was due to this incident which happened yesterday.

commented

I'm also seeing this a lot recently, but only for macOS 11 - macOS 10.15 mostly seemed fine ever since I started using it in July 2020.

I added macOS 11.0 in November 2020, and it worked fine for a while, but since a couple of weeks it causes enough builds to fail that I'll need to disable it for now.

commented

Just wanted to chime in as well, I've been seeing a lot of these errors on my project, as seen in this PR: pypa/cibuildwheel#484 .

Also reported at https://github.community/t/macos-11-0-big-sur-builds-stalling-out/153761

commented

Struggling with the same problem for a long time with macOS bigsur CI, all it says is "This check failed".
https://github.com/strawberrymusicplayer/strawberry/runs/1672059215

commented

For people Googling this issue, as of today macos-11.0 is not generally available as mentioned in #2486 and in the docs.

So for now you should use macos-latest or macos-10.15.

commented

All macos-latest run into This check failed at April 1st.

commented

All macos-latest run into This check failed at April 1st.

same here.... 😬

commented

@GoodManWEN @k-hench We're experiencing service degradation at the moment, sorry for the inconvenience, it should be resolved shortly

commented

FYI, we're hitting this - please queue for resolution :)

commented

Just ran into it as well

commented

I also got this error. Wait I just got it now and I keep re-running jobs and nothing happen. I tried to delete repository and make new and nothing happen (maybe it will be fixed)

commented

We had some infrastructure issues on Friday, which are resolved by now.

commented

Not only macos, but all jobs return this message This check failed
Trouble happen in a private repo of a PRO account.
image

commented

Team, I get the same issue now. Please resolve it

commented

@bhargav55 it was GitHub outage on Friday. Should be resolve by now

commented

This is happening again to our environment: https://github.com/ABenatti/network_symmetry (private repo)

commented

still happening

commented

Same issue

commented

Make sure you are using runs-on: macos-latest, if the tag is wrong you'll get this same nonsensical error.

commented

We have experienced this on Ubuntu jobs as well: https://github.com/sillsdev/TheCombine/runs/3263385677

Screenshot 2021-08-06 113747

commented

@johnterickson there was an issue with the pipelines at that time.
I'm going to close the issue as the occurrences are intermittent now and there shouldn't be any global issues.

commented

still happens
Screen Shot 2021-08-10 at 8 59 45 PM

commented

Still occasionally happens on ubuntu-18.04

commented

This check failed error occured for me when my monthly Github Actions quota was over, so check your emails to see the quota reset date, GitHub Actions will work fine from that date.

commented

Hi Team, I am facing a This check failed issue. Please resolve it.

commented

Hi Team, I am facing a This check failed issue. Please resolve it.

Try checking your Github Actions quota from Settings > Billing & Plans, if it's full, wait till it renews.

commented

Hi Team, I am facing a This check failed issue. Please resolve it.

Try checking your Github Actions quota from Settings > Billing & Plans, if it's full, wait till it renews.

I have checked. it is not full but still getting an error

Screen Shot 2021-11-05 at 3 56 13 PM

commented

Having the same issue

commented

Having the same trouble.

commented

issue is back, Tests are not running using ubuntu-latest

commented

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).

commented

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.