similar to: [LLVMdev] Dejagnu Support Added

> I've tested this with srcdir=objdir and srcdir!=objdir, and on both linux > and on sparc. I'd appreciate the help testing this on additional platforms > such as Darwin and FreeBSD. Please let me know if you have any problems or > questions. I check in src==obj case at FreeBSD, files attached. -------------- next part -------------- A non-text attachment was scrubbed...

Tanya Lattner wrote: > I've finished adding the -rundejagnu option to the nightly tester script, > which was the last step to fully support Dejagnu. I think now is the > appropriate time to discuss keeping QMTest or switching to Dejagnu. A lot > of work went into using QMTest, so I think we should make this decision > carefully and before the 1.4 release. > > Here are the

I've finished adding the -rundejagnu option to the nightly tester script, which was the last step to fully support Dejagnu. I think now is the appropriate time to discuss keeping QMTest or switching to Dejagnu. A lot of work went into using QMTest, so I think we should make this decision carefully and before the 1.4 release. Here are the pros and cons in my eyes, please feel free to add your

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

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 sounds really cool Julien! Two questions: 1) does it preserve the checking that the existing tcl stuff does, which

On Sunday 28 November 2004 00:24, Tanya Lattner wrote: Just some comments from a QMTest user... Note however, that even with them, dejagnu looks better. > Cons of QMTest: > 1) You have to use the gui to add directories. I think you're wrong. Manually creating a directory would work, as QMTest does not place anything special in directories. > 2) You have to use the gui to XFAIL

> > Cons of QMTest: > > 1) You have to use the gui to add directories. > > I think you're wrong. Manually creating a directory would work, as QMTest does > not place anything special in directories. I may have worded this poorly, but I think you have to use the gui to add new directories or tests, or specific tests. Otherwise, it does not know what to do with those

I've uploaded the 2.0 pre-release to this location: http://llvm.org/prereleases/2.0/ If you have free time and would like to help test this release, please download the appropriate tarballs from the website. Here are a few ways you can help test this release: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run

Tanya, I have done make check and nightly report tests on LLVM on the GCC 4.2.0 release, on Linux x86 32 bit. On make check the bit intrinsics test is still failing but it works from the command line, strange ? What files do you want from the nightly report, as I am not familiar with it ? I will be doing Cygwin tests next. Aaron ----- Original Message ----- From: "Tanya M.

I've updated the pre-release tarballs online. I'm also extending the testing completion date to May 22nd at 5pm PDT. The new release target date is May 23rd. If you have any free time, please give the new pre-release a try. Thanks to all who have tested LLVM! -Tanya P.S. Documentation review should still be completed today! Thanks! > I've uploaded the 2.0 pre-release to this

Thanks for testing the release. Overall the test results look decent with a couple exceptions. You also have a few CBE failures that I am not seeing. What version of xcode do you have installed? Can you send me the following files? SingleSource/Regression/C/Output/2008-01-07-LongDouble.* SingleSource/Regression/C/Output/PR1386.* Thanks, Tanya On Jan 26, 2008, at 6:43 AM, Takanori Ishikawa

> On make check the bit intrinsics test is still failing but it works from the > command line, strange ? Did Chris help you with this or is it still an issue? > What files do you want from the nightly report, as I am not familiar with it > ? in llvm-test, if you run the gmake TEST=nightly report command it will generated a report.nightly.txt file. Thats what I want to see. Thanks!

> I'm asking for people (especially those running nightly testers) to give > Dejagnu a try. I will do. But last 2 days (after http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/020279.html ) LLVM broken at FreeBSD: In file included from Path.cpp:27: platform/Path.cpp:26: error: no `bool llvm::sys::Path::isvalid() const' member function declared in class

My test results for the LLVM 2.2 prerelease. === Q. Target === * Mac OS X 10.4.11 * 2 GHz Intel Core 2 Duo * MacBook % uname -a Darwin macbook.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 === Q. How you built the release === * objDir != srcDir * Release build * llvm-gcc-4.2 from source

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

Aaron, On Thu, 2007-05-17 at 22:54 +0100, Aaron Gray wrote: > Tanya, > > I have done make check and nightly report tests on LLVM on the GCC 4.2.0 > release, on Linux x86 32 bit. > > On make check the bit intrinsics test is still failing but it works from the > command line, strange ? Can you be a bit more specific about which test is failing? Reid. > > What

Hello, The attached patch adds the jcheck target equivalent to make check, but that can run with a -j flag ($ make jcheck -jX). It does not interfere with the regular check, but rather builds on top of the check-one target: it first generates a list of tests to run using RunLLVMTests, and then run those tests according to the supplied -j flag, invoking the check-one target for each one of them.

I'm having troubles running the test suite on OS X 10.4. Inside my objdir, 'make check' gives this: % make check llvm[0]: Running test suite

Dear Tanya: > You also have a few CBE failures that I am not seeing. What version > of xcode do you have installed? Xcode 2.4.1 > Can you send me the following files? > SingleSource/Regression/C/Output/2008-01-07-LongDouble.* > SingleSource/Regression/C/Output/PR1386.* OK, I attached those files (llvm-2.2-test-output.tar.gz) Best regards, 2008/1/30, Tanya Lattner <tonic at

Hi, Here are my results. Environment: - frontend was built from source, - platform: Linux/x86 (gcc 4.1.2) - Release build - srcdir != objdir Dejagnu summary: # of expected passes 1939 # of expected failures 5 Nightly test report attached. Wojtek -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: report.nightly.txt URL: