-
Notifications
You must be signed in to change notification settings - Fork 100
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
Flaky Tests #918
Comments
Thanks for the notice. I will figure it out soon. |
CDH workflow triggers were not updated when the pull functionality got moved there: changes to |
That is the case. |
Then, I think it would be great time to extend our dependency graph. 😉 |
Update: The tests are passing after cleaning up https://github.com/confidential-containers/guest-components/actions/runs/13429528372?pr=916 |
Ok, we fixed the tests that were failing every time, but there are also some flaky jobs. For example, https://github.com/confidential-containers/guest-components/actions/runs/13515374662/job/37762988211#step:20:474 We're pulling a container from the aliyun container service here. I wonder if we want to copy these containers to another registry? We could also keep that registry but skip that test on bare metal runners that might have more trouble connecting to it. |
+1 |
Anyone who has submitted a PR recently has probably noticed that the
image-rs
tests take a few tries. I think this is just because we aren't always able to pull the image. This seems to happen most frequently on s390x but maybe it is elsewhere too. It's not a huge inconvenience but maybe there is a way we can fix this?cc @BbolroC
The text was updated successfully, but these errors were encountered: