This is the same infrequent check failure we've observed. On our test systems, this only seems to occur when the ESX infrastructure is under heavy use (like when there are VM migrations, etc).
It looks like an oversight in our implementation of the 'check' based test suite. The 'T' environment variable only appears to affect the timeout for the "tc_cl_scan" tests in check_clamav.c: https://github.com/Cisco-Talos/clamav-devel/blob/dev/0.103/unit_tests/check_clamav.c#L706 All other tests either use default (4 seconds) or have the timeout hardcoded to 20 seconds. It should be trivial to make the 'T' environment variable work everywhere, and to increase the timeout from 4 seconds for the "tc_cl" tests where you're seeing the error (https://github.com/Cisco-Talos/clamav-devel/blob/dev/0.103/unit_tests/check_clamav.c#L667). As a side note, I wish to get away from using 'check' and switch to something like googletest, ctest, and/or cunit as we also migrate to cmake. -Micah On 11/22/19, 4:29 AM, "clamav-users on behalf of Frans de Boer" <[email protected] on behalf of [email protected]> wrote: On 21-11-2019 21:08, Frans de Boer wrote: > On 21-11-2019 20:44, Frans de Boer wrote: >> LS, >> >> I get the next report (all systems): >> /configure: line 30094: auto=yes: command not found >> >> Also, check_clamav failed on 2 different systems (openSUSE 15.1). It >> did not failed on openSUSE Tumbleweed. >> >> --- Frans. >> >> >> >> _______________________________________________ >> >> clamav-users mailing list >> [email protected] >> https://lists.clamav.net/mailman/listinfo/clamav-users >> >> >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml > > Forgot to mention the log content: > > FAIL: check_clamav > ================== > > Using default test timeout; alter by setting 'T' env var (in seconds) > Running suite(s): cl_api > cli > jsnorm > str > regex > disasm > unique > matchers > htmlnorm > bytecode > 99%: Checks: 989, Failures: 1, Errors: 0 > ../../clamav-0.102.1/unit_tests/check_clamav.c:90:F:cl_dup:test_cl_retver:0: > cl_retver > NOTICE: Use the 'T' environment variable to adjust testcase timeout > FAIL check_clamav (exit status: 1) > > It is a Phenom II at 3.7 GHz and no other processes taking much time. > > -- Frans. > Tried export T=30/300/3000, but failure still comes within 10-15 seconds. So, T does nothing here. --- Frans. _______________________________________________ clamav-users mailing list [email protected] https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml _______________________________________________ clamav-users mailing list [email protected] https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
