CI: Ubuntu 2004 is slow #9567
Description
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)
| fedora 33 |
ubuntu 2004 |
ubuntu 2010 |
|
|---|---|---|---|
| 20 podman run - basic tests | 3.00 | 5.00 | 5.00 |
| 33 podman run --log-driver | 4.00 | 9.00 | 5.00 |
| 48 podman ps --filter | 2.00 | 7.00 | 4.00 |
| 51 podman stop --all | 5.00 | 9.00 | 6.00 |
| 53 podman stop - can trap signal | 5.00 | 9.00 | 6.00 |
| 65 podman cp file from host to container | 19.00 | 76.00 | 26.00 |
| 66 podman cp file from container to host | 15.00 | 95.00 | 25.00 |
| 67 podman cp dir from host to container | 17.00 | 142.00 | 35.00 |
| 68 podman cp dir from container to host | 14.00 | 107.00 | 28.00 |
| 69 podman cp file from host to container volume | 1.00 | 34.00 | 6.00 |
| 70 podman cp file from host to container mount | 2.00 | 29.00 | 6.00 |
| 71 podman cp * - wildcard copy multiple files from container to host | 1.00 | 18.00 | 5.00 |
| 72 podman cp - will not recognize symlink pointing into host space | 1.00 | 14.00 | 5.00 |
| 73 podman cp - will not expand globs in host space (#3829) | 1.00 | 13.00 | 4.00 |
| 74 podman cp - will not expand wildcard | 1.00 | 13.00 | 5.00 |
| 75 podman cp into container: weird symlink expansion | 3.00 | 28.00 | 13.00 |
| 76 podman cp into a subdirectory matching GraphRoot | 3.00 | 22.00 | 8.00 |
| 77 podman cp from stdin to container | 13.00 | 41.00 | 24.00 |
| 78 podman cp from container to stdout | 12.00 | 38.00 | 21.00 |
| 79 podman build - basic test | 5.00 | 35.00 | 15.00 |
| 82 podman build - cache (#3920) | 4.00 | 24.00 | 11.00 |
| 83 podman build - URLs | 2.00 | 15.00 | 6.00 |
| 84 podman build - workdir, cmd, env, label | 17.00 | 129.00 | 58.00 |
| 85 podman build - stdin test | 4.00 | 17.00 | 14.00 |
| 86 podman build - does not gobble stdin that does not belong to it | 2.00 | 7.00 | 7.00 |
| 87 podman build --layers test | 6.00 | 13.00 | 16.00 |
| 88 build with copy-from referencing the base image | 12.00 | 18.00 | 21.00 |
| 99 podman load - by image ID | 2.00 | 5.00 | 6.00 |
| 100 podman load - by image name | 3.00 | 6.00 | 6.00 |
| 102 podman load - multi-image archive | 4.00 | 8.00 | 7.00 |
| 103 podman load - multi-image archive with redirect | 4.00 | 8.00 | 7.00 |
| 105 podman kill - rejects invalid args | 2.00 | 6.00 | 6.00 |
| 120 podman volume: exec/noexec | 2.00 | 5.00 | 5.00 |
| 121 podman volume, implicit creation with run | 4.00 | 7.00 | 6.00 |
| 123 podman volume prune | 3.00 | 7.00 | 6.00 |
| 125 podman pod - communicating between pods | 3.00 | 8.00 | 7.00 |
| 126 podman pod - communicating via /dev/shm | 2.00 | 6.00 | 6.00 |
| 135 podman system df - with active containers and volumes | 3.00 | 5.00 | 5.00 |
| 153 podman shell completion test | 65.00 | 201.00 | 142.00 |
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.