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

Remove build \!remote flags from test phase 2 #8379

Merged
merged 2 commits into from
Nov 18, 2020

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented Nov 17, 2020

Add some more tests, document cases where remote will not work
Add FIXMEs for tests that should work on podman-remote but currently
do not.

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 Nov 17, 2020
@cevich
Copy link
Member

cevich commented Nov 17, 2020

/lgtm
/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 17, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 17, 2020
@rhatdan rhatdan removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Nov 17, 2020
@edsantiago
Copy link
Member

I see that someone pressed Re-run. I don't think that's going to help: these look like very real errors: lots in ubuntu and only push in fedora

@rhatdan
Copy link
Member Author

rhatdan commented Nov 17, 2020

@edsantiago I found a race condition on podman-remote network rm --force, that is causing the network remove failures.

@rhatdan rhatdan force-pushed the remote2 branch 2 times, most recently from 97658ff to 175b482 Compare November 18, 2020 15:43
@rhatdan
Copy link
Member Author

rhatdan commented Nov 18, 2020

@containers/podman-maintainers PTAL

return
}
if err := network.RemoveNetwork(config, name); err != nil {
utils.InternalServerError(w, err)
report := reports[0]
Copy link
Member

Choose a reason for hiding this comment

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

Should do a length check to make sure it is at least len(1) so we don't panic

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed


decoder := r.Context().Value("decoder").(*schema.Decoder)
if err := decoder.Decode(&query, r.URL.Query()); err != nil {
utils.Error(w, "Something went wrong.", http.StatusBadRequest, errors.Wrapf(err, "failed to parse parameters for %s", r.URL.String()))
Copy link
Member

Choose a reason for hiding this comment

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

I'm not going to block just because of this... but if you need to resubmit for any reason, could there maybe be a better diagnostic than "Something went wrong"?

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed, although this message is in all over the code. I think this is what Docker did when there was an unexpected error.

Copy link
Member

Choose a reason for hiding this comment

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

@edsantiago I thoroughly concur and have been dinging those as I encounter them. It makes me grind my teeth every time I spot it.

The --force parameter was not being handled correctly.
This is leading to some race conditions in testing failures.

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

Tentatively LGTM aside from two questionable "Something went wrong" messages. I appreciate the FIXME in SkipIfRemotes that should work, that makes it easy to grep for them. I'll let others slash-lgtm tho.

Add some more tests, document cases where remote will not work
Add FIXMEs for tests that should work on podman-remote but currently
do not.

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

LGTM once @QiWang19 's question is answered/addressed.

Copy link
Member

@ashley-cui ashley-cui left a comment

Choose a reason for hiding this comment

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

LGTM

@rhatdan rhatdan added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2020
@openshift-merge-robot openshift-merge-robot merged commit b1007ca into containers:master Nov 18, 2020
@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 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 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.

9 participants