Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Disable the M1 job as it's been failing consistently #28561

Closed
wants to merge 1 commit into from
Closed

Disable the M1 job as it's been failing consistently #28561

wants to merge 1 commit into from

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Oct 13, 2022

No description provided.

@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label Oct 13, 2022
@Karm Karm self-requested a review October 13, 2022 13:15
Karm
Karm approved these changes Oct 13, 2022
View reviewed changes
Copy link
Member

@Karm Karm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx. I think we would need to connect our own runners to saturate the allocation 🤷‍♂️

@gsmet
Copy link
Member

gsmet commented Oct 13, 2022

@holly-cummins pinging you as it has been failing for weeks now. Not sure what to do about it? Either you can fix it in a stable way or we will just have to wait for GH to roll M1 runners.

@holly-cummins
Copy link
Contributor

I've rebooted the mac, so it's now running jobs again.

@holly-cummins
Copy link
Contributor

... although manual reboots isn't sustainable, clearly. As a hack, I'll set up a scheduled reboot for Sunday, and we can see if that is enough to keep it sustainable. I'll also look into podman-desktop/podman-desktop#225 to see if that reduces the number of moving parts.

@holly-cummins
Copy link
Contributor

Adding this in here, so it's searchable. This is the error that crops up and needs a reboot (for now?) to fix it.

A job started hook has been configured by the self-hosted runner administrator
Run '/Users/githubactions/podman-start.sh'
Starting machine "podman-machine-default"
Error: dial unix /var/folders/mq/dx78dkw10dv2hb0fm0qvchqm0000gp/T/podman/qmp_podman-machine-default.sock: connect: no such file or directory
Error: Process completed with exit code 125.

Note that https://github.com/quarkusio/quarkus/actions/runs/3243362735/jobs/5318611709 isn't showing the error, because I rebooted the machine. :)

@holly-cummins
Copy link
Contributor

We now have green builds on M1 again, and I have scheduled a reboot for midnight every Sunday. Clearly, that's not ideal, so I will raise a defect against podman (it seems slightly different from any existing issues): containers/podman#16163

@holly-cummins
Copy link
Contributor

I might have borked one build just now by trying to upgrade podman mid-build (because I can't quiesce them), but hopefully that was a one-off!

@geoand
Copy link
Contributor Author

geoand commented Oct 14, 2022

Closing this

@geoand geoand closed this Oct 14, 2022
@quarkus-bot quarkus-bot bot added the triage/invalid This doesn't seem right label Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Karm Karm Karm approved these changes

Assignees
No one assigned
Labels
area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure triage/invalid This doesn't seem right
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@geoand @gsmet @holly-cummins @Karm