<div dir="ltr">Hi Will,<div><br></div><div style>No, I haven't looked into that since the release process started. I will once it's all finished, but I don't think there's anything to do with how the directories are scanned.</div>
<div style><br></div><div style>It seems that the order comes up from exploding a packed file, but I've added a sort into that packed file and the order is still different.</div><div style><br></div><div style>ClamAV is an old program, and I'm not sure what's the benefit of running it, if there's anything special about it, but I wouldn't mind disabling some functionality to avoid random output.</div>
<div style><br></div><div style>cheers,</div><div style>--renato</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 4 June 2013 21:29, Will Schmidt <span dir="ltr"><<a href="mailto:will_schmidt@vnet.ibm.com" target="_blank">will_schmidt@vnet.ibm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 2013-05-08 at 11:16 -0500, Hal Finkel wrote:<br>
> Renato,<br>
><br>
> We're now seeing a new problem with the ClamAV test. This problem does not seem to show up if you run the test-suite from the command line, but only when run through LNT (although this could obviously mean many things).<br>
<br>
Hi Renato, Hal,<br>
Have either of you made any headway on the clamAV issue on ppc64? I<br>
cleared up the directories on the buildbot this morning, to verify we<br>
aren't running with any old code, and see the issue remains.<br>
<br>
<a href="http://fpaste.org/16559/37707613/" target="_blank">http://fpaste.org/16559/37707613/</a><br>
<br>
The gist of the issue is that the "Matched signature for file type..."<br>
messages are appearing out of order.<br>
<br>
I did look for a 'scanned directories' reference that was mentioned<br>
earlier, and that content seems consistent between .out-nat<br>
and .out-simple.<br>
<br>
clamscan.out-nat:Scanned directories: 0<br>
clamscan.out-nat:Scanned files: 16<br>
clamscan.out-simple:Scanned directories: 0<br>
clamscan.out-simple:Scanned files: 16<br>
<br>
<br>
Thanks,<br>
-Will<br>
<br>
<br>
<br>
<br>
><br>
> <a href="http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux/builds/2793/steps/lnt.nightly-test/logs/test.log" target="_blank">http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux/builds/2793/steps/lnt.nightly-test/logs/test.log</a> has:<br>
><br>
> cp /home/clangbuild/clang-ppc64-1/test-suite/instant.txt Output/clamscan.out-nat.time<br>
> /home/clangbuild/clang-ppc64-1/test-suite/DiffOutput.sh "diff " simple clamscan<br>
> ******************** TEST (simple) 'clamscan' FAILED! ********************<br>
> Execution Context Diff:<br>
> 1304,1305d1303<br>
> < Matched signature for file type %s<br>
> <<br>
> 1372a1371,1372<br>
> > Matched signature for file type %s<br>
> ><br>
> 1693,1694d1692<br>
> < Matched signature for file type %s<br>
> <<br>
> 1761a1760,1761<br>
> > Matched signature for file type %s<br>
> ><br>
> 1965,1966d1964<br>
> < Matched signature for file type %s<br>
> <<br>
> 2033a2032,2033<br>
> > Matched signature for file type %s<br>
> ><br>
> 2321,2322d2320<br>
> < Matched signature for file type %s<br>
> <<br>
> 2388a2387,2388<br>
> ><br>
> > Matched signature for file type %s<br>
><br>
> So these 'Matched signature' lines are appearing out of order somehow. Will put the diff -u here: <a href="http://fpaste.org/10881/79449211/" target="_blank">http://fpaste.org/10881/79449211/</a><br>
><br>
> Do you have any idea what could cause this?<br>
><br>
> Thanks again,<br>
> Hal<br>
><br>
> ----- Original Message -----<br>
> ><br>
> > On 26 April 2013 15:15, Hal Finkel < <a href="mailto:hfinkel@anl.gov">hfinkel@anl.gov</a> > wrote:<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > I ran svn update (in the test suite directory) yesterday. It was<br>
> > missing only r180566, and that test (pcompress2) was fine. Running<br>
> > svn diff reports no local changes. diffing the<br>
> > MultiSource/Applications/ ClamAV/Output/clamscan.out-nat with<br>
> > llvm-trunk/projects/test- suite/MultiSource/<br>
> > Applications/ClamAV/clamscan. reference_output reports no<br>
> > differences.<br>
> ><br>
> ><br>
> > Your out-nat is correct, what's weird is your out-simple. It's as it<br>
> > would be on the old code, without sorting, as if you got the updated<br>
> > reference output but not the updated source code... Ex:<br>
> ><br>
> ><br>
> > 2955c2957<br>
> ><br>
> ><br>
> > < Scanned directories: 1<br>
> > ---<br>
> > > Scanned directories: 0<br>
> ><br>
> ><br>
> > Currently, no directories are scanned because the code first<br>
> > retrieves the list of files (recursively), sorts them, and then<br>
> > scans, it doesn't scan any dir, only specific files. The old code<br>
> > used to...<br>
> ><br>
> ><br>
> > --renato<br>
> ><br>
> ><br>
> > PS: This is another source of randomness, the order in which inodes<br>
> > appear in a directory, but it was supposedly all removed, and<br>
> > definitely on ClamAV.<br>
> _______________________________________________<br>
> llvm-commits mailing list<br>
> <a href="mailto:llvm-commits@cs.uiuc.edu">llvm-commits@cs.uiuc.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br>
><br>
<br>
<br>
</blockquote></div><br></div>