-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UPSTREAM: 70647: Always run untag when removing docker image #22500
Conversation
Can anyone confirm the 2 failed tests are due to this commit? It looks like to me that they are something different related with scheduling a pod with a volume and none of the modified files appears in the traces. |
/retest |
most recent unit failure is
time before that was
seem like to different flakes |
@droslean was going to rebuild that missing image. lets see if it is there. |
nope |
/test unit |
These still don't seem to be related with the PR itself... is there anything we can do to help? |
/retest |
/lgtm |
/approve |
gah, i thought Travis wasn't actually required... |
/retest Please review the full test history for this PR and help us cut down flakes. |
12 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
9 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@sjenning @derekwaynecarr guys is this happening in other PRs waiting for merge? The travis error is related with |
The travis CI error in question makes me wonder if this is somehow related to https://docs.travis-ci.com/user/customizing-the-build/#git-clone-depth |
@soukron
|
Let me try. |
New changes are detected. LGTM label has been removed. |
@brenton please check if the result it's the expected or not. |
When I look at the "files changed' in this PR I don't see any .travis.yaml updates. In any case, the travis CI job failed in the same way (and still cloned with a depth of 50). |
@soukron, I talked with a few other devs on the team. This is highly likely a situation with clone depth. If you update your PR to include a custom .travis.yaml it should go away. |
After including the custom .travis.yaml with the option the result is even worse... |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, sjenning, soukron The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I've undoed the change in .travis.yml after confirming that an empty commit (a new-line in readme file) will fail in the same tests. I've submitted the issue #22639 to track the problem in the files as I expected that the code should pass the tests. |
/retest |
superseded by #23183 which contains an addition fix that the first commit introduced and was fixed upstream |
K8S PR: kubernetes/kubernetes#70647
Backport of commit applied to /pull/22154 in release-3.11
xref https://bugzilla.redhat.com/show_bug.cgi?id=1691333