Created attachment 144003 [details] test-suite.log FreeBSD 9.2-STABLE #0 r259483 gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/unit_tests' FAIL: check_clamav PASS: check_freshclam.sh PASS: check_sigtool.sh SKIP: check_unit_vg.sh FAIL: check1_clamscan.sh FAIL: check2_clamd.sh PASS: check3_clamd.sh PASS: check4_clamd.sh SKIP: check5_clamd_vg.sh SKIP: check6_clamd_vg.sh SKIP: check7_clamd_hg.sh SKIP: check8_clamd_hg.sh SKIP: check9_clamscan_vg.sh ======================================== 3 of 7 tests failed (6 tests were not run) See unit_tests/test-suite.log Please report to http://bugs.clamav.net/ ======================================== gmake[3]: *** [test-suite.log] Error 1
After update to FreeBSD 9.3-PRERELEASE #0 r267703 and ports as of 20140621 problem gone. I suppose this PR can be closed, especially if it was just me.
It did not work for me, I was trying upgrade from both clamav-0.98.3_3 and clamav-0.98.3_4 to clamav-0.98.3_6 using portmaster. It worked, however, doing portmaster --force-config security/clamav and disabling compile-time checks. Running the same command second time and re-enabling compile-time checks yields success, so I assume there was some unknown interaction between older clamav installed when running tests with newly compiled test suite.
Somethings fishy here. Tried updating the backup server, first to 9.3-PRERELEASE #0 r267703 Then updated ports as of today (20140622) and got the same error. rebuit python rebuilt unrar ======================================== 3 of 7 tests failed (6 tests were not run) See unit_tests/test-suite.log Please report to http://bugs.clamav.net/ ======================================== There must be someting hiding in another port or the system that I fail to see
(In reply to bsd from comment #2) > It did not work for me, I was trying upgrade from both clamav-0.98.3_3 and > clamav-0.98.3_4 to clamav-0.98.3_6 using portmaster. It worked, however, > doing > > portmaster --force-config security/clamav > > and disabling compile-time checks. Running the same command second time and > re-enabling compile-time checks yields success, so I assume there was some > unknown interaction between older clamav installed when running tests with > newly compiled test suite. +1 for the above Another issue seems to be that the freshclam rc script does not respect the setting in rc.conf: clamav_freshclam_flags="-v -c 18 -u vscan -p /var/amavis/freshclam.pid" gives /usr/local/bin/freshclam -v -c 18 -u vscan -p /var/amavis/freshclam.pid --daemon -p /var/run/clamav/freshclam.pid two times pidfile?
Over to maintainer.
Sorry for the long delay. Are you still seeing these tests failing? Only on FreeBSD 9? I'll work on trying to reproduce it.
We upgraded both boxes running clamav to 10-STABLE and no problems there, cannot tell if still present on 9, do not have access presently to a 9.x cpu for testing. I guess we could set one up if required. Thanks,
I tried to reproduce it on 9.3 amd64 without success. If you check and reproduce it let me know, otherwise I believe we can close this ticket.
I tried recently some upgrade, one of them failed - it was on 8.4-STABLE i386 from clamav-0.98.4_1 to clamav-0.98.4_2. gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.4/unit_tests' FAIL: check_clamav PASS: check_freshclam.sh PASS: check_sigtool.sh SKIP: check_unit_vg.sh PASS: check1_clamscan.sh PASS: check2_clamd.sh PASS: check3_clamd.sh PASS: check4_clamd.sh SKIP: check5_clamd_vg.sh SKIP: check6_clamd_vg.sh SKIP: check7_clamd_hg.sh SKIP: check8_clamd_hg.sh SKIP: check9_clamscan_vg.sh ======================================== 1 of 7 tests failed (6 tests were not run) See unit_tests/test-suite.log Please report to http://bugs.clamav.net/ ======================================== gmake[3]: *** [test-suite.log] Error 1 All other upgrades went smoothly.
Could you please try it again with 0.98.5 to be sure the problem persists? Are you using default OPTIONS? Any change on make.conf?
I did an upgrade now for five servers with no error. I did check OPTIONS was set for TEST, but I don't know the otgers, but I think they are the default. I have some defines set in /etc/make.conf, on one server it has WITHOUT_ATM=YES WITHOUT_FORTRAN=YES WITHOUT_GAMES=YES WITHOUT_INET6=YES WITHOUT_INET6_SUPPORT=YES WITHOUT_KERBEROS=YES WITHOUT_KERBEROS_SUPPORT=YES WITHOUT_NIS=YES WITHOUT_SENDMAIL=YES For me, it is no longer problem now, if necessary, I can just switch the TEST OPTION off if there will be some tests failing in future, but others may not be happy in such case. Anyway, it does not manifests itself with 0.98.5 on any server I administer.
Do you have security/openssl installed?
I just built 0.98.5 on 8.4-STABLE #0 r264402 and 10.1-STABLE #0 r274551 No problems on either. No, we are not using security/openssl, we use openssl from base
It seems to be happening only if openssl from ports is installed, it's being tracked in #195182, closing this one and marked as duplicated since the new ticket is more specific. *** This bug has been marked as a duplicate of bug 195182 ***
In my case OPENSSL from base, too, and I am fine with the way it is resolved.