-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore: Skipping TestBuildKanikoInsecureRegistry
pending investigation
#7122
Conversation
Codecov Report
@@ Coverage Diff @@
## main #7122 +/- ##
==========================================
- Coverage 70.48% 68.49% -1.99%
==========================================
Files 515 560 +45
Lines 23150 26506 +3356
==========================================
+ Hits 16317 18155 +1838
- Misses 5776 7096 +1320
- Partials 1057 1255 +198
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
TestBuildKanikoInsecureRegistry
pending investigation
The kokoro job still timed out. I am thinking we need to increase the timeout. |
32d36cd
to
21b7d79
Compare
increasing timeout to 90 mins. |
a3fb9e4
to
47655df
Compare
…ckly. With run mode added to artifact hash, skaffold build images weren't used in the subsequent run/dev/test command. This led to building the same artifact twice
47655df
to
33756cb
Compare
@tejal29 looks like the kokoro status was "canceled"? But seems like the tests are working properly. Not sure what happened so I'm gonna trigger a rerun |
@tejal29 any idea as to why this might still be timing out ? |
43878a1
to
77204e9
Compare
…/skaffold into fix_kaniko_int_test
Related to #7121
I tried downgrading the kaniko version to older v1.6.0, however it did not work.
Skipping this test pending investigation.