-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
CI flake: podman image trust show: output is in random order #6764
Labels
flakes
Flakes from Continuous Integration
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
A friendly reminder that this issue had no activity for 30 days. |
Still happening, mostly just singletons but every so often triplets causing CI flakes:
|
edsantiago
added
flakes
Flakes from Continuous Integration
kind/bug
Categorizes issue or PR as related to a bug.
and removed
stale-issue
labels
Aug 14, 2020
Removed stale-issue label, this is not stale. Triggered on #7317 : https://cirrus-ci.com/task/4997918144856064 |
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Aug 17, 2020
The output of 'podman image trust' is in random order; but its e2e test was assuming a specific one. This caused flakes. Fixes: containers#6764 Signed-off-by: Ed Santiago <[email protected]>
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Aug 17, 2020
The output of 'podman image trust' is in random order; but its e2e test was assuming a specific one. This caused flakes. Fixes: containers#6764 Signed-off-by: Ed Santiago <[email protected]>
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Aug 18, 2020
The output of 'podman image trust' is in random order; but its e2e test was assuming a specific one. This caused flakes. Fixes: containers#6764 Signed-off-by: Ed Santiago <[email protected]>
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Sep 14, 2020
The output of 'podman image trust' is in random order; but its e2e test was assuming a specific one. This caused flakes. Fixes: containers#6764 Signed-off-by: Ed Santiago <[email protected]>
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 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
flakes
Flakes from Continuous Integration
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
cirrus-flake-xref is reporting a lot of flakes in the
podman image trust show
test (see below).Investigation shows that the output of
podman image trust show
comes out in random order. The test is expecting the following output, in this order:...and is expecting
accept
,reject
, andsigned
in lines 1, 2, and 3 respectively. However, often the output lines are in different order. This causes the test to fail, and if you get unlucky three times the entire CI run will fail.One solution might be to fix
podman image trust show
to output lines in consistent order. Another might be to fix the test so it doesn't rely on order. I don't know enough to suggest which might be preferable.Podman trust [It] podman image trust show
The text was updated successfully, but these errors were encountered: