Has anyone used CDash for testing Orocos? I've got it working for RTT, but it requires some minor changes. I'm wondering if anyone else is interested in this capability?
The tests directory, in particular, requires modifications to the dependancies to get the tests to build after the main libraries, and also needs the "EXCLUDE FROM_ALL" turned off. Overall the mod's are quite minor IMHO.
Using CDash for automated testing
On Tue, Aug 25, 2009 at 03:32, <kiwi [dot] net [..] ...> wrote:
> Has anyone used CDash for testing Orocos? I've got it working for RTT, but it requires some minor changes. I'm wondering if anyone else is interested in this capability?
>
> The tests directory, in particular, requires modifications to the dependancies to get the tests to build after the main libraries, and also needs the "EXCLUDE FROM_ALL" turned off. Overall the mod's are quite minor IMHO.
It's on my list of things to do (together with the build farm VMs)
when I actually get ahead of schedule :-)
We could control the flags you mention with a -DCDASH_FEATURE=ON (or
similar) cmake variable.
Peter
Using CDash for automated testing
On Aug 25, 2009, at 03:43 , Peter Soetens wrote:
> On Tue, Aug 25, 2009 at 03:32, <kiwi [dot] net [..] ...> wrote:
>> Has anyone used CDash for testing Orocos? I've got it working for
>> RTT, but it requires some minor changes. I'm wondering if anyone
>> else is interested in this capability?
>>
>> The tests directory, in particular, requires modifications to the
>> dependancies to get the tests to build after the main libraries,
>> and also needs the "EXCLUDE FROM_ALL" turned off. Overall the
>> mod's are quite minor IMHO.
>
> It's on my list of things to do (together with the build farm VMs)
> when I actually get ahead of schedule :-)
Great minds thing alike ... we've gotten bitten too many times by not-
compiling-due-to-damn-corba that we're doing the same.
> We could control the flags you mention with a -DCDASH_FEATURE=ON (or
> similar) cmake variable.
I was thinking something similar, although it may not be required. The
real change to the tests dir is to make the tests correctly depend on
the library (they don't now). This way, when ENABLE_TESTING() is on
the tests automatically get built without needing the "make
check" (but they aren't run until you "make check").
Patch is attached for what it's taken on Mac and Jaunty.
S
Using CDash for automated testing
On Tue, Aug 25, 2009 at 13:39, Stephen Roderick<kiwi [dot] net [..] ...> wrote:
> On Aug 25, 2009, at 03:43 , Peter Soetens wrote:
>
>> On Tue, Aug 25, 2009 at 03:32, <kiwi [dot] net [..] ...> wrote:
>>>
>>> Has anyone used CDash for testing Orocos? I've got it working for RTT,
>>> but it requires some minor changes. I'm wondering if anyone else is
>>> interested in this capability?
>>>
>>> The tests directory, in particular, requires modifications to the
>>> dependancies to get the tests to build after the main libraries, and also
>>> needs the "EXCLUDE FROM_ALL" turned off. Overall the mod's are quite minor
>>> IMHO.
>>
>> It's on my list of things to do (together with the build farm VMs)
>> when I actually get ahead of schedule :-)
>
> Great minds thing alike ... we've gotten bitten too many times by
> not-compiling-due-to-damn-corba that we're doing the same.
>
>> We could control the flags you mention with a -DCDASH_FEATURE=ON (or
>> similar) cmake variable.
>
> I was thinking something similar, although it may not be required. The real
> change to the tests dir is to make the tests correctly depend on the library
> (they don't now). This way, when ENABLE_TESTING() is on the tests
> automatically get built without needing the "make check" (but they aren't
> run until you "make check").
Ack.
>
> Patch is attached for what it's taken on Mac and Jaunty.
The patch needs a little bit of cleanup in tests/CMakeLists.txt .Do
you mind that I commit a correct version or do you resubmit ?
Peter
Using CDash for automated testing
On Aug 25, 2009, at 09:04 , Peter Soetens wrote:
> On Tue, Aug 25, 2009 at 13:39, Stephen Roderick<kiwi [dot] net [..] ...>
> wrote:
>> On Aug 25, 2009, at 03:43 , Peter Soetens wrote:
>>
>>> On Tue, Aug 25, 2009 at 03:32, <kiwi [dot] net [..] ...> wrote:
>>>>
>>>> Has anyone used CDash for testing Orocos? I've got it working for
>>>> RTT,
>>>> but it requires some minor changes. I'm wondering if anyone else is
>>>> interested in this capability?
>>>>
>>>> The tests directory, in particular, requires modifications to the
>>>> dependancies to get the tests to build after the main libraries,
>>>> and also
>>>> needs the "EXCLUDE FROM_ALL" turned off. Overall the mod's are
>>>> quite minor
>>>> IMHO.
>>>
>>> It's on my list of things to do (together with the build farm VMs)
>>> when I actually get ahead of schedule :-)
>>
>> Great minds thing alike ... we've gotten bitten too many times by
>> not-compiling-due-to-damn-corba that we're doing the same.
>>
>>> We could control the flags you mention with a -DCDASH_FEATURE=ON
>>> (or
>>> similar) cmake variable.
>>
>> I was thinking something similar, although it may not be required.
>> The real
>> change to the tests dir is to make the tests correctly depend on
>> the library
>> (they don't now). This way, when ENABLE_TESTING() is on the tests
>> automatically get built without needing the "make check" (but they
>> aren't
>> run until you "make check").
>
> Ack.
>
>>
>> Patch is attached for what it's taken on Mac and Jaunty.
>
> The patch needs a little bit of cleanup in tests/CMakeLists.txt .Do
> you mind that I commit a correct version or do you resubmit ?
As a side note, do you know how to force cdash/ctest to do parallel
"builds" - not parallel test runs? It seems to drop the -jN if you
type "make -j6 Experimental". And Orocos takes damn forever to build ...
I intend to post on cmake list. Can't find anything via google to
date ...
S
Using CDash for automated testing
On Aug 25, 2009, at 09:04 , Peter Soetens wrote:
> On Tue, Aug 25, 2009 at 13:39, Stephen Roderick<kiwi [dot] net [..] ...>
> wrote:
>> On Aug 25, 2009, at 03:43 , Peter Soetens wrote:
>>
>>> On Tue, Aug 25, 2009 at 03:32, <kiwi [dot] net [..] ...> wrote:
>>>>
>>>> Has anyone used CDash for testing Orocos? I've got it working for
>>>> RTT,
>>>> but it requires some minor changes. I'm wondering if anyone else is
>>>> interested in this capability?
>>>>
>>>> The tests directory, in particular, requires modifications to the
>>>> dependancies to get the tests to build after the main libraries,
>>>> and also
>>>> needs the "EXCLUDE FROM_ALL" turned off. Overall the mod's are
>>>> quite minor
>>>> IMHO.
>>>
>>> It's on my list of things to do (together with the build farm VMs)
>>> when I actually get ahead of schedule :-)
>>
>> Great minds thing alike ... we've gotten bitten too many times by
>> not-compiling-due-to-damn-corba that we're doing the same.
>>
>>> We could control the flags you mention with a -DCDASH_FEATURE=ON
>>> (or
>>> similar) cmake variable.
>>
>> I was thinking something similar, although it may not be required.
>> The real
>> change to the tests dir is to make the tests correctly depend on
>> the library
>> (they don't now). This way, when ENABLE_TESTING() is on the tests
>> automatically get built without needing the "make check" (but they
>> aren't
>> run until you "make check").
>
> Ack.
So this change in behaviour is ok then? That was my only real concern.
>> Patch is attached for what it's taken on Mac and Jaunty.
>
> The patch needs a little bit of cleanup in tests/CMakeLists.txt .Do
> you mind that I commit a correct version or do you resubmit ?
Be my guest. I was hacking and expected (sorry!) you to have to clean
it up some.
S
Using CDash for automated testing
Has anyone used CDash for testing Orocos? I've got it working for RTT, but it requires some minor changes. I'm wondering if anyone else is interested in this capability?
The tests directory, in particular, requires modifications to the dependancies to get the tests to build after the main libraries, and also needs the "EXCLUDE FROM_ALL" turned off. Overall the mod's are quite minor IMHO.