similar to: [LLVMdev] new llvm-testresults mailing list

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] new llvm-testresults mailing list"

2005 Mar 10
0
[LLVMdev] new llvm-testresults mailing list
> Do to popular request, I just set up a new mailing list to capture the > nightly tester output from the various testers running 'round the world. > The new list is available here: > http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults > > If you're running a nightly tester, please update your crontab to send > mail to the llvm-testresults at cs.uiuc.edu list
2004 Jun 25
2
[LLVMdev] Using -noexternals option of NightlyTest.pl
Result night tester run at FreeBSD 5.1 accessable by URL http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html I can't guaranty run it per day base, sorry. As i can see, make (bug 385) and perl (bug 386) not builded by NightlyTest.pl (but builded if use gmake night tests run format) So I don't known preferable solutions: its can be closed or patches applied. Vladimir
2004 Jun 25
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Fri, 25 Jun 2004, Vladimir Merzliakov wrote: > Result night tester run at FreeBSD 5.1 accessable by URL > http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html > I can't guaranty run it per day base, sorry. Okay, sounds great. I added it to the page with a note to that effect: http://llvm.cs.uiuc.edu/testresults/ Thanks a lot for volenteering to run it. Also, if you notice
2005 Mar 10
3
[LLVMdev] new llvm-testresults mailing list
On Thu, 10 Mar 2005, Vladimir Merzliakov wrote: >> Do to popular request, I just set up a new mailing list to capture the >> nightly tester output from the various testers running 'round the world. >> The new list is available here: >> http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults >> >> If you're running a nightly tester, please update
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: >>
2004 Jun 24
5
[LLVMdev] Using -noexternals option of NightlyTest.pl
> Are you using the NightlyTest.pl file? To run the tester I don't use > gmake directly at all. Instead, I have this in my crontab: > > 5 3 * * * LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan /home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86 > > When run like this,
2004 Dec 23
1
[LLVMdev] Re: [llvm-commits] CVS: llvm-www/testresults/index.html
> Changes in directory llvm-www/testresults: > > index.html updated: 1.22 -> 1.23 > --- [skiped] > <li><a href="http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html">X86: > FreeBSD 5.3-RC1</a> -- debug build</li> > Can be description updated to "X86: FreeBSD 5.3 (Pentium 3 @ 1.0Ghz) ? Please! :) Vladimir
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > At this moment I use > "gmake TEST=nightly" command line to run night tester > > What I must specific and where to disable SPEC run (i don't have it) I think that it's currently a bug that this does not automatically happen. > I known about new NightlyTest.pl option: -noexternals > But what I must do for
2004 Jun 26
1
[LLVMdev] Non-portable use time command in RunSafely.sh
If you look at http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html then you see that all program test have '*' in run time columns. I think problem in using plain 'time' command in RunSafely.sh At FreeBSD 'time <program> <args>' call generate output in format " 0,00 real 0,00 user 0,00 sys" for *.time files instead expected
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, ] >
2004 Jun 24
1
[LLVMdev] Using -noexternals option of NightlyTest.pl
> On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > > At this moment I use > > "gmake TEST=nightly" command line to run night tester > > > > What I must specific and where to disable SPEC run (i don't have it) > > I think that it's currently a bug that this does not automatically happen. > > > I known about new NightlyTest.pl option:
2004 Jul 05
3
[LLVMdev] Propose change gnuplot options for small picture versions
In current state dates at small version of pictures generated by night builder script is unreadable ( for example http://llvm.cs.uiuc.edu/testresults/X86/running_loc.png ). I suggest rotate it to vertical position in small picture versions. .png file created modified gnuplot script (for comparing) and patch attached. "set xlabel 0,-1 " added for solving xlabel and xtics text overlap
2004 Jun 24
3
[LLVMdev] Using -noexternals option of NightlyTest.pl
At this moment I use "gmake TEST=nightly" command line to run night tester What I must specific and where to disable SPEC run (i don't have it) I known about new NightlyTest.pl option: -noexternals But what I must do for enable it Vladimir
2004 Jun 24
3
[LLVMdev] Using -noexternals option of NightlyTest.pl
> Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm dir? After providing :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm at CVSROOT this problem disappear. But have personal problem: I must have now 2 copy LLVM sources 1) to plain build llvm 2) to nighttester run Can I use llvm builded in nighttest/build directory to install plain llvm? Vladimir
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >
2004 Aug 30
0
[LLVMdev] lib/System Unleashed - Need Your Help!
After update LLVM compile break with errors at FreeBSD 5.1 You can see log at night tester http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html If you need additional information i will be glad provide it. Vladimir
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> That's weird. What is your default shell that Perl invokes with the > "system" command. This works fine with bash-2.05b. In reality :) i use this script in crontab (and run it manually with added verbose flag): ---8X-------------- #!/bin/sh - # if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ]) then mkdir
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> x86 FreeBSD: > * hasn't run with changes yet I manually start script. I use this options (+ -verbose now for testing) /home/wanderer/pkg/build/llvm/src/llvm/utils/NightlyTest.pl -parallel -enable-linscan -noexternals -noremove :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm /home/wanderer/pkg/build/llvm/night/build
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 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote: > But I am using llvm-gcc-4.2. Any idea why it's failing? > > Evan All the failing testers are using gcc-4.0 according to the web pages they point at. > On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > >> On Feb 16, 2008, at 7:06 AM, Apache wrote: >>> New Test Failures: >>>