llvm dev - Jan 2018 - svn problem checking out test suite

It could be.  I am not sure what is running upstream of the affected 
machines though it is odd that only those using late releases of svn are 
affected.

I did try using https for a by-hand checkout and that worked but I don't 
know how to change the buildbots to use https instead of http.  I sent a 
note off to the person who runs the buildbot master.

On 01/26/2018 02:22 PM, Don Hinton wrote:
> Not sure if this applies, but at least one antivirus engine thinks 
> MultiSource/Applications/ClamAV/inputs/rtf-test/docCLAMexe.rtf is
malicious.
> 
>
https://www.hybrid-analysis.com/sample/bba4eab51c27a6ffbd86bf870048da1902cc7235a4de49cf30208906dac50f85?environmentId=100
>
<https://www.hybrid-analysis.com/sample/bba4eab51c27a6ffbd86bf870048da1902cc7235a4de49cf30208906dac50f85?environmentId=100>
> 
> 
> On Fri, Jan 26, 2018 at 11:02 AM, Bill Seurer via llvm-dev 
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at
lists.llvm.org>> wrote:
> 
>     There are lots and lots of .rtf files and it is just these 3 and
>     just on certain systems.
> 
>     On 01/26/2018 11:41 AM, James Y Knight wrote:
> 
>         You likely have an http proxy in your network which is blocking
>         RTF files in case they are viruses or something. You might try
>         https, if you're lucky it will bypass your proxy.
> 
> 
> 
>     -- 
> 
>     -Bill Seurer
> 
>     _______________________________________________
>     LLVM Developers mailing list
>     llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>     http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>     <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> 
> 

-- 

-Bill Seurer

Hi Bill,

I believe you just need to update the urls in the various .py files at
http://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/
<http://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/>.
After that, the buildmaster will need restarting. Hopefully all the bots support
https, but it can be made optional if that's not the case.
> On 26 Jan 2018, at 12:45, Bill Seurer via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> It could be.  I am not sure what is running upstream of the affected
machines though it is odd that only those using late releases of svn are
affected.
> 
> I did try using https for a by-hand checkout and that worked but I
don't know how to change the buildbots to use https instead of http.  I sent
a note off to the person who runs the buildbot master.
> 
> On 01/26/2018 02:22 PM, Don Hinton wrote:
>> Not sure if this applies, but at least one antivirus engine thinks
MultiSource/Applications/ClamAV/inputs/rtf-test/docCLAMexe.rtf is malicious.
>>
https://www.hybrid-analysis.com/sample/bba4eab51c27a6ffbd86bf870048da1902cc7235a4de49cf30208906dac50f85?environmentId=100
<https://www.hybrid-analysis.com/sample/bba4eab51c27a6ffbd86bf870048da1902cc7235a4de49cf30208906dac50f85?environmentId=100>
>> On Fri, Jan 26, 2018 at 11:02 AM, Bill Seurer via llvm-dev <llvm-dev
at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>    There are lots and lots of .rtf files and it is just these 3 and
>>    just on certain systems.
>>    On 01/26/2018 11:41 AM, James Y Knight wrote:
>>        You likely have an http proxy in your network which is blocking
>>        RTF files in case they are viruses or something. You might try
>>        https, if you're lucky it will bypass your proxy.
>>    --     -Bill Seurer
>>    _______________________________________________
>>    LLVM Developers mailing list
>>    llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>>    http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>    <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> 
> 
> -- 
> 
> -Bill Seurer
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180126/aa9dbd50/attachment.html>

Looks like

         f.addStep(SVN(name='svn-test-suite',
                       mode='update', 
baseURL='http://llvm.org/svn/llvm-project/test-suite/',
                       defaultBranch='trunk',
                       workdir='test/test-suite'))

is what needs to be changed (in ClangBuilder.py).


On 01/26/2018 06:13 PM, Daniel Sanders wrote:
> Hi Bill,
> 
> I believe you just need to update the urls in the various .py files at 
> http://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/. 
> After that, the buildmaster will need restarting. Hopefully all the bots 
> support https, but it can be made optional if that's not the case.
> 
>> On 26 Jan 2018, at 12:45, Bill Seurer via llvm-dev 
>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at
lists.llvm.org>> wrote:
>>
>> It could be.  I am not sure what is running upstream of the affected 
>> machines though it is odd that only those using late releases of svn 
>> are affected.
>>
>> I did try using https for a by-hand checkout and that worked but I 
>> don't know how to change the buildbots to use https instead of
http.
>>  I sent a note off to the person who runs the buildbot master.
>>
>> On 01/26/2018 02:22 PM, Don Hinton wrote:
>>> Not sure if this applies, but at least one antivirus engine thinks 
>>> MultiSource/Applications/ClamAV/inputs/rtf-test/docCLAMexe.rtf is 
>>> malicious.
>>>
https://www.hybrid-analysis.com/sample/bba4eab51c27a6ffbd86bf870048da1902cc7235a4de49cf30208906dac50f85?environmentId=100
>>>
<https://www.hybrid-analysis.com/sample/bba4eab51c27a6ffbd86bf870048da1902cc7235a4de49cf30208906dac50f85?environmentId=100>
>>> On Fri, Jan 26, 2018 at 11:02 AM, Bill Seurer via llvm-dev 
>>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at
lists.llvm.org>
>>> <mailto:llvm-dev at lists.llvm.org>> wrote:
>>>    There are lots and lots of .rtf files and it is just these 3 and
>>>    just on certain systems.
>>>    On 01/26/2018 11:41 AM, James Y Knight wrote:
>>>        You likely have an http proxy in your network which is
blocking
>>>        RTF files in case they are viruses or something. You might
try
>>>        https, if you're lucky it will bypass your proxy.
>>>    --     -Bill Seurer
>>>    _______________________________________________
>>>    LLVM Developers mailing list
>>> llvm-dev at lists.llvm.org <mailto:llvm-dev at
lists.llvm.org>
>>> <mailto:llvm-dev at lists.llvm.org>
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>>    <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
>>
>>
>> -- 
>>
>> -Bill Seurer
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 

-- 

-Bill Seurer