-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
try to reproduce #245 in CI #267
try to reproduce #245 in CI #267
Conversation
47f4d56
to
ae63683
Compare
So CI did fail but it was because the default test timeout for go is 10 minutes. You'll probably have to add a |
Maybe change it to 30m or something? I think they usually take right around 10m anyway, so adding another 10 is still causing a timeout at 15. |
Looks like it passed! |
That's bad, right :( ? |
yep, this was supposed to fail. I'll write a few further thoughts in #245, as this was just an experiment to reproduce the issue. |
So this Dockerfile did fail, but unfortunately we didn't get the same error. The integration tests built the Dockerfile with kaniko and Docker, and then diffed the images to make sure they are the same. Looks like kaniko was able to build the image, but the two images were pretty different:
|
in GoogleContainerTools#245 (comment) @MnrGreg describes a multi-stage buld failing in the same way. Maybe this can be reproduced in CI?
bb61708
to
6b24e64
Compare
Just did a rebase to current |
Cool so that actually fixed it --
All of our filesystem diffing tests passed, but when CI tried to compare layers it timed out:
|
Hey @Delphinator I'm going to close this PR since it seems like #388 fixed the issue. If you're still running into issues please let us know. |
This is an attempt to reproduce #245 in CI.