-
Notifications
You must be signed in to change notification settings - Fork 12
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
macos-13
not working
#41
Comments
it worked again, seems it is unstable |
@matiktli is it still unstable for you? |
It looks like it's unstable for me; sometimes the action succeeds - and sometimes it fails 😄
Note that I set A Not working
Working
|
Facing a similar issue on Note that I'm also seeing
|
@joffrey-bion: thanks for the report, I will give it a look this week. Saving here your versions in case the logs disappear by then:
I think it could be time to let QEMU upgrade beyond this version. 🤔 |
Ah sorry I should have copied more of the logs, thanks for saving this. I didn't touch the default value for the QEMU update input because of the performance overhead. The action is already taking 6min for me when it works, so I didn't want to make this worse. But if it removes the flakiness it's definitely a win. I can try that next time. |
@joffrey-bion no worries! Indeed the QEMU installation is a huge bottleneck. Plus it's kinda difficult to cache all this Homebrew stuff. I already spent a lot of time trying to figure out how to cache it, but something always goes wrong. :( Honestly I can't wait for Github to start adding M3/M4 action runners. They support nested virtualization and with this I will be able to drop support for Intel-based macOS runners. |
@douglascamata hopefully they will pre-install Colima again. It was already there in I don't understand why it's no longer there in |
I was about to try to do that, so thanks for letting me know that I would probably waste my time 😆 This saves me some pointless hassle. |
I am creating issue again as according to: #37 it should be fixed.
And indeed it worked once but then start failing again.
Here are the logs:
The text was updated successfully, but these errors were encountered: