llvm dev - Jul 2009 - [LLVMdev] Unexpected failures in the DejaGNU test collection

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.

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

-Tanya
> -
> Devang
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090714/1a708868/attachment.html>

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.
There is no point running llvm-gcc test suite if llvm-gcc is not updated :)
-
Devang

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

On Jul 16, 2009, at 10:56 AM, Daniel Dunbar wrote:
> 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.
>
I'd be fine with that. I don't know if gcc's test suite runs cleanly
on its own, so avoiding running everything is preferred because that  
would be a lot of noise if no one is going to fix the issues that are  
not llvm specific.

>> 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?
>
Most likely. Things that become release criteria are things that are  
regularly tested and people are actively fixing the failures that occur.

-Tanya
> - 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
>>
>>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090716/f223f49f/attachment.html>