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
I have been trying to track down some random deadline exceeded errors from buildkit that start happening after many hours of load testing. With Go 1.21rc2 I updated all the WithTimeout to WithTimeoutCause and annotated the deadline error with the function/line it came from and found all of my deadline exceeded errors came from recordBuildHistory
I am wondering if we should have a shorter timeout and instead of returning the context error, just log that we failed to record build history. It doesn't seem right to return an error for the solve when the solve actually succeeds and we just failed to record it.
The text was updated successfully, but these errors were encountered:
I have been trying to track down some random
deadline exceeded
errors from buildkit that start happening after many hours of load testing. With Go 1.21rc2 I updated all theWithTimeout
toWithTimeoutCause
and annotated the deadline error with the function/line it came from and found all of mydeadline exceeded
errors came from recordBuildHistoryThis is likely related to #3743
I am wondering if we should have a shorter timeout and instead of returning the context error, just log that we failed to record build history. It doesn't seem right to return an error for the solve when the solve actually succeeds and we just failed to record it.
The text was updated successfully, but these errors were encountered: