Replies: 5 comments 1 reply
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
I just tried to
🤔 |
Beta Was this translation helpful? Give feedback.
-
Using the same exact .config I used the first time works now and I see it registered in the org actions runner list. I wonder if there is a timing issue/race condition here with registering actions runners at the same time for the same repo/workflow run? |
Beta Was this translation helpful? Give feedback.
-
It has become less frequent. It now takes probably 30 runs to catch the issue. However, it still happens as of this AM. |
Beta Was this translation helpful? Give feedback.
-
Latest one... Still a problem
|
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
I'm creating actions runners on demand for my workflows and register them to the repo that requested them from the org level.
I start a macOS VM with Anka and then once it has networking I install the latest actions runner for macOS with a script under https://github.com/veertuinc/anklet/tree/main/plugins/handlers/github. I then have my Anklet Github plugin make a call for a registration token and then use that, through another bash script in the VM, to register the runner and then finally start the runner service. This works 99% of the time.
The config command that ran:
Here is a photo of the pending job:
According to the actions runner _diag logs and status, I see this worked.
However then a second log file is created and the VM/Runner never shows in the self-hosted runners panel in the org level or repo level. Here is the log
This is reproducible, but only if I run a bunch of other things either at the same time, or before it. If I run the matrix on its own, it seems to be ok...
Here is the workflow yaml I'm working with
Things I've checked:
There is a worker log too, but I'm unsure if it's related. It has a few exit code 0 and non0 logs lines I'll provide below if they somehow are related:
Beta Was this translation helpful? Give feedback.
All reactions