-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
WIP - remote build: fix streaming and error handling #11046
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@edsantiago, it looks like we were masking errors before. I think this will help but it's hard to reproduce. |
A huge ton of skips: podman-remote build just doesn't really work at all. Lots of issues filed, a few more left to go. Submitting this just to see how it does in CI. Signed-off-by: Ed Santiago <[email protected]>
2c7f6bb
to
a3ffc22
Compare
@edsantiago one round without flakes. Let's try another time. I noticed that we need to distinguish between EOF and unexpected EOF. Not yet sure if that's the key or not. |
Ah, you rebased on my buildah-bud PR, clever. Why do you say "without flakes" though? I see the same old same old |
I think this one happened in "another time". First run went fine. The hunt continues... |
Address a number of issues in the streaming logic in remote build, most importantly an error in using buffered channels on the server side. The pattern below does not guarantee that the channel is entirely read before the context fires. for { select { case <- bufferedChannel: ... case <- ctx.Done(): ... } } Fixes: containers#10154 Signed-off-by: Valentin Rothberg <[email protected]>
Ed will cherry-pick my commit here into his PR, so I am closing. |
Address a number of issues in the streaming logic in remote build, most
importantly an error in using buffered channels on the server side.
The pattern below does not guarantee that the channel is entirely read
before the context fires.
Fixes: #10154
Signed-off-by: Valentin Rothberg [email protected]