-
Notifications
You must be signed in to change notification settings - Fork 654
[CI]: buildg times-out #4046
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
Comments
This was referenced Mar 27, 2025
This was referenced Apr 12, 2025
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 14, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
This was referenced Apr 14, 2025
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 16, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
This was referenced Apr 16, 2025
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 18, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 18, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
This was referenced Apr 18, 2025
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 18, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 18, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 18, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 19, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Apr 20, 2025
See containerd#4046 Root cause is undiagnosed / unclear, but it seems like in some circumstances, buildg command is too late to read from stdin. This workaround introduces an arbitrary delay before writing to stdin, as a temporary solution to reduce test flakyness. Signed-off-by: apostasie <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
This was first spotted in #4007 (comment) and seen again in #4044
Message is definitely coming from https://github.com/ktock/buildg/blob/main/pkg/buildkit/client.go#L83
It is unclear to me if this is somehow builkit timeouting on GHA cache (but why then?), or something else that would be buildg specific.
Tagging @ktock for insight?
Steps to reproduce the issue
No response
Describe the results you received and expected
What version of nerdctl are you using?
main
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response
The text was updated successfully, but these errors were encountered: