Actions
action #163391
opentest fails in clamav: test needs to be optimized / aligned with clamav system reqs
Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2024-07-05
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
While debugging https://bugzilla.opensuse.org/show_bug.cgi?id=1227404 (originally filed as product bug), it turned out that there are 'just' a few things with the test that are not 'right'
Please ensure to reach out to Reinhard Max vor input on the optimizations! He has good understanding of how clamav acts/reacts and this knowledge should be used.
Few things we identified:
- https://docs.clamav.net/Introduction.html?highlight=system%20requirements#recommended-system-requirements -The requirements are 3GB+ (we run on a 2GB machine - and the test fails on OOM, clamscan being killed)
- while clamscan runs (and consumes a lot of memory), there is a 2nd instance of clamav running as 'clamd' (the daemon) - further pushing on the memory
- the clamscan calls redirecting their output to a log file, which is only printed in success cases, makes debugging needlessly complicated (the log is not even uploaded on failure); Proposal: send output to tty
- On successful runs, clamd, freshclam are stopped twice (end of run() plus post_run_hook
And Max certainly has more input than that
openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
clamav
Test suite description¶
Same as jeos, plus some more tests.
Reproducible¶
Fails since (at least) Build 20240612
Expected result¶
Last good: 20240611 (or more recent)
Further details¶
Always latest result in this scenario: latest
Actions