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
Currently, we are stuck on the current version of buildkit, since moby/buildkit#4347 (comment) seems to have introduced a deadlock.
To reproduce: update buildkit in go.mod to ca71a446d9f4e31ca7c4fa30fb8fb8861b8b0117, and run a large number of integration tests. The engine will lock up after some time - after sending SIGUIT to the engine, you can observe the stack trace:
Currently, we are stuck on the current version of buildkit, since moby/buildkit#4347 (comment) seems to have introduced a deadlock.
To reproduce: update buildkit in
go.mod
toca71a446d9f4e31ca7c4fa30fb8fb8861b8b0117
, and run a large number of integration tests. The engine will lock up after some time - after sendingSIGUIT
to the engine, you can observe the stack trace:See #6169 for more information on when this was originally discovered.
Next steps:
The text was updated successfully, but these errors were encountered: