similar to: santizer problems with dynamic thread local storage

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no

Hello and thanks in advance to those who post back, I''m working on a calender but, it renders the data in the controller then saves it as @code so I call it in the veiw <%= @code %>. So everythings working and I add this line.. @event = Event.find_by_date("#{@temp13.year}-#{@temp13.month}-#{@temp13.day}") if @event == nil @@td = "<td width=50 height=50

clang+llvm-3.8.0-rc3-x86_64-linux-gnu-debian8.tar.xz (sha1sum: 2dedc6136d7cfbac8348652c543887964d92393c) Native: All ok Cross compiling to MIPS: All ok clang+llvm-3.8.0-rc3-mips-linux-gnu.tar.xz (sha1sum: f286149dbb2ea7e194c5c3719b6cded476f6e65f) All ok (aside from non-regression failures in check-all). There were two kinds of check-all failure: * mips64 sanitizers. Not a regression since

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 Mon, Feb 29, 2016 at 2:20 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > clang+llvm-3.8.0-rc3-x86_64-linux-gnu-debian8.tar.xz (sha1sum: 2dedc6136d7cfbac8348652c543887964d92393c) > Native: All ok > Cross compiling to MIPS: All ok > > clang+llvm-3.8.0-rc3-mips-linux-gnu.tar.xz (sha1sum: f286149dbb2ea7e194c5c3719b6cded476f6e65f) > All ok

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 errors now so it isn't any changes in llvm. There are two different errors: FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 47 -

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

Hi Galina, The failing build was http://lab.llvm.org: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]

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

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

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

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

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

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

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

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

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

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

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

I may have found a similar issue with plain old RSAAuthentication. After upgrading to 3.4p1 on Solaris 8, I am no longer able to use RSAAuthentication with PermitRootLogin forced-commands-only Following is output from sshd -d -d: Connection from 10.100.100.8 port 39955 debug1: Client protocol version 2.0; client software version OpenSSH_3.4p1 debug1: match: OpenSSH_3.4p1 pat OpenSSH* Enabling