similar to: [LLVMdev] qmtest problem

Boy does THAT look familiar .. The problem is that you need an older version of QMTest, version 2.0.3 to be exact. The configuration of QMTest that LLVM uses won't work with 2.2 Reid. On Sun, 2004-06-20 at 10:53, Vladimir Merzliakov wrote: > I attempt install and use qmtest for run LLVM testsuit at FreeBSD, but > without success. > > I have installed qm-2.2 (latest and single

> 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

Brian Gaeke wrote: > > A typo in test/Makefile was the trigger for this problem: > > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ > 020216.html > > John, can you please look into this bug some more and add some error > checking to the llvm-specific qmtest python modules to make this error > less severe? Does the fork bomb occur in the

A typo in test/Makefile was the trigger for this problem: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ 020216.html John, can you please look into this bug some more and add some error checking to the llvm-specific qmtest python modules to make this error less severe? Thanks! -Brian On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote: > > I think there is a very

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

I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest

> > 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

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

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) > >

>> I'm not sure that I follow. The qmtest stuff isn't working on Zion >> because (I believe) of an upgrade that happened on the machine (the >> qmtest >> binary doesn't work anymore?). Are you seeing a problem on freebsd where >> the feature tests go into a loop? If so, can you provide us with more >> information? >> make, ~ > ps -xu

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

>> > I assume you're talking about the FreeBSD run. I'm not sure what is >> > going >> > on >> >> No. You can see problem with Feature tests at >> http://llvm.cs.uiuc.edu/testresults/X86/ also (see Feature Test Results >> section ) > > I'm not sure that I follow. The qmtest stuff isn't working on Zion > because (I

Actually, I'm talking about the shell that Perl invokes. When you run the NightlyTest.pl script, it uses Perl. The system() function in Perl invokes the "standard" shell to execute the command provided as the argument to system(). In NightlyTest.pl, I have changed the program to check out both the regular llvm CVS module as well as the llvm-test module. This command is what is

> Boy does THAT look familiar .. > > The problem is that you need an older version of QMTest, version 2.0.3 > to be exact. The configuration of QMTest that LLVM uses won't work with > 2.2 Ok, I will attempt with QMTest 2.0.3 I think this requirement can be added to http://llvm.cs.uiuc.edu/docs/TestingGuide.html in "Requirements" section for simplify testsuit use by

Hi Reid, > The makefile for the feature tests is in the directory above. Simply: > > cd ~/llvm/test > make Feature.t > > This works for the regression tests to: > > make Regression.t Thanks, > The tests are run QMTest which just "knows" what to do with the test > file. In many cases there is a RUN: line which instructs the test > harness how to run the

Does anyone have any objections to removing support for QMtest from the LLVM regression testing framework? The LLVM Dejagnu framework has all of the functionality provided by QMtest and more. -Chris -- http://nondot.org/sabre/ http://llvm.org/

I see two minor configure errors on FreeBSD. The first is: checking for mmap of files... yes checking if /dev/zero is needed for mmap... test: FreeBSD: unexpected operator no The second: checking for python... true python test: : bad number configure: WARNING: QMTest requires Python 2.2 or later I guess it shouldn't get the "bad number" error if python is missing (and it is in

Dear yueqiang, I tracked this down this morning, and it is a bug with our Python code that runs the tests. Essentially what is happening is that the code is finding the temporary directory it created the first time it ran the tests and believes that there are tests inside of it which it needs to run. It then gets confused and quits. This bug only shows up when the source tree and the

On Tue, 2004-12-28 at 22:47, Jeff Cohen wrote: > I see two minor configure errors on FreeBSD. The first is: > > checking for mmap of files... yes > checking if /dev/zero is needed for mmap... test: FreeBSD: unexpected > operator > no That was a bug and I just fixed it. Thanks for pointing it out. > The second: > > checking for python... true python > test: : bad

On Sun, 2004-08-29 at 16:01, Jeff Cohen wrote: > Fair enough... The following tests under MultiSource fail: > > Benchmarks/Olden/power > Benchmarks/OptimizerEval > Benchmarks/Ptrdist/ks > Benchmarks/MallocBench/perl > Applications/sgefa > > However, they also fail in the exact same way without my change. > OptimizerEval appears to be non-deterministic; it produces