You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The slsa-framework/slsa-github-generator deadlocks if builder outputs a lot of data over both stdout and stderr. The reason is that the current implementation reads from stdout and stderr sequentially, which is a known cause of deadlocks: golang/go#16787.
Because of #3569, it also does not print any logs in the process, the action just times out.
I'll create a simpler reproduction upon request. But the bug should be fairly obvious when looking at internal/builders/docker/pkg/builder.go and golang/go#16787.
# Summary
Fixes#3571. Fixes#3569. Shoutout to @jblebrun who wrote most of the
code in this PR and debugged this issue together with me.
## Testing Process
...
## Checklist
- [ ] Review the contributing [guidelines](./../CONTRIBUTING.md)
- [ ] Add a reference to related issues in the PR description.
- [ ] Update documentation if applicable.
- [ ] Add unit tests if applicable.
- [ ] Add changes to the [CHANGELOG](./../CHANGELOG.md) if applicable.
Signed-off-by: Juliette Pretot <julsh@google.com>
Co-authored-by: Jason LeBrun <jibbl@google.com>
Describe the bug
The slsa-framework/slsa-github-generator deadlocks if builder outputs a lot of data over both stdout and stderr. The reason is that the current implementation reads from stdout and stderr sequentially, which is a known cause of deadlocks: golang/go#16787.
Because of #3569, it also does not print any logs in the process, the action just times out.
To Reproduce
Steps to reproduce the behavior:
I'll create a simpler reproduction upon request. But the bug should be fairly obvious when looking at
internal/builders/docker/pkg/builder.go
and golang/go#16787.Expected behavior
No deadlock.
cc @tiziano88 @jblebrun
The text was updated successfully, but these errors were encountered: