search for: seurer

...example, http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/20127) and also when I build it locally: FAIL: Clang :: CodeGenCXX/main-norecurse.cpp (2951 of 27722) ******************** TEST 'Clang :: CodeGenCXX/main-norecurse.cpp' FAILED ******************** Script: -- /home/seurer/llvm/build/llvm-test/./bin/clang -cc1 -internal-isystem /home/seurer/llvm/build/llvm-test/bin/../lib/clang/3.8.0/include -nostdsysteminc -emit-llvm /home/seurer/llvm/llvm-test/tools/clang/test/CodeGenCXX/main-norecurse.cpp -o - | /home/seurer/llvm/build/llvm-test/./bin/FileCheck /home/seurer/l...

...e-linux/builds/3636 Any ideas? Thanks! Here's the full output from one of the failures: FAIL: MemorySanitizer-powerpc64le :: Linux/mallinfo.cc (34091 of 34964) ******************** TEST 'MemorySanitizer-powerpc64le :: Linux/mallinfo.cc' FAILED ******************** Script: -- /home/seurer/llvm/build/llvm-test/./bin/clang --driver-mode=g++ -fsanitize=memory -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -fno-function-sections -gline-tables-only -O0 -g /home/seurer/llvm/llvm-test/projects/compiler-rt/test/msan/Linux/mallinfo.cc -o /home/seu...

...tls_dynamic.cc LeakSanitizer-Standalone-powerpc64 :: TestCases/Linux/use_tls_dynamic.cc MemorySanitizer-POWERPC64 :: dtls_test.c I looked at dtls_test.c in detail ******************** TEST 'MemorySanitizer-POWERPC64 :: dtls_test.c' FAILED ******************** Script: -- /home/seurer/llvm/build/llvm-test/./bin/clang -fsanitize=memory -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -gline-tables-only -g /home/seurer/llvm/llvm-test/projects/compiler-rt/test/msan/dtls_test.c -o /home/seurer/llvm/build/llvm-test/projects/compiler-rt/tes...

...brid-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: > > Yo...

> On 2015-Nov-05, at 08:31, Aaron Ballman <aaron at aaronballman.com> wrote: > > On Thu, Nov 5, 2015 at 11:26 AM, James Molloy <james at jamesmolloy.co.uk> wrote: >> Ah I see. >> >> I can't think of a way that would help users in any particular way offhand. >> I hadn't considered exposing it to clang users - do you think there is merit

...roject/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...

...ust 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

On 9/13/17 10:31 AM, Peter Bergner via llvm-dev wrote: > On 9/12/17 8:15 PM, Bill Seurer via llvm-dev wrote: >> I updated one of my powerpc64le llvm test systems to Fedora 25 and I >> started getting a whole bunch of sanitizer test case failures.  I tried >> testing some earlier revisions on the new OS that had worked fine under >> the old but they generate the...

...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/bba4eab51c27a6ffbd86bf870048da 1902cc7235a4de49cf30208906dac50f85?environmentId=100 On Fri, Jan 26, 2018 at 11:02 AM, Bill Seurer via llvm-dev < 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 file...

...d this problem on a compiler-rt change too. It was on the clang-cmake-mips builder earlier this week. ________________________________________ From: llvm-dev [llvm-dev-bounces at lists.llvm.org] on behalf of Renato Golin via llvm-dev [llvm-dev at lists.llvm.org] Sent: 30 October 2015 08:34 To: Bill Seurer Cc: LLVM Dev Subject: Re: [llvm-dev] Revisions that cause buildbot problems but aren't on blame lists On 30 October 2015 at 14:48, Bill Seurer via llvm-dev <llvm-dev at lists.llvm.org> wrote: > It appears this happens when (for instance) one of the test cases in > projects/test-sui...

...d cannot get it to work right. However, it isn't really documented anywhere so maybe I didn't set it up properly. Plus there's all the mention of llvmgcc... So is anyone doing this? Is there some setup information that I missed? Thanks for any tips on how to do this! -- -Bill Seurer

...ppens when (for instance) one of the test cases in projects/test-suite is updated and causes a failure. Such a revision also won't kick off a new test cycle. Should the bots be including their test cases in determining blame lists and when to run or was this left off on purpose? -- -Bill Seurer

Hi Bill, The PPC LNT buildbot is randomly failing on LNT because of timeouts. http://lab.llvm.org:8011/builders/clang-ppc64le-linux-lnt I've checked all recent LNT failures and they were spotted on some processes (lua, sqlite3, tramp3d, expandfft, etc), so I doubt this is in any was a real time out due to code-gen issues. I imagine they're all at the edge already and the standard

...8011/builders/clang-cmake-mips/builds/10220 and the commit that caused it was 'r251331 [compiler-rt] Fix ptrace interceptor for aarch64'. ________________________________ From: Galina Kistanova [gkistanova at gmail.com] Sent: 02 November 2015 16:03 To: Daniel Sanders Cc: Renato Golin; Bill Seurer; LLVM Dev Subject: Re: [llvm-dev] Revisions that cause buildbot problems but aren't on blame lists Hello Bill, Daniel, Could you point me to the exact build and tell me the correct revision to blame, please? Most likely, this means that your bot defines wrong dependencies. I can look in to t...

...mac running svn 1.9.4. 1.9.7 on a powerpc64 BE machine or on the mac with 1.9.4 always eventually gives the "Connection reset by peer" and 1.9.7 hangs on a powerpc64 LE machine. Is there be something wrong with those 3 files? I am really hoping that svn isn't broken. -- -Bill Seurer

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. On Fri, Jan 26, 2018 at 11:13 AM, Bill Seurer via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I updated one of the powerpc64 lnt buildbot machines to a new OS release > and the buildbot started failing every run when it tries to check out the > test suite. > > The checkout will run for a while then always fails like t...

...led in my commit r272505 which is unrelated. > >> > >> > http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883 > >> > >> -- Sean Silva > > > > > > > -- -Bill Seurer

On 10/29/2015 07:40 AM, Bill Seurer wrote: > On 10/28/15 23:47, Philip Reames via llvm-dev wrote: > > This long running bot failed on a unused variable warning. Given that > > several other bots cover the warnings, any chance we could get this one > > configured to not fail the build on warnings? Doing so would...

This just failed again: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/1579 Bill, could you take a look at this? This is like the 3rd time I've been incorrectly pinged by this buildbot due to this issue. -- Sean Silva On Mon, Jun 13, 2016 at 8:07 PM, Sean Silva <chisophugis at gmail.com> wrote: > Thanks for taking a look. The flaky ASan test failure in the

...eason: scheduler > Build Source Stamp: [branch trunk] 225670 > Blamelist: ab,abataev,alexfh,artagnon,benlangmuir,chandlerc,chapuni,compnerd,dexonsmith,djasper,dsanders,ehsan,eugenis,foad,gribozavr,hfinkel,jhibbits,jkolek,joerg,majnemer,matze,nathan,rafael,rdivacky,rksimon,rsmith,rtrieu,sanjoy,seurer,spatel,timurrrr,tomatabacu,tstellar > > BUILD FAILED: failed annotate > > sincerely, > -The Buildbot