-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ci(buildkit): fix timeout for image job #4491
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see it's still failing with timeout, we try 30 min or what could be the cause?
207630b
to
c11cf91
Compare
Ok got a proper stacktrace now: https://github.com/moby/buildkit/actions/runs/7231798843/job/19705540067?pr=4491#step:13:505 |
Signed-off-by: CrazyMax <[email protected]>
c11cf91
to
b014472
Compare
@tonistiigi Added
So seems related to emulation when invoking |
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Comparing QEMU logs in https://github.com/moby/buildkit/actions/runs/7238175771/job/19719814734?pr=4491#step:7:4174 that succeeds:
With this one that fails: https://github.com/moby/buildkit/actions/runs/7238175771/job/19719964140?pr=4491#step:7:47491
An operation timed out and retries indefinitely? |
This seems related to https://gitlab.com/qemu-project/qemu/-/issues/456 where PI (priority-inheritance) futexes are not supported in qemu. This is supported since QEMU 7.2.0 but atm we are using 7.0.0. Not sure why I can't repro consistently though. Same happens in this project anonaddy/docker#245 (comment) |
Signed-off-by: CrazyMax <[email protected]>
bcc5f3f
to
7f9b09f
Compare
Still hangs with QEMU 8.0.4 😕 https://github.com/moby/buildkit/actions/runs/7246753647/job/19741177891?pr=4491#step:7:37760
|
@crazy-max I guess this should be draft, right? |
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
"buildkitd --version" might hang when using emulation during smoke test. Add a timeout to mitigate this issue and avoid blocking CI. This is currently tracked in moby#4491 Signed-off-by: CrazyMax <[email protected]>
No description provided.