Skip to content

[DEBUGGING]: buildg time-out flaky issue (#4046) #4103

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
wants to merge 1 commit into from

Conversation

apostasie
Copy link
Contributor

See #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.

@apostasie apostasie closed this Apr 14, 2025
@apostasie apostasie reopened this Apr 14, 2025
@apostasie apostasie closed this Apr 15, 2025
@apostasie apostasie reopened this Apr 15, 2025
@apostasie apostasie closed this Apr 15, 2025
@apostasie apostasie reopened this Apr 15, 2025
@apostasie
Copy link
Contributor Author

Current patch is not fixing the issue.

I will leave this open for possible further debugging, but the current intuition is likely a miss.

@apostasie apostasie changed the title [WIP] Workaround buildg time-out [DEBUGGING] Workaround buildg time-out Apr 15, 2025
@apostasie apostasie changed the title [DEBUGGING] Workaround buildg time-out [DEBUGGING]: Workaround buildg time-out Apr 15, 2025
@apostasie apostasie changed the title [DEBUGGING]: Workaround buildg time-out [DEBUGGING]: buildg time-out flaky issue (#4046) Apr 16, 2025
@apostasie apostasie closed this Apr 16, 2025
@apostasie apostasie reopened this Apr 16, 2025
@apostasie apostasie closed this Apr 16, 2025
@apostasie apostasie reopened this Apr 16, 2025
@apostasie
Copy link
Contributor Author

Failure likely: #3556

@apostasie apostasie closed this Apr 16, 2025
@apostasie apostasie reopened this Apr 16, 2025
@apostasie apostasie closed this Apr 17, 2025
@apostasie apostasie reopened this Apr 17, 2025
@apostasie apostasie closed this Apr 17, 2025
@apostasie apostasie reopened this Apr 17, 2025
@apostasie apostasie closed this Apr 17, 2025
@apostasie apostasie reopened this Apr 17, 2025
@apostasie apostasie closed this Apr 17, 2025
@apostasie apostasie reopened this Apr 17, 2025
@apostasie apostasie reopened this Apr 18, 2025
@apostasie apostasie closed this Apr 18, 2025
@apostasie apostasie reopened this Apr 18, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie
Copy link
Contributor Author

Failure is #4132

@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 19, 2025
@apostasie apostasie reopened this Apr 19, 2025
@apostasie apostasie closed this Apr 20, 2025
@apostasie apostasie reopened this 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]>
@apostasie
Copy link
Contributor Author

@AkihiroSuda

Current assessment on this is that buildg timeout is just too short.

Suggesting on upstream to increase it (#242).

I do not see what we can do here in nerdctl, so, I am going to close this for now.

If and when we get an updated buildg, we can re-evaluate.

@apostasie apostasie closed this Apr 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants