similar to: [LLVMdev] LNT ClamAV Output

Hi Torok, I've used a hard-coded list on the input parameter and still got some output (slightly) scrambled between two different bots... INPUT = $(PROJ_SRC_DIR)/inputs/clam.cab \ $(PROJ_SRC_DIR)/inputs/clamdoc.tar.gz \ $(PROJ_SRC_DIR)/inputs/clam.exe \ $(PROJ_SRC_DIR)/inputs/clam.exe.bz2 \ $(PROJ_SRC_DIR)/inputs/clam-v2.rar \

On 04/03/2013 01:20 AM, Renato Golin wrote: > Hi Torok, > > I've used a hard-coded list on the input parameter and still got some output (slightly) scrambled between two different bots... > > I though the dbdir could be the culprit, but it has only one file. Attached is the output of both. > The version of ClamAV in the LLVM test-suite is quite old, and it first unpacks

On Wed, Apr 3, 2013 at 12:12 AM, Török Edwin <edwin+ml-debian at etorok.net> wrote: > On 04/03/2013 01:20 AM, Renato Golin wrote: >> Hi Torok, >> >> I've used a hard-coded list on the input parameter and still got some output (slightly) scrambled between two different bots... >> >> I though the dbdir could be the culprit, but it has only one file.

On 04/15/2013 11:01 AM, David Blaikie wrote: > On Wed, Apr 3, 2013 at 12:12 AM, Török Edwin <edwin+ml-debian at etorok.net> wrote: >> On 04/03/2013 01:20 AM, Renato Golin wrote: >>> Hi Torok, >>> >>> I've used a hard-coded list on the input parameter and still got some output (slightly) scrambled between two different bots... >>> >>>

On 2 April 2013 21:20, Török Edwin <edwin+ml-debian at etorok.net> wrote: > You can pass all the filenames from the inputs/ directory directly on the > command-line, instead of specifying -r inputs/. > That way the order of scanning will be exactly the one specified on the > command-line. > Hum, I think I can fix that with Make... --renato -------------- next part

Hi Renato, What is it that makes the output of the program asynchronous? The output is deterministic on Darwin, so it seems like it should be possible to make it more stable. I'm not really a fan of doing any more transformations on the output than we have to, because it just pushes complexity into the test suite infrastructure. - Daniel On Tue, Apr 2, 2013 at 10:05 AM, Renato Golin

Hi all, Looking into ClamAV, it seems that the output is highly asynchronous, so a simple diff is obviously bogus. Since the output is mainly a report of what's happening, without any logical sequence, I can sort both outputs and diff them, for a similar (though not perfect) result. If you sort clamscan.out-nat and clamscan.out-simple, you'll see that they're identical. I'm not

On 04/02/2013 11:06 PM, Daniel Dunbar wrote: > On Tue, Apr 2, 2013 at 11:46 AM, Renato Golin <renato.golin at linaro.org <mailto:renato.golin at linaro.org>> wrote: > > On 2 April 2013 19:20, Daniel Dunbar <daniel at zuster.org <mailto:daniel at zuster.org>> wrote: > > What is it that makes the output of the program asynchronous? The output is

On Tue, Apr 2, 2013 at 11:46 AM, Renato Golin <renato.golin at linaro.org>wrote: > On 2 April 2013 19:20, Daniel Dunbar <daniel at zuster.org> wrote: > >> What is it that makes the output of the program asynchronous? The output >> is deterministic on Darwin, so it seems like it should be possible to make >> it more stable. >> > > This is a virus

On Fri, Apr 19, 2013 at 1:13 PM, Renato Golin <renato.golin at linaro.org>wrote: > On 19 April 2013 17:48, Török Edwin <edwin at etorok.net> wrote: > >> Otherwise what might seem like a 20% improvement >> could very well be just a 0.2% improvement in practice. >> > > This is (maybe to a lesser extent) what happens with most of our > benchmarks, and

On 2 April 2013 19:20, Daniel Dunbar <daniel at zuster.org> wrote: > What is it that makes the output of the program asynchronous? The output > is deterministic on Darwin, so it seems like it should be possible to make > it more stable. > This is a virus scan and, AFAICS, depends on the order in which the INODEs are laid out in the directory. I'm not sure there is a way to

On 19 April 2013 17:48, Török Edwin <edwin at etorok.net> wrote: > Otherwise what might seem like a 20% improvement > could very well be just a 0.2% improvement in practice. > This is (maybe to a lesser extent) what happens with most of our benchmarks, and running them 3 times doesn't add that much confidence but makes it run much slower. I end up treating the test-suite as

Hi Since the buildbot host was updated to Fedora F20 levels, the clang buildbot has been failing with the following: $ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt --no-timestamp --cc /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++

This is probably another area where a bit of dynamic behavior could help. When we find a regressions, kick off some runs to bisect back to where it manifests. This is what we would be doing manually anyway. We could just search back with the set of regressing benchmarks, meaning the whole suite does not have to be run (unless it is a global regression). There are situations where we see commit

On 30 June 2013 10:14, Anton Korobeynikov <anton at korobeynikov.info> wrote: > 1. Increasing sample size to at least 5-10 > That's not feasible on slower systems. A single data point takes 1 hour on the fastest ARM board I can get (Chromebook). Getting 10 samples at different commits will give you similar accuracy if behaviour doesn't change, and you can rely on 10-point

Hi folks, Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg. At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership, Don't know if it is my actual config (previous one untouched anyway), but this is what

On 30 April 2014 10:21, Tobias Grosser <tobias at grosser.es> wrote: > To my understanding, the first patches should just improve LNT to report how > reliable the results are it reports. So there is no way that this can effect > the test suite runs, which means I do not see why we would want to delay > such changes. > > In fact, if we have a good idea which kernels are

Hi, I am running CentOS Linux release 7.6.1810 (Core) with ClamAV installed. When i am running freshclam i am seeing a Warning message and the details are described below:- # freshclam ClamAV update process started at Thu Dec 13 11:49:18 2018 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.2 Recommended version: 0.101.0 DON'T PANIC! Read

Hi All, I installed clam on CentOS 5 as below. yum install clamav clamav-db clamd I got them form Dag. below are the RPMS I installed. [root at box ~]# rpm -qa |grep clam clamav-db-0.90.2-1.el4.rf clamd-0.90.2-1.el4.rf clamav-0.90.2-1.el4.rf But, when I restart clam it gives following error. [root at box init.d]# /etc/init.d/clamd restart Stopping Clam AntiVirus Daemon:

Me again, I'm still building my new mail server and I'm struggling getting clamav and exim to talk to each other. I've installed: clamav-server-0.98.7-1.el7.x86_64 clamav-lib-0.98.7-1.el7.x86_64 clamav-0.98.7-1.el7.x86_64 clamav-milter-0.98.7-1.el7.x86_64 clamav-data-0.98.7-1.el7.noarch clamav-update-0.98.7-1.el7.x86_64 clamav-milter-systemd-0.98.7-1.el7.noarch