Raise the kaniko tests timeout from 2m
#4863
Assignees
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/flake
Categorizes issue or PR as related to a flakey test
Comments
afrittoli
added
the
kind/flake
|
/cc @lbernick @xchapter7x |
5 tasks
abayer
added a commit
to abayer/tektoncd-pipeline
that referenced
this issue
May 17, 2022
…outs fixes tektoncd#4863 The parallelism change appears to make a real difference in cutting down on flaky tests, while only increasing total duration of the integration test runs to ~30-35 minutes from ~25, which seems like a worthy trade to me. Also bumps the timeout for Kaniko tasks in e2e tests to 5 minutes, where a timeout was specified in the first place. Signed-off-by: Andrew Bayer <[email protected]>
5 tasks
|
/assign |
tekton-robot
pushed a commit
that referenced
this issue
May 17, 2022
…outs fixes #4863 The parallelism change appears to make a real difference in cutting down on flaky tests, while only increasing total duration of the integration test runs to ~30-35 minutes from ~25, which seems like a worthy trade to me. Also bumps the timeout for Kaniko tasks in e2e tests to 5 minutes, where a timeout was specified in the first place. Signed-off-by: Andrew Bayer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
kanikotests reliably pass.Actual Behavior
We frequently see the
kanikotests flake downstream, and most of the ones I've looked at are timeouts.Quoting @imjasonh "Nobody should expect kaniko to do anything reliably in 2m" 🤣
cc @abayer since this touches on flakes (not sure if you've seen this in your adventures)
The text was updated successfully, but these errors were encountered: