Skip to content

[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

Closed
apostasie opened this issue Mar 27, 2025 · 1 comment
Closed

[CI]: buildg times-out #4046

apostasie opened this issue Mar 27, 2025 · 1 comment
Labels
area/ci e.g., CI failure bug Something isn't working

Comments

@apostasie
Copy link
Contributor

apostasie commented Mar 27, 2025

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

=== RUN   TestBuilder/Debug
    builder_builder_test.go:159: 
    builder_builder_test.go:159: ======================== Pre-test cleanup ========================
    builder_builder_test.go:159: 
    builder_builder_test.go:159: ======================== Test setup ========================
    builder_builder_test.go:159: 
    builder_builder_test.go:159: ======================== Test Run ========================
    command.go:113: /usr/local/bin/nerdctl --namespace=nerdctl-test builder debug /tmp/TestBuilderDebug385954703/001
    command.go:113: Expected exit code: 0
        
        Command:  /usr/local/bin/nerdctl --namespace=nerdctl-test builder debug /tmp/TestBuilderDebug385954703/001
        ExitCode: 1
        Error:    exit status 1
        Stdout:   
        Stderr:   timed out to access cache storage. other debug session is running?
        
        Env:
        SHELL=/bin/bash
        LOGNAME=rootless
        XDG_SESSION_TYPE=tty
        HOME=/home/rootless
        LANG=C.UTF-8
        SSH_CONNECTION=::1 41924 ::1 22
        XDG_SESSION_CLASS=user
        IPFS_PATH=/home/rootless/.local/share/ipfs
        USER=rootless
        SHLVL=1
        XDG_SESSION_ID=5
        XDG_RUNTIME_DIR=/run/user/1001
        SSH_CLIENT=::1 [419](https://github.com/containerd/nerdctl/actions/runs/14111164974/job/39530341996?pr=4044#step:8:420)24 22
        DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
        OLDPWD=/home/rootless
        _=/usr/local/bin/gotestsum
        PATH=/usr/local/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
        ***
        DOCKER_CONFIG=/tmp/TestBuilderDebug385954703/001
        NERDCTL_TOML=/tmp/TestBuilderDebug385954703/001/nerdctl.toml
    case.go:180: 
    case.go:181: ======================== Post-test cleanup ========================
--- FAIL: TestBuilder/Debug (3.13s)

What version of nerdctl are you using?

main

Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

Host information

No response

@apostasie apostasie added the kind/unconfirmed-bug-claim Unconfirmed bug claim label Mar 27, 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]>
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]>
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 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]>
@AkihiroSuda AkihiroSuda added bug Something isn't working area/ci e.g., CI failure and removed kind/unconfirmed-bug-claim Unconfirmed bug claim labels Apr 20, 2025
@apostasie
Copy link
Contributor Author

Since #4162 landed, I have not seen this again. Closing as fixed.

Thanks @ktock - appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci e.g., CI failure bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants