search for: testsuites

Having built rsync 2.5.5 on IRIX 6.2 with gcc 3.1, I ran into two failures when running the testsuite with make check: both the chgrp and hardlinks tests fail: The failure in the chgrp test occurs here: + rsync -rtgvvv /amnt/callisto/volumes/obj-irix5/local/obj.irix5/rsync-2.5.5/testtmp.chgrp/from/ /amnt/callisto/volumes/obj-irix5/local/obj.irix5/rsync-2.5.5/testtmp.chgrp/to/ rsync: opendir

...formance when compiled by different compilers (gcc, icc, llvm-gcc), so I hope LLVM's optimizers can (in the future) make it faster ;) I had a quick look at the build infrastructure, and there are some issues with getting it to work with programs that use autoconf (such as ClamAV), since AFAICT testsuites aren't allowed to run configure (listed below) Building issues aside there are some more questions: * ClamAV is GPL (but it includes BSD, LGPL parts), ok for testsuite? * what version to use? Latest stable, or latest svn? [In any case I'll wait till the next stable is published, it should...

Yo, Currently if you build rsync and you don't have rsync installed, make test will fail because some tests reference the rsync binary directly (instead of using the $RSYNC variable). I cannot find anything which refers to this problem in the mail archives or CVS logs. Below is a patch which fixes this problem. (please CC: me, I'm not subscribed. Thanks.) -- Geoff. --------------

Hello, Noticed a couple of problems with the rsync testsuite. I have included a possible patch for each problem (attached & inlined.) The first problem is that on OpenBSD when make test is run and tests are skipped you see messages like this: cat: "/tmp/rsync-2/rsync/testtmp.chown/whyskipped": No such file or directory SKIP chown () After my patch, you get the appropriate

...mpilers (gcc, icc, llvm-gcc), so I hope LLVM's optimizers can (in > the > future) make it faster ;) > > I had a quick look at the build infrastructure, and there are some > issues with getting it to work with programs that use autoconf (such > as > ClamAV), since AFAICT testsuites aren't allowed to run configure > (listed > below) > > Building issues aside there are some more questions: > * ClamAV is GPL (but it includes BSD, LGPL parts), ok for testsuite? > * what version to use? Latest stable, or latest svn? > [In any case I'll wait till the...

Hi, sounds like a nice project. Some comments below. > *1. Project title:* > Extend the llvm-test testsuite to include new programs and benchmaraks[1], benchmaraks -> benchmarks > and give a web service interface to run a test build remotely. Also, this is not a title, it is a summary. How about calling it: "Improve the llvm testsuite" > *2. Abstract:* > LLVM[2]

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

...check correctness of a llvm > module which I wrote. How to run SPEC2000 benchmark in LLVM? > > Unnikrishnan C do you know how to run LLVM's nightly testsuite? It has support for SPEC. When you configure LLVM you need to use --with-externals to specify a directory that holds external testsuites like SPEC. For example: --with-externals=$HOME/externals/ In $HOME/externals/ you should put the SPEC testsuite directories, eg speccpu2000. Note that this will only work if you got the nightly testsuite working first, since it is the nightly testsuite that picks up SPEC. You will see in the ni...

Hello, I want to run SPEC2000 benchmark in LLVM to check correctness of a llvm module which I wrote. How to run SPEC2000 benchmark in LLVM? Unnikrishnan C -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Hello every body, With the ideas and suggestions that I got from you all I came up with the proposal for the project of improving the llvm-test testsuite. I am posting my proposal here, if you have any feedback(anything to be added or anything to be removed ) please let me know, so that I can improve the proposal before I upload it in Google web app. Thanks in advance.! Regarda, Rjika *Proposal

...ware is not available. The gcc project has a > compile > farm which might be usable for this, but we would need to ask them > if it > is ok. > (2) Likewise for the gcc testsuite, with results emailed to the > nightly > test mailing list. I would like the Fortran and Ada testsuites to > be run > as well as the C/C++/ObjC tests. > > Just some thoughts! I agree this would be useful. However these two items require access to lots of machine cycles. Do you anticipate lots of work, enough to justify for a GSoC proposal, in existing test setup to accommodate th...

...tor to emulate targets for which the hardware is not available. The gcc project has a compile farm which might be usable for this, but we would need to ask them if it is ok. (2) Likewise for the gcc testsuite, with results emailed to the nightly test mailing list. I would like the Fortran and Ada testsuites to be run as well as the C/C++/ObjC tests. Just some thoughts! Ciao, Duncan.

I've run the tests from clang-tests/trunk/gcc-4_2-testsuite on a Ubuntu x86-64 Linux box with the following results: === gcc Summary === # of expected passes 29946 # of unexpected failures 9938 # of unexpected successes 29 # of expected failures 28 # of unresolved testcases 1451 # of untested testcases 273 # of unsupported tests 811 pid is 4456

On Wednesday 12 November 2008 00:33, Bill Wendling wrote: > > Please take a look and send feedback toi the list. I'd like to get > > the > > process moving early in the 2.4 cycle. > > Hi Dave, > > Here are my opinions: > > I like the idea of regular validation tagging. However, I think that > it should be as automated as possible. I'm worried that

I want to report a problem with an inline assembly instruction from a code generator pass? How can I do that with the proper diagnostic format and source location? Right now we only get: clang -c /d/g/clang-tests/gcc-4_2-testsuite/src/gcc.target/i386/pr30848.c fatal error: error in backend: Inline asm output regs must be last on the x87 stack But gcc-4-2 can: $ gcc-4.2 -c

This bot seems kind of flaky. In the last 100 builds, it has failed "gdb-75-check" 22 times with what is either a linker error or a missing header (or both?): gdb compile failed, /usr/bin/ld: error: /home/buildslave/osuosl_slave/clang-x86_64-ubuntu-gdb-75/clang-tests/build/gdb/testsuite/gdb.trace/pendshr1.c.o: requires dynamic R_X86_64_PC32 reloc against 'pendfunc1' which

I want to report a problem with an inline assembly instruction from a code generator pass? How can I do that with the proper diagnostic format and source location? Right now we only get: clang -c /d/g/clang-tests/gcc-4_2-testsuite/src/gcc.target/i386/pr30848.c fatal error: error in backend: Inline asm output regs must be last on the x87 stack But gcc-4-2 can: $ gcc-4.2 -c

...And with Markdown.pl 1.0.2b8: Total Avg. Min. Q1. Med. Q3. Max. Parse Time (ms): 11143 242 177 182 196 225 1696 Diff. Min. (ms): 2986 64 0 5 18 48 1519 This benchmark includes time for processing three testsuites: one is John Gruber's Markdown testsuite, the one comming with Markdown Test, the two others are PHP Markdown's and PHP Markdown Extra's own testsuites. MDTest works with multiple testsuites (which are simply test folders) and by default use all the folders it can find in its d...

There appears to be a bug in RUnit. Given a testsuite testsuite.math, say, when I run: runTestSuite(testsuite.math) this works fine, provided there are no extraneous files in the unit test subdirectory. But if there are any Emacs temp files (with names that end with '~') then runTestSuite gets confused and tries to run functions from the temp files as well. [[alternative HTML version

Wayne, i like the diff -u idea. I find -c awkward. It seems to me that the shell script could test for support of -u and if present use it instead of -c. ala if [ -n "`diff -u /dev/null /dev/null 2>&1`" ] then difftype="-c" else difftype="-u" fi diff $difftype "$2"/"$f" "$3"/"$f" || failed=YES or something