similar to: sanitizer test case failures after OS update

The test case that you added in this revision fails on several of the power buildbots (for 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: --

> 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

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

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

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

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 same

Hi, I've had 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

It appears that lnt has the capability to run the SPEC2000/2006/2017(maybe) tests from looking at the options and from poking around in the mailing list archives. Or does it? I experimented a bit and 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

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

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

I've investigated several failures that my buildbots detected but when I figured out which revisions caused the failures they weren't on any blame lists. Thus the developer has no clue they broke anything until I contact them. It appears this happens 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

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 this: /usr/bin/svn checkout --non-interactive --no-auth-cache --revision 323463 http://llvm.org/svn/llvm-project/test-suite/trunk at 323463 test/test-suite in dir

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

I looked at this a bit a while back when you first asked but I didn't see anything obviously wrong. Benjamin, at least one of the referenced failures was on BE powerpc64. I don't remember if that one (http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883) failed on stage 1 or 2 and the results pages are no longer available. BTW, I tried testing the same revision many

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 make it > > more likely to actually get to the

Bill, For some reason the llvm-symbolizer tests fail on ppc: http://lab.llvm.org:8011/builders/clang-ppc64le-linux/builds/182/steps/ninja%20check%201/logs/stdio because it can't be started: /home/buildbots/ppc64le-clang-test/clang-ppc64le/stage1/./bin/llvm-symbolizer: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by

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 make it more likely to actually get to the "sanitizer" part of the testing process. Philip -------- Forwarded Message -------- Subject: buildbot failure in LLVM on

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

Hello, Some of our AArch64 bots have started timing out while compiling SingleSource/UnitTests/Vector/AArch64/aarch64_neon_intrinsics. On clang-cmake-aarch64-quick the failure first appears between r275337 and r275351, and on clang-cmake-aarch64-full it appears after r275352, so there's isn't a clear culprit for this. I suspect we have been slowly approaching that threshold for a while.

Hi, My New Year's resolution is to complain (constructively) whenever I get a spurious build failure email from a buildbot. For new or infrequent contributors especially, they can be extremely confusing and unnecessarily alarming. This one below is the first build ever attempted by the builder, so how on earth can it have come up with a meaningful blame list? And in any case, surely we