CI: test overlay and vfs#20161
Conversation
00ab112 to
1246120
Compare
|
Draft because I'm pretty sure this is going to fail due to missing settings in .cirrus.yml |
|
Awright, who wants to speculate on why overlay make (only) podman-remote slower? |
|
@edsantiago can you share a link to the timing results? |
|
Durrr. Sorry.
|
|
Are you sure they're slower and did not hang+timeout? |
|
Good question. No, I'm not sure, but my reasoning is that all the test logs end at about 2900s, which is ~48m, which is close to the 50m limit. And the tail of each log is different (different tests). Granted, buffering means that we probably don't get to see the very very tail ... but in non-overlay tests, we never get to 2900s, so I still think something is slowing down. If I were more talented/hardworking/capable I'd write a minitool to check timestamps on each line and look for big jumps; or to compare against a regular vfs run. Maybe I'll do so today. |
1246120 to
9903e2f
Compare
|
Here we go. This is a comparison of a good (standard) CI run against a bad one (this PR). Some tests run faster with overlay, but the huge majority run slower. I'm still trying to chase this down, but ITM would anyone like to look at the table below and see if they can figure out a common factor among the slow tests?
Methodology: I grabbed timing results from |
bb006e9 to
f0f3b0b
Compare
|
Cockpit tests failed for commit f0f3b0be736b96993c2d720ebc30ccad9a03fa32. @martinpitt, @jelly, @mvollmer please check. |
f0f3b0b to
bb7634b
Compare
|
I need help with this permissions-check failure: I cannot reproduce on 1minutetip, because on a default 1minutetip the permissions are correct: Somehow, under Cirrus, the There's also a |
test/e2e/common_test.go
Outdated
There was a problem hiding this comment.
This fixes the test hang.
We actually have a long history with this issue of leaked mounts: https://github.com/containers/buildah/blob/0d717cd0a52376c80cb527a344a1d7446b0d56e7/tests/helpers.bash#L116-L123
That dates to 2020. See containers/buildah#1991 .
Is there really no way to fix this leak?
8e93f67 to
6d2e4b6
Compare
|
@giuseppe PTAL |
|
Eyeballs welcome, but this is not ready to merge. I'm seeing a LOT of new flakes, like this new container-cp one. |
e33f221 to
3a2dea7
Compare
3a2dea7 to
e7b22f0
Compare
185b678 to
559d688
Compare
|
As a fun side note, vfs seems to be slower than overlay. Is this expected?
Summary: all Anyhow, everyone probably knew that already, this is just confirmation that overlay is better. The horrible #20282 flake is another confirmation. |
559d688 to
6ac8e40
Compare
|
Cockpit tests failed for commit 5123917085ccc86f6e959c95ebac43bda9a79126. @martinpitt, @jelly, @mvollmer please check. |
|
Cockpit tests failed for commit 55c4ed8c84e2889879debce9bc7bfbd8c1729ce4. @martinpitt, @jelly, @mvollmer please check. |
|
@containers/podman-maintainers I am marking this as ready for review... with one big fat warning: #20282. That has gone from failing every other run, to failing not at all in one week. That concerns me. I see two choices:
|
|
Cockpit tests failed for commit 881cdae821d5974522f390f407c3e8ff8dd651c4. @martinpitt, @jelly, @mvollmer please check. |
|
Cockpit tests failed for commit 2bbf47854143075fe75674c7d68917e510224b21. @martinpitt, @jelly, @mvollmer please check. |
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
Cockpit tests failed for commit 254b9e59427822d4b4f040931a585329f332563b. @martinpitt, @jelly, @mvollmer please check. |
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
Cockpit tests failed for commit fe0b71afabe599b17ebfbeba5fb7473d899b7ade. @martinpitt, @jelly, @mvollmer please check. |
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
This is as ready as I can make it. Any feedback on my flake question?
|
Luap99
left a comment
There was a problem hiding this comment.
LGTM, I fine to merge is as. If it flakes to often we can always skip later.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
We're only testing vfs in CI. That's bad. containers#18822 tried to remedy that but that only worked on system tests, not e2e. Here we introduce CI_DESIRED_STORAGE, to be set in .cirrus.yml in the same vein as all the other CI_DESIRED_X. Since it's 2023 we default to overlay, testing vfs only in priorfedora. Fixes required: - e2e tests: - in cleanup, umount ROOT/overlay to avoid leaking mounts - system tests: - fix a few badly-written tests that assumed/hardcoded overlay - buildx test: add weird exception to device-number test - mount tests: add special case code for vfs - unprivileged test: disable one section that is N/A on vfs Signed-off-by: Ed Santiago <santiago@redhat.com>
|
/lgtm |
We're only testing vfs in CI. That's bad. #18822 tried to
remedy that but that only worked for system tests, not e2e.
Here we introduce CI_DESIRED_STORAGE, to be set in .cirrus.yml
in the same vein as all the other CI_DESIRED_X. Since it's 2023
we default to overlay, testing vfs only in priorfedora.
Skip the "split imagestore" test under overlay (#19748)
Signed-off-by: Ed Santiago santiago@redhat.com