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
[tests] FullCleanTest.test_private_map_was_generated timeouts when running in container #3283
Comments
Optionally, we might have an env.variable (with current default) to customize the |
That's interesting, most of my testing happens on a container on my laptop, not seen any timeout issues like this so far. Albeit it's an LXD container and not podman/buildah/docker |
The "container blame" is just a theory as I dont exactly know the full environment where we noticed such timeouts. The lengthy plugins usually run much faster (esp. |
How are these potentially problematic containers launched, exactly? Containers are in most respects the same as running on bare metal, so this kind of performance drop is surprising. That being said, |
We are still investigating this, but we can make #3288 raised for it. |
When running avocado tests in a container(*), this test easily timeouts despite it has 10 minutes timeout (https://github.com/sosreport/sos/blob/main/tests/cleaner_tests/full_report/full_report_run.py#L25).
The main cause is
sos report
takes 8 minutes (while subsequentclean
is supposed to run a few times longer, so even 20 minutes timeout might not be sufficient). We can increase the timeout as a defensive resolution, but .. to what value? Also does it make sense to optimise the run somehow? Since the most lengthy plugins are:(*) I think the fact sos runs in container vastly contributes to the duration of all those plugins (esp.
cgroups
).Does it make sense to call this
sos
with option e.g.--plugin-timeout 60
(or maybe90
)? For the sake of cleaner testing, we are not much interested in files like/sys/fs/cgroup/cpuacct/system.slice/sys-kernel-config.mount/tasks
(collecting this file took over 2 seconds alone).The text was updated successfully, but these errors were encountered: