> I've run the test last night to see how long it takes, and I can
> afford to cronjob it for the night.
Great!
> I didn't quite realize it would automatically send the report, but
> it did [1] and there are a few test failure from the
> Frontend{C,C++} directories. I suppose this is because I have
> llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is
> there a specific version of llvm-gcc that is prefered for nightly
> tests? Shall I go with the latest stable one? 4.0 or 4.2?
llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind
that you need to keep llvm-gcc in sync with llvm (same revision number).
> What does -enable-linscan do? It's not referenced anywhere in
> NewNightlyTest.pl, but it's given as example in [2].
Its an option to enable linear scan register allocator. It probably wasn't
default when the docs were written.
> I will also take the freedom to disable the nightly test if I need
> the CPU cycles for something else during a night.
Understood.
-Tanya
>
> jlh
>
> [1] http://llvm.org/nightlytest/test.php?machine=288&night=6315
> [2] http://llvm.org/docs/TestingGuide.html#nightly
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>