llvm dev - Mar 2005 - [LLVMdev] new llvm-testresults mailing list

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 to 
yourself) so the summaries from the tester will get archived.  Internally 
our crontab line looks like this (e.g., for the ppc tester):

5 2 * * * $HOME/bin/ppc-nightly-test

And the script looks like this:

------ 8< ------- 8< -------

#!/bin/zsh
export CVSROOT=/home/vadve/shared/PublicCVS
export BUILDDIR=$HOME/buildtest
export WEBDIR=$HOME/Sites/nightlytest
export LLVMGCCDIR=$HOME/cfrontend/install
export
PATH=$HOME/cfrontend/install/bin:$HOME/qmtest/bin:/usr/local/bin:/sw/bin:$PATH
export LD_LIBRARY_PATH=/proj/install/lib
export LLVM_LIB_SEARCH_PATH=$HOME/cfrontend/install/bytecode-libs

logfile=/tmp/nightly_test_log_$$
rm -f $logfile
exec >$logfile 2>&1
$HOME/llvm/utils/NightlyTest.pl -enable-llcbeta
/usr/bin/mail -s 'PowerPC nightly test' llvm-testresults at cs.uiuc.edu
<
$logfile
rm -f $logfile
exit 0

------ 8< ------- 8< -------

That is one way to run the tester, but there are probably others.

Thanks!

-Chris

-- 
http://nondot.org/sabre/
http://llvm.cs.uiuc.edu/

> 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
to
> yourself) so the summaries from the tester will get archived.  Internally 
> our crontab line looks like this (e.g., for the ppc tester):
>
I update script for http://npt.cc.rsu.ru/testresults-X86-FreeBSD/ 
nigthtester.

I think can be vary helpful if LLVM and (more important) LLVM CFE have
daily versions like GCC and print its in logs and night test result pages.
LLVM CFE not rebuild at each night test run and some tests can fail and not 
fail
in dependency from current LLVM CFE.

Also I found some inconsistent at http://llvm.cs.uiuc.edu/testresults/ page:
all hardware platform names is bold except Alpha.

Vladimir

On Thu, 2005-03-10 at 04:13, Vladimir Merzliakov wrote:
> Also I found some inconsistent at http://llvm.cs.uiuc.edu/testresults/
page:
> all hardware platform names is bold except Alpha.
Really?  Are you sure? ;)

Andrew

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 your crontab to
send mail
>> to the llvm-testresults at cs.uiuc.edu list (potentially in addition to
>> yourself) so the summaries from the tester will get archived. 
Internally
>> our crontab line looks like this (e.g., for the ppc tester):
>> 
> I update script for http://npt.cc.rsu.ru/testresults-X86-FreeBSD/ 
> nigthtester.
Thanks!
> I think can be vary helpful if LLVM and (more important) LLVM CFE have 
> daily versions like GCC and print its in logs and night test result 
> pages. LLVM CFE not rebuild at each night test run and some tests can 
> fail and not fail in dependency from current LLVM CFE.
I think the best way to deal with this in the short term is to output the 
date stamp of the "cc1" program in llvm-gcc.  If we output the date in
the
Dejagnu test results section, it would be easy to see that for a CFE of 
date N, all C{++}Frontend tests dated > N can be expected to fail.

Eventually, the CFE will be split off to run as a proper project, and the 
tests will be distributed with it.  I don't think anyone is planning on 
working on this though.

BTW, I added a line to the shell script we use to update the 
NightlyTest.pl file from CVS before running it.  This might be a useful 
addition to your script (to avoid making you update it when the .pl file 
changes).

Thanks!

-Chris

-- 
http://nondot.org/sabre/
http://llvm.cs.uiuc.edu/