[LLVMdev] Unexpected failures in the DejaGNU test collection

[Daniel Dunbar]

On Tue, Jul 14, 2009 at 11:08 AM, Tanya Lattner<lattner at apple.com> wrote:
>
> On Jul 14, 2009, at 10:03 AM, Devang Patel wrote:
>
> On Tue, Jul 14, 2009 at 8:49 AM, Daniel Dunbar<daniel at zuster.org> wrote:
>
> Since it came up, what is blocking us from putting these tests in the
>
> llvm-gcc test suite instead of in the LLVM test suite?
>
> Usually we want to check these tests regularly against llvm backend
> changes. The nightly tester does not svn update and rebuild llvm-gcc
> hence these tests are in LLVM Test Suite. BTW, llvm-gcc test suite
> already has llvm.objc and llvm-obj-c++ folders for llvm related tests.
>
>
> Do the nightly testers even run the llvm-gcc test suite or keep track of
> those results? I'm pretty sure they don't.

I think it wouldn't be too hard to incorporate this; we could only
check the llvm specific directories.

> It is also not our release criteria. So something to keep in mind.

If its incorporated into the nightlytest, it automatically becomes
part of the release criteria, right?

 - Daniel

> -Tanya
>
> -
> Devang
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>