Closed mwisner closed 2 years ago
@mwisner Hi! could you provide a link to the real workflow runs?
HI @mikhailkoliada,
Thank you for reviewing this issue... Sadly this is a private repo, so I am not sure how to provide the link.
It seems like our issues were resolved. Not sure what happened to be honest but ran them again a few hours later and they started working again. Appreciate you reviewing this issue either way!
This seems like still happening here. https://github.com/mdvip/middleware/actions/runs/5348462958 Can anyone take a look?
we are having the same issue
Likewise:
github#L1 GitHub Actions has encountered an internal error when running your job.
What deployed yesterday, fails today.
Seven hours later...
Restarted the failed release and we have successfully deployed.
Totally unrelated to this particular runner image, but seems Google is bringing us all here. We're having the same issues since around 11:30am EST today June 22, 2023. In our case it's only jobs with concurrency constraints that are failing. I've had a ticket open for a few hours, but no response yet. Also nothing on https://www.githubstatus.com/ yet.
Github says the issues are fixed.
Yes this is an ever occurring issue at GitHub and they typically just ignore your support request OR make you run in circles around checking your workflow, settings and debug logging for a pipeline thats worked several times before and has had no changes and then magically Poof! The issue resolves itself through no action on your part
Microsoft GitHub Actions support is a scam and the team have the integrity of a gnat.
Just get used to it.. nice platform and great service but accountability and reliability are not part of the GH core values 🤷♂️
Description
Hi,
Within the past few days one specific repo of ours has started receiving:
Before this, our workflows ran flawlessly for at least the past year, and we have many other repos that have had no issues
I've created a very basic workflow:
Within the repo in question, this workflow, along with all the other workflows fail. Things I've tried:
runs-on
tomacos-latest
,ubuntu-22.04
etc... (The same result)Is there anything repo-specific that would cause this error?
Note: We are using GH enterprise cloud.
I'm at a bit of a loss here.... Any help or recommendations would be much appreciated.
Platforms affected
Virtual environments affected
Image version and build link
ubuntu-latest
Is it regression?
yes
Expected behavior
runs
Actual behavior
Error: GitHub Actions has encountered an internal error when running your job.
Repro steps
n/a.