Skip to content
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

Fix flake on failed podman-remote build : try 2 #10034

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented Apr 14, 2021

This time we are checking if the function actually succeeded,
otherwise we will report an error.

Also if we did not get the id, report unexpected failure.

Signed-off-by: Daniel J Walsh [email protected]

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhatdan

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2021
This time we are checking if the function actually succeeded,
otherwise we will report an error.

Also if we did not get the id, report unexpected failure.

[NO TESTS NEEDED] Still no good way to test this, but manually.

Signed-off-by: Daniel J Walsh <[email protected]>
@edsantiago
Copy link
Member

Nice! What I'm seeing now is:

Error: stream dropped, unexpected failure

instead of the pull policy is "never" one. The important factors, though, are (1) it exited nonzero (as it should), and (2) it seems to take a lot longer to fail: 202s, 182s, 48s

LGTM!

@rhatdan
Copy link
Member Author

rhatdan commented Apr 15, 2021

@containers/podman-maintainers PTAL

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vrothberg
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2021
@openshift-merge-robot openshift-merge-robot merged commit b2a3bb4 into containers:master Apr 15, 2021
edsantiago added a commit to edsantiago/libpod that referenced this pull request Apr 15, 2021
This test continues to flake on podman-remote (especially Ubuntu)
even after containers#10030 and containers#10034. I give up. Stop checking the error
message in podman-remote tests.

Signed-off-by: Ed Santiago <[email protected]>
jmguzik pushed a commit to jmguzik/podman that referenced this pull request Apr 26, 2021
This test continues to flake on podman-remote (especially Ubuntu)
even after containers#10030 and containers#10034. I give up. Stop checking the error
message in podman-remote tests.

Signed-off-by: Ed Santiago <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants