arch linux CI workflow fails about libvfio-user HOT 11 OPEN

It looks like it timed out.

from libvfio-user.

pacman has a download timeout of 10s if I'm not mistaken that can be disabled by:

Not sure if you can also simply increase this, but one could simply use the timeout command on the pacman command in combination with this flag. I can have a look at this later the day.

from libvfio-user.

It's the entire workflow that's timing out though, I think, if you check the execution times. It shouldn't really take 10 minutes to update (!)

from libvfio-user.

Ah yeah, thank's for the hint, now I see it too in the workflow run. Hm, I'll sync my fork and try to reproduce this on my runner.

from libvfio-user.

I looked into this but I'm not able to reproduce it: https://github.com/gierens/libvfio-user/actions/runs/6066677383 ... ran it multiple times and the arch job always succeeds as the fastest.

What I did notice however is that the centos job sometimes comes pretty close to the 10 minute mark (https://github.com/gierens/libvfio-user/actions/runs/6066677383/attempts/1):

And also failed one time (https://github.com/gierens/libvfio-user/actions/runs/6066677383/attempts/3):

Apparently due to some connection issue:

So my best guess is, that something similar happened to the arch job on the mentioned PR ... some connection issue to the arch repos and then a timeout. Nothing to worry too much about.

I'm also not convinced that the timeout came from Github since the default Github Actions timeout is 6 hours unless configured otherwise: https://nesin.io/blog/github-action-timeout ... and I cannot find any such config in the workflows.

from libvfio-user.

See the yaml in .github - we set timeout to 10 minutes as that really should be long enough for pre-commit CI.

from libvfio-user.

Ah, yeah you're right ... my editor plugin for searching doesn't seem to go into hidden directories that's why I could find it, my bad!

from libvfio-user.

But then that's actually settled I'd say, just a timeout due to a connection issue.

from libvfio-user.

we saw this a few times but will keep open and monitor...

from libvfio-user.

I wonder if maybe the arch repo mirror that is chosen in the jobs on your runner is flaky.

from libvfio-user.

Well, it's github's runner so not something we'd control

from libvfio-user.