similar to: [LLVMdev] Nightly Test Page Busted?

I had the same problem, actually. Is the HTML file just too heavy? It makes it hard to compare results from your workstation against the buildbots. Reid On Thu, Jul 23, 2009 at 3:22 PM, David Greene<dag at cray.com> wrote: > If I click on a "View Details" link for a particular nightly test, my browser > sits there waiting until I tell it to stop.  I something wrong with

We are experiencing serious load/memory issues on llvm.org and unfortunately, there is not anything we can do about it. This means that because the nightlytest page needs to access a mysql database, it will be very very slow. Bugzilla will be slow too. We have a machine being ordered, but it will take time to arrive and time to setup. Until then, I'm asking people to please try to be

On Thursday 23 July 2009 17:43, Tanya Lattner wrote: > We are experiencing serious load/memory issues on llvm.org and > unfortunately, there is not anything we can do about it. This means > that because the nightlytest page needs to access a mysql database, it > will be very very slow. Bugzilla will be slow too. Has there been a spike in traffic recently? Or maybe I just got lucky

On Wednesday 15 July 2009 15:43, Török Edwin wrote: > How about starting simple, and just auto-tagging builds that work? > Could be done per OS/arch, and one global tag when all buildbots pass. We've talked about this before and I've been working on setting up such a system. Unfortunately, I can't figure out why my buildbots fail to configure llvm-gcc. Is there a link to the

Nightly tester 'grawp' is reporting compilation error ? How do I see detailed build log ? Thanks, - Devang

On Thu, Jul 16, 2009 at 7:42 AM, David Greene<dag at cray.com> wrote: > On Wednesday 15 July 2009 15:43, Török Edwin wrote: > >> How about starting simple, and just auto-tagging builds that work? >> Could be done per OS/arch, and one global tag when all buildbots pass. > > We've talked about this before and I've been working on setting up > such a system.

Hi Devang, Unfortunately, there's no way to see the build log unless you're on the machine from which the report was generated. If you can log in to Grawp's machine then it should be in the "WEBDIR". It is most likely mis-compiling because the needed llvm-gcc patch has not been applied after the SETCC patch to LLVM was committed last weekend. Reid. On Fri, 2006-12-29 at

Today I'm seeing a lot of the nightly tests hit their execution time limit. Is this normal? I ran it this morning and it seemed to finish in a reasonable amount of time. I updated and now it's taking forever. Anyone else seeing this? -Dave

On 2009-07-15 23:24, Dale Johannesen wrote: > On Jul 15, 2009, at 11:52 AMPDT, Stuart Hastings wrote: > > >> We've had a lot of churn in all the trunks (llvm, llvm-gcc, clang) >> recently, and the testing buildbots have been failing repeatedly. >> >> I spoke with Chris this AM, and he suggested we have a "stabilization >> day." Please avoid

You all just need remove "stacker_rt.ll". the stacker_rt.ll is a generated file, not source. The Makefile should have a dependency on llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem will go away. Reid. On Sat, 2006-12-30 at 08:37 -0500, Nick Lewycky wrote: > Jim Laskey wrote: > > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build

On Wed, 2006-10-18 at 12:43 -0700, Chris Lattner wrote: > On Wed, 18 Oct 2006, Reid Spencer wrote: > > I had upgraded my Linux kernel from 2.6.17 to 2.6.18. I suggested to Jim > > that changes in the minor revision number of the operating system should > > not count as a new machine. He said he'd look into it when he has time. > > Its not a huge issue, I just

Reid, Click on any of these logs and you'll see the same asm parsing issues. It's been going on for much of the week. http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build (bytecode)

On Wed, 18 Oct 2006, Reid Spencer wrote: > I had upgraded my Linux kernel from 2.6.17 to 2.6.18. I suggested to Jim > that changes in the minor revision number of the operating system should > not count as a new machine. He said he'd look into it when he has time. > Its not a huge issue, I just didn't want to be incrementing the machine > numbers needlessly and needed to

Jim Laskey wrote: > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build > (bytecode) > /Volumes/Muggles/LLVM/nightlytest/build/llvm/Release/bin/gccas: / > Volumes/Muggles/LLVM/nightlytest/build/llvm/projects/Stacker/lib/ > runtime/Release/stacker_rt.ll:21,0: parse error, expecting `LOAD' or > `STORE' >

Hi Chris, On Wed, 2006-10-18 at 11:59 -0700, Chris Lattner wrote: > On Wed, 18 Oct 2006, Reid Spencer wrote: > > How are the nightly test machines identified? I went to look at my > > machine's test results and couldn't find any (for a while) because a new > > machine id had been set. I'd like to avoid creating new machine ids so > > could you please

I've noticed that my nightly tester doesn't seem to be reporting the results of running llvm-test, only build warnings and make check. Checking with -verbose shows that it's running the test suite, so I don't quite understand what's going on. Looking at http://llvm.org/nightlytest/ shows that none of the other Linux testers are reporting test suite results either.

On Thursday 16 July 2009 14:04, Daniel Dunbar wrote: > 2009/7/15 Török Edwin <edwintorok at gmail.com>: > > I'm not too keen about seeing buildbots play with trunk ;) > > > > How about starting simple, and just auto-tagging builds that work? > > Could be done per OS/arch, and one global tag when all buildbots pass. > > I don't know anything about svn

2009/7/16 Daniel Dunbar <daniel at zuster.org> > I plan to check my buildbot configuration "stuff" into the > llvm-project repository soon. I have to refactor things a bit to > support use by other people, but currently I have configurations for > llvm, clang, and llvm-gcc in various target / self-hosting > permutations. I also have a regular buildbot driver

It seems after the change on Zion that the nightly test is broken. When I go to http://llvm.org/nightlytest/, I get a blank page. Any ideas? Reid.

On Sat, 5 May 2007, David Greene wrote: > There's the llvm-testresults list, but I find it less than fully useful > because it's not immediately obvious from scanning message subjects if > there's been a test failure. It's a lot of messages to wade through and > read to get this information. Right. > What about a Tinderbox-like setup where we could consult a web