similar to: [LLVMdev] Non-portable use time command in RunSafely.sh

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

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

Hello everyone, I am working to run the LLVM Nightly Testsuite on embedded arm devices. Not all of these devices can mount NFS to share a common directory tree. To mitigate this I have patched test-suite/RunSafely.sh (attached) to create a temporary directory, run the test remotely, collect the output, and cleanup after itself. The patch breaks compatibility with the current remote device model

> 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

Daniel Dunbar wrote: > I am going to change the LLVM test-suite RunSafely.sh to only track > 'user' time, instead of reporting 'user' + 'sys' time as it currently > does. This will probably cause a spike in nightly test numbers, > although hopefully it will be limited to the smaller tests. > > The eventual goal is to report all numbers (independently), so

I am going to change the LLVM test-suite RunSafely.sh to only track 'user' time, instead of reporting 'user' + 'sys' time as it currently does. This will probably cause a spike in nightly test numbers, although hopefully it will be limited to the smaller tests. The eventual goal is to report all numbers (independently), so that we can control for noise better. However,

On Apr 18, 2010, at 11:08 PM, John Criswell wrote: > Second, why are you only interested in user time? The reason why we had > RunSafely.sh measure user + system time is that it gives a more accurate > depiction of how well an optimization works. If a program spends most > of its time in the OS, increasing speed in user-space doesn't gain us > much. If a transform

> Also i found that generated > http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html page have > links: "Test Results" and "LLVM Page"-> http://npt.cc.rsu.ru/ > > I think this links must be hardcoded URLs in NightlyTester and point to > appropriate LLVM prject web site pages. I propose this attached patch. -------------- next part -------------- A

Dear All, Is the lack of virtual memory limits for Darwin in RunSafely.sh intentional or accidential? What about Cygwin? It seems to me that some of the limits should be applied for all operating system targets. -- John T.

Hi All, 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 (potentially in addition

> 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

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

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

> 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

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > 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 >

Just for information. After root update OS from FreeBSD 5.1 to FreeBSD 5.3-RC1 at make.cc.rsu.ru I don't rebuild LLVM C Frontend. Last LLVM build fail (2004-10-30) is result this situation. I update LLVM C Frontend and rerun manually nighttest script. All ok now :) Also, I think, "X86: FreeBSD 5.1 (may not be run every day)" line at

Eric Christopher <echristo at apple.com> writes: > On Nov 8, 2011, at 7:20 PM, David A. Greene wrote: > > I couldn't figure out how to run the test-suite. Are there up-to-date > instructions somewhere? llvm-gcc doesn't exist anymore... > > Easiest is to check out the test-suite branch into projects and then after you configure and build from the top

On Sat, 11 Sep 2004 13:53:11 -0700 Reid Spencer <reid at x10sys.com> wrote: > On Sat, 2004-09-11 at 12:49, Jeff Cohen wrote: > > > > ===================== MultiSource/Applications/sgefa > > > sgefa is a known XFAIL. See the nightly test results over the last > several months. Actually, you should compare your test results with the > 1.3 release test results

Folks, With some MacOS help from Nate, I've begun the conversion of LLVM to use lib/System, the operating system independence layer. Currently, the library has implementations for three abstractions: Path, Program, and Signals. These provide some basic utilities for manipulating file system paths, finding and executing programs, and cleaning up after Signals. The implementations should work

On Thu, May 17, 2007 at 03:15:09PM -0700, Tanya M. Lattner wrote: > > Should configure also error out if perl isn't installed? > > Yes. Reid has changed this so that perl is now required. > > Thanks so much for reporting these! You're welcome! I'm still working on the "method four" testing that you requested. The "make check" is done, results