-
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: Ubuntu 2004 is slow #9567
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
Timing results from #9697:
From #9686:
From #9669 :
From #9652 :
DAE see a pattern with ubuntu 2004? |
Merged
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Mar 15, 2021
- cp test: clean up stray image - build test: add workaround for containers#9567 (ultra-slow ubuntu). We're seeing CI flakes (timeouts) due to ubuntu 2004 being absurdly slow. Workaround: double our timeout on one specific test when ubuntu + remote. - build test: clean up new copy-from test (from containers#9275). The test was copy-pasted from buildah system tests, without really adapting for podman environment (e.g. it was using images that we don't use here, and would cause pulls, which will cause flakes). Rewrite test so it references only $IMAGE, remove some confusing/unnecessary stuff, selectively run parts of it even when rootless or remote, and add a test to confirm that copy-from succeeded. - load test: add error-message test to new load-invalid (containers#9672). Basically, make sure the command fails for the right reason. - play test (kube): use $IMAGE, not alpine; and add pause-image cleanup to teardown() - apiv2 mounts test: add a maintainability comment in a tricky section of code; and tighten up the mount point test. Signed-off-by: Ed Santiago <[email protected]>
|
Does this mean we can close this issue? |
I've run a few more timings. Yes, it looks like this is fixed. Thanks again @baude. |
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Sep 17, 2021
* 070-build: - remove workaround for containers#9567, which is closed. - add many more cases to the ignorefile test, to test complicated special cases of Buildah PR 3486. * 160-volumes: - remove a skip_if_remote, volumes now work on remote - use a random name for tarball, and clean up when done using it. This fixes a gating-test failure (test runs as root, then rootless, and rootless can't clobber root's file). Signed-off-by: Ed Santiago <[email protected]>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Sep 22, 2021
* 070-build: - remove workaround for containers#9567, which is closed. - add many more cases to the ignorefile test, to test complicated special cases of Buildah PR 3486. * 160-volumes: - remove a skip_if_remote, volumes now work on remote - use a random name for tarball, and clean up when done using it. This fixes a gating-test failure (test runs as root, then rootless, and rootless can't clobber root's file). 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
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
I've updated my test-timings script to have it interpret system test results. Ubuntu is slow, especially 2004:
(All of these are remote, from #9556. It takes just a few seconds to get results for any PR, so just ask if you want others)
33
2004
2010
Someone with access to Ubuntu should probably do some manual runs of system tests, verify the slowness, then possibly instrument the tests in question to track down the cause.
The text was updated successfully, but these errors were encountered: