Open cppforlife opened 4 years ago
During early development, I saw some hangs that sound similar, so I think we do have some corner cases or flakiness somewhere in the kubectl exec
flow. Getting some parallel tests running in CI will also be helpful to squash these parallelism bugs.
We've added various hardening improvements on parallel build scenarios in the most recent release. It might be worth giving your test scenario another try on 0.1.3 to see if the problem is resolved or if we've still got more raciness to squash.
What steps did you take and what happened
things were working ok for a few hours. then i issued 3 builds in parallel (same single go file app submitted 3 times). they got stuck (not sure where; lost the output). after that i've tried to issue single build and now buildkit is stuck (been sitting at
#10 sending tarball
for 10+ minutes). getting stuck on sending tarball happens consistently. this continues to happen even after rm/create cycle.(command:
/usr/local/bin/kubectl-buildkit build --progress=plain --file dev/Dockerfile.dev --tag kbld:rand-1605358502697084000-246112051777-simple-app-two .
)What did you expect to happen
not get stuck.
Environment Details:
error is happening on single pod buildkit. ive got 5 nodes in cluster. previously had buildkit installed with 5 nodes.
Builder Logs Logs:
Dockerfile app: https://github.com/vmware-tanzu/carvel-kbld/tree/develop/test/e2e/assets/simple-app