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 bindings prune containers flaky test #9902

Conversation

jmguzik
Copy link
Contributor

@jmguzik jmguzik commented Mar 31, 2021

In #9863 prune containers filter params were narrowed to support only those
required by http API. name filter in bindings was replaced by until filter,
which is not a good match, as until filters are causing tests to be flaky.

Signed-off-by: Jakub Guzik [email protected]

In containers#9863 prune containers filter params were narrowed to support only those
required by http API. name filter in bindings was replaced by until filter,
which is not a good match, as until filters are causing tests to be flaky.

Signed-off-by: Jakub Guzik <[email protected]>
@jmguzik
Copy link
Contributor Author

jmguzik commented Mar 31, 2021

@rhatdan FYI

@rhatdan
Copy link
Member

rhatdan commented Mar 31, 2021

That works, but I would love to get a working tests in.
LGTM to fix flakes for now.
@containers/podman-maintainers PTAL
/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2021
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.

I prefer to use Skip(...) and not remove the code, so we leave some breadcrumbs for the future.

Can you elaborate on what is causing the flakes? (would be great in the commit message and a comment in the test)

@jmguzik
Copy link
Contributor Author

jmguzik commented Mar 31, 2021

@rhatdan @vrothberg The problem is in bindings every test is instantiated with default container:

_, err := bt.RunTopContainer(&name, nil)

This excludes using label as a filter in this test. I maybe lack experience, but saw that adding label is not that easy and possibly not worthy, as it is tested in apiv2 tests.

I tried a second filter allowed which is until, but it causes tests to flake. In my opinion, it is related to the time conversions which are occurring in the API (one format to another) and accuracy. If you include sleep in this test, it should pass.

So, it is impossible to recreate previous test behavior (which was wrong, because filters from the list were used here) as the only filter that can be used is a label (or until with sleep if you want). Thus, in my opinion, skip is not valid here. You would skip invalid behavior.

@jmguzik
Copy link
Contributor Author

jmguzik commented Mar 31, 2021

And unitil is added by me, previously name filter was here.

@vrothberg
Copy link
Member

@edsantiago may have an idea how to make it pass

@jmguzik
Copy link
Contributor Author

jmguzik commented Mar 31, 2021

@vrothberg my alternative idea for sleep until would be something like 0ns or 1ns and keeping fingers crossed that it is enough.
I would suggest however to remove this one and I can experiment further once @edsantiago will provide input.

@edsantiago
Copy link
Member

@vrothberg @jmguzik sorry, this is way above my head. I don't know ginkgo at all.

@jmguzik
Copy link
Contributor Author

jmguzik commented Mar 31, 2021

@vrothberg @jmguzik sorry, this is way above my head. I don't know ginkgo at all.

So, then my proposition would be to test with ns or sleep if you really want until check. @vrothberg please let me know what you prefer.

@rhatdan
Copy link
Member

rhatdan commented Mar 31, 2021

/approve
/lgtm
Lets work on this in a separate PR. For now I want to fixup CI so tests can merge.

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmguzik, 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 lgtm Indicates that a PR is ready to be merged. label Mar 31, 2021
@openshift-merge-robot openshift-merge-robot merged commit 24a0262 into containers:master Mar 31, 2021
@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.

6 participants