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 \
$(PROJ_SRC_DIR)/inputs/clam-v3.rar \
$(PROJ_SRC_DIR)/inputs/clam.zip \
$(PROJ_SRC_DIR)/inputs/README \
$(PROJ_SRC_DIR)/inputs/rtf-test/Doc11.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/Doc1.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/Doc22.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/Doc2.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/doc3.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/docCLAMexe.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/rtf1.rtf \
$(PROJ_SRC_DIR)/inputs/rtf-test/rtf-novirus.rtf
RUN_OPTIONS = --debug --exclude-dir .svn --verbose -d$(PROJ_SRC_DIR)/dbdir
-r $(INPUT)
This is what Make generated for me on both machines:
Output/clamscan.simple --debug --exclude-dir .svn --verbose \
-d/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/dbdir
\
-r \
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clam.cab
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clamdoc.tar.gz
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clam.exe
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clam.exe.bz2
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clam-v2.rar
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clam-v3.rar
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/clam.zip
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/README
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/Doc11.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/Doc1.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/Doc22.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/Doc2.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/doc3.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/docCLAMexe.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/rtf1.rtf
\
/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/inputs/rtf-test/rtf-novirus.rtf
I though the dbdir could be the culprit, but it has only one file. Attached
is the output of both.
cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130402/1b21eaf0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ClamAV-output.zip
Type: application/zip
Size: 5376 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130402/1b21eaf0/attachment.zip>
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 the database file, and then loads each one (newer versions would load the database directly, without unpacking to a tmpdir): Loading databases from %s in cli_cvdload() MD5(.tar.gz) = %s in cli_untgz() cli_untgz: Unpacking %s cli_untgz: Unpacking %s As a quick workaround you could remove the daily.cvd from the dbdir and put just a file called: "empty.pdb". You wouldn't be testing ClamAV's digital signature checking code then, but everything else should still work. --Edwin
On 3 April 2013 08:12, Török Edwin <edwin+ml-debian at etorok.net> wrote:> As a quick workaround you could remove the daily.cvd from the dbdir and > put just a file called: "empty.pdb". > You wouldn't be testing ClamAV's digital signature checking code then, but > everything else should still work. >I see. That looks like an important test (at least from a compiler point of view), so I'll see if I can sort the list of files in the temp dir, too. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130403/e133d508/attachment.html>
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. Attached is the output of both. >> > > The version of ClamAV in the LLVM test-suite is quite old,In the interests of having relevant metrics - should we update to a more recent version?> and it first unpacks the database file, and then loads each one (newer versions > would load the database directly, without unpacking to a tmpdir): > > Loading databases from %s > in cli_cvdload() > MD5(.tar.gz) = %s > in cli_untgz() > cli_untgz: Unpacking %s > cli_untgz: Unpacking %s > > As a quick workaround you could remove the daily.cvd from the dbdir and put just a file called: "empty.pdb". > You wouldn't be testing ClamAV's digital signature checking code then, but everything else should still work. > > --Edwin > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev