Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] Nightly Testers"
2006 Jul 07
0
[LLVMdev] New Nightly Tester
Hey All,
I have been making some changes to the nightly tester that will
hopefully make debugging problems and performance issues easier. The
big change is nightly test results will now be kept in a central
location (http://llvm.org/nightlytest/index.php). I have committed a
new file to utils/ called 'NewNightlyTest.pl'. It *should* behave
almost exactly like the previous NightlyTest.pl
2008 Jul 21
0
[LLVMdev] nightly tester setup
Hard to tell what's wrong. Perhaps /usr/local/bin is not part of path
for a cron job?
You should add NewNightlyTest.pl -noremove -release options. That
leaves the build directory around for you examine it afterwards. Just
manually delete the build directory before running NewNightlyTest.pl.
Evan
On Jul 20, 2008, at 6:00 PM, Nick Lewycky wrote:
> I've noticed that my nightly
2008 Jul 21
4
[LLVMdev] nightly tester setup
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.
2009 Feb 26
1
[LLVMdev] [PATCH] Parallelized make check
On Wed, Feb 25, 2009 at 12:02:18PM -0800, Julien Lerouge wrote:
> For 2), I think the NewNightlyTest.pl script would require some small
> changes, to invoke the jcheck target instead of check, pass the desired
> -j flag, and also parse the log. I'll take a look. In any case, the
> changes would only apply to the DejaGNU tests (llvm-test already works
> fine with -jX).
Here is
2008 Jul 25
0
[LLVMdev] nightly tester setup
Daniel Dunbar wrote:
> Did you manage to solve your issue yet, I just had the same problem
> and found out that the problem was that I had redefined LLVMGCC
> which was (eventually) causing LCC1 to get defined to garbage in Makefile.rules.
> Since the .bc target depends on the source and LCC1 this was basically
> breaking all the rules.
I haven't fixed it yet, but I haven't
2006 Dec 30
2
[LLVMdev] nightly tester grawp
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)
2008 Apr 05
4
[LLVMdev] Proposal for improving the llvm nightly tester
hi all,
After having some discussions in the IRC, I am trying here to come up with a
proposal for GSoC 2008 for improving the llvm nightly tester[1].Following
are the ideas and suggestions that came up in the discussion, if you have
any comment or any other suggestion please add them to the list. I have
some doubts in some places.
1. Improvements to the perl script which manage actual testing
2008 Apr 05
0
[LLVMdev] Proposal for improving the llvm nightly tester
My main complaints about the nightly tester are:
Loading the web pages is waaay tooo sllooooow
The information provided is not terribly useful for tracking down
bugs. What bug fixers need is environment+command line options
adequate to reproduce the problem. Access to the run logs would be a
good start.
On Apr 4, 2008, at 9:22 PM, Rajika Kumarasiri wrote:
> hi all,
> After having
2006 Dec 30
3
[LLVMdev] nightly tester grawp
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
2008 Jun 05
0
[LLVMdev] Linux x86 testers needed!
Hello list!
Tanya Lattner wrote:
> We are in desperate need of linux x86 testers (32 or 64 bit). If you
> could set one up, the LLVM project would be very grateful. Right now
> we have virtually no testers covering this platform.
I've run the test last night to see how long it takes, and I can
afford to cronjob it for the night.
I didn't quite realize it would automatically
2008 Jun 05
2
[LLVMdev] Linux x86 testers needed!
> I've run the test last night to see how long it takes, and I can
> afford to cronjob it for the night.
Great!
> I didn't quite realize it would automatically send the report, but
> it did [1] and there are a few test failure from the
> Frontend{C,C++} directories. I suppose this is because I have
> llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is
>
2006 Dec 30
0
[LLVMdev] nightly tester grawp
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'
>
2008 Apr 07
0
[LLVMdev] Proposal for improving the llvm nightly tester
> 1. Improvements to the perl script which manage actual testing
> (./util/NewNightlyTest.pl)
> (a). compiling llvm-gcc
> (b). allowing someone to use an existing tree versus checking out a
> new one
> 2. The improvements to the email that get sent to the llvm-testresults
> (a). finding a point in time where some test failed
> (b). comparing two
2009 Mar 10
1
[LLVMdev] inconsistent use of LLVMGCCDIR?
The utils/NewNightlyTest.pl script seems to use LLVMGCCDIR in a way
that is inconsistent with the top-level configure script. I would
like to fix this but I don't want to break everyone's nightly tests.
Can someone review the attached patch to make sure I'm not missing
something?
The NewNightlyTest.pl script checks the LLVMGCCDIR environment
variable and uses it for two
2008 Jan 31
2
[LLVMdev] [llvm-testresults] OldGrawp-O0-PIC i386 nightly tester results
On Jan 30, 2008, at 9:12 PM, Apache wrote:
> http://llvm.org/nightlytest/test.php?machine=231&night=4754
> Name: il0102a-dhcp80.apple.com
> Nickname: OldGrawp-O0-PIC
> Buildstatus: OK
>
> New Test Passes:
> test/CFrontend/2008-01-28-PragmaMark.c [DEJAGNU]
>
>
> New Test Failures:
> Benchmarks/Shootout-C++/except [LLC compile, ]
>
2008 Jan 31
0
[LLVMdev] [llvm-testresults] OldGrawp-O0-PIC i386 nightly tester results
It's me. Our ISD::LABEL implementation has issues...
Evan
On Jan 30, 2008, at 9:34 PM, Dale Johannesen wrote:
>
> On Jan 30, 2008, at 9:12 PM, Apache wrote:
>
>> http://llvm.org/nightlytest/test.php?machine=231&night=4754
>> Name: il0102a-dhcp80.apple.com
>> Nickname: OldGrawp-O0-PIC
>> Buildstatus: OK
>>
>> New Test Passes:
>>
2006 Oct 18
1
[LLVMdev] Nightly Test Machine Identification
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
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
llvm itself is built with gcc-4.0, but the run line is:
// RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 |
grep {i32 1} | count 2
According the log:
FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+
+Frontend/2008-02-13-sret.cpp
Failed with exit(1) at line 1
while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /
2008 May 30
0
[LLVMdev] [llvm-testresults] grue-x86-64-pic i386 nightly tester results
On May 30, 2008, at 4:34 AM, Apache wrote:
> http://llvm.org/nightlytest/test.php?machine=277&night=6245
> Name: grue.apple.com
> Nickname: grue-x86-64-pic
> Buildstatus: Error: compilation aborted
>
> Buildlog available at http://llvm.org/nightlytest/machines/2008-05-30_06:33:56-Build-Log.txt
That last pathname is not correct, it should be
2009 Feb 25
0
[LLVMdev] [PATCH] Parallelized make check
On Wed, Feb 25, 2009 at 10:26:02AM -0800, Chris Lattner wrote:
>
> On Feb 24, 2009, at 10:03 PM, Julien Lerouge wrote:
>
> > On Tue, Feb 24, 2009 at 06:24:17PM -0800, Julien Lerouge wrote:
> >> I haven't tested with objdir != srcdir.
> >
> > Ok, that was broken. Attached is a smaller diff that should work in
> > all
> > cases.
>
> This