search for: qmtest

I attempt install and use qmtest for run LLVM testsuit at FreeBSD, but without success. I have installed qm-2.2 (latest and single version accessable from http://www.codesourcery.com/qmtest/download.html in sources) When I start qmtest for LLVM ("make qmtest" in <llvm-obj-dir>/test directory - right?) error print...

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

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 own opinion. (Note: RUN lines are basically sequences of commands that are put into a ba...

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

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

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 pros and cons in my eyes, please feel free to add your own > opinion. > > (Note: RUN lines are basically sequences...

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 test. In fact, I've already tried to run the tests with QMTest, bypassing Makefiles, but I get numerous error in QMTest/llvmdb.py. It appear...

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 this case). But we don't use QMTest anymore, correct? So isn't the python test obsolete?

Vladimir, 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 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 test. On Wed, 2004-06-09 at 05:18, Vladimir Prus wrote: > I've finally managed to bring my backend to a minimally working form. I can > compile...

I've finally managed to bring my backend to a minimally working form. I can compile three small examples with arithmetic operations, branches and phi operations. However, there surely is a lot of omissions and bugs. How do I test a backend. For obvious reasons, I'd prefer a number of really small tests, to make debugging easier. I see some number of such small tests in

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

...re the same. If they are different directories, then this error does not occur. To work around this, simply remove the llvm/test/tmp directory and re-run the tests. I'll file a bug report and work on a fix. Thanks for finding this. yue wrote: > hi, > when I run 'make ./test qmtest' it displays: > ----------------------------------------------- > QMTEST_CLASS_PATH=/home/yue/llvm/test/QMTest qmtest -D > /home/yue/llvm/test run -O /home/yue/llvm/test/QMTest/expectations.qmr > -c "srcroot=/home/yue/llvm" -c "buildroot=/home/yue/llvm" -c &gt...

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/

...aeke 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 LLVM Python code or in the QMTest library code that looks up the name of the configuration variable? -- John T. > > Thanks! > > -Brian > > On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote: &...

...ach 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 stuff that's filling the process table. More to come once I am able to duplicate the problem and inspect the situation... -Brian On Nov 3, 2004, at 5:01 AM, Vladimir Merzliakov wrote: >>> I'm not sure that I follow. The qmtest stuff isn't working on Zion >>> be...

...or 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 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 this case). But we don't use QMTest anymore, correct? So > isn't the python test obsolete? ERM, we removed those tests before the /dev/zero t...

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 similar situation with the PowerPC/Mac OS X > nightly tests. Over each of the past few nights, something has been > filling up the process...

...; I tried running SingleSource also, and ran into a few problems. Some of > the tests failed because they cannot include alloca.h. This may be a > linux dependency. Anyway, again I saw the same results with or without > my change. Which platform are you compiling on? > I cannot run qmtest at all. I don't seem to have it or any way of > building it. qmtest is an external package. You need version 2.03. I suggest you read: http://llvm.cs.uiuc.edu/docs/TestingGuide.html In the requirements section there's a link to the QMTest software. > > There's no rush to...

...ap... 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 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 this case). But we don't use QMTest anymore, correct? So >>isn't the python test obsolete? >> >> > >ERM, we...

...e following: > cd /usr/obj > /usr/src/llvm/configure > make This change allows a single source directory to be shared among several object directories. This will be very useful for those compiling for x86 and Sparc. Also, part of the test suite is now powered using qmtest. You will need to have qmtest and python installed to use the test suite. The new configure script checks for qmtest and python, so you should know if you have everything you need. Visit http://www.qmtest.com for information on qmtest and the version of python required to use it. This new b...