-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
integration: log goroutine trace on test timeout #5568
integration: log goroutine trace on test timeout #5568
Conversation
Signed-off-by: Tonis Tiigi <[email protected]>
f054ad5
to
ca6fa29
Compare
ca6fa29
to
47642a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Add maximum timeout to each test and log all buildkitd goroutines when a test gets stuck. Currently tests can time out and will print daemon logs but these would already be after shutdown signal is sent to the daemon. Signed-off-by: Tonis Tiigi <[email protected]>
47642a2
to
58b5e6a
Compare
@@ -18,6 +22,8 @@ import ( | |||
|
|||
const buildkitdConfigFile = "buildkitd.toml" | |||
|
|||
const maxSandboxTimeout = 5 * time.Minute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5min might not be enough for this test TestIntegration/TestBasicGhaCacheImportExport
: https://github.com/moby/buildkit/actions/runs/12189447998/job/34004770018?pr=5568#step:8:2218
Default timeout is 10m:
buildkit/cache/remotecache/gha/gha.go
Line 44 in 409f7b4
defaultTimeout = 10 * time.Minute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added extra time to GHA test
This test can hit rate-limiting from Github and run long. Signed-off-by: Tonis Tiigi <[email protected]>
Add maximum timeout to each test and log all buildkitd
goroutines when a test gets stuck. Currently tests can time out
and will print daemon logs but these would already be after
shutdown signal is sent to the daemon.
Is there any other runtime info that is also worth printing?
Test with fake deadlock: