Bugzilla – Bug 1227404
[Build 20240703] openQA test fails in clamav: timeout of 300s reached scanning eicar test file
Last modified: 2024-07-05 11:50:25 UTC
## Observation The test uses an eicar test file to validate clamav, but clamscan -i --log=clamscan.log eicar_test_files runs for 5 minutes and does not return to the CLI prompt. That sounds very excessive Clamav has just been updated to version 1.3.1 (from 0.103) openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in [clamav](https://openqa.opensuse.org/tests/4318292/modules/clamav/steps/96) ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20240612](https://openqa.opensuse.org/tests/4268502) ## Expected result Last good: [20240611](https://openqa.opensuse.org/tests/4266212) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=JeOS-for-kvm-and-xen&machine=64bit_virtio-2G&test=jeos-extra&version=Tumbleweed)
Where can I find the files that are used in this test, so that I can try to reproduce the failure outside of OpenQA?
(In reply to Dominique Leuenberger from comment #0) > runs for 5 minutes and does not return to the CLI prompt. That sounds very > excessive Newer versions of ClamAV are known to run slower, partly because some default limits were raised and because these raied defaults reveal a longer existing performance issue when scanning certain PDF files. I warned about this upfront, but we need to proceed the update anyway, because version 0.103 will be EOL soon.
(In reply to Reinhard Max from comment #1) > Where can I find the files that are used in this test, so that I can try to > reproduce the failure outside of OpenQA? https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/data/eicar_test_files These are the three test files that are downloaded into a directory named "eicar_test_files" and then clamav started as $ > clamscan -i --log=clamscan.log eicar_test_files
Hmm, that takes only about 15 seconds on my less than current x86_64 workstation. It would be interesting to see the normal output of clamscan in that situation rather than reducing and redirecting it to a file. On my machine it looks like this: -------------------------------------------------------------------------------- $ clamscan eicar_test_files Loading: 12s, ETA: 0s [========================>] 8.70M/8.70M sigs Compiling: 2s, ETA: 0s [========================>] 41/41 tasks /[...]/eicar_test_files/eicar.zip: Eicar-Signature FOUND /[...]/eicar_test_files/eicar.txt: Eicar-Signature FOUND /[...]/eicar_test_files/eicar.pdf: Pdf.Dropper.Agent-7001939-0 FOUND ----------- SCAN SUMMARY ----------- Known viruses: 8695659 Engine version: 1.3.1 Scanned directories: 1 Scanned files: 3 Infected files: 3 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 1.00:1) Time: 15.306 sec (0 m 15 s) Start Date: 2024:07:04 18:55:02 End Date: 2024:07:04 18:55:17 -------------------------------------------------------------------------------- Please also try to run the test with a doubled timeout to see if it then completes.
While debugging this, we came to the conclusion that the issue is openQA's setup for that test and have thus moved the issue to https://progress.opensuse.org/issues/163391