Hi,
I a a brand new installation of Orocos 2.2.1 made with the
orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos) env.sh
scripts.
I run the rtt_ros_integration_example (sh run.sh) to check everything is OK.
I went into the rrt/bin directory where some tests are available. I run all
of them and some success, some failed, some failed with memory access
violation.
Are these tests uptodate ? Do I have something wrong on my installation ?
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/enum_type_test
Running 4 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/enum_type_test.cpp(83):
fatal error in "testEnumIntConversion": critical check Types()->type("int")
failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/enum_type_test.cpp(121):
fatal error in "testEnumStringConversion": critical check ts failed
unknown location(0): fatal error in "testEnumSaveIntProperties": memory
access violation at address: 0x00000008: no mapping at fault address
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/enum_type_test.cpp(168):
last checkpoint
*** 3 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/function_test
Running 11 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testSimpleReturnFunction": Parse error at line 1: Semantic
error: Return type 'int' for function 'foo' is an unknown type.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testOnlyExportFunction": Parse error at line 4: Semantic
error: Return type 'int' for function 'foo_ret' is an unknown type.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testReturnExportFunction": Parse error at line 4: Semantic
error: Return type 'int' for function 'foo_ret' is an unknown type.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testCallFunction": Parse error at line 1: Semantic error:
"int" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testFunctionStack": Parse error at line 2: Semantic error:
"double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testFunctionExportArgs": Parse error at line 1: Semantic
error: "int" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testFunctionCallArgs": Parse error at line 1: Semantic
error: "int" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/function_test.cpp(460):
fatal error in "testFunctionFail": Parse error at line 8: Semantic error:
"bool" is an unknown type...
*** 8 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/marshalling_test
Running 1 test case...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/marshalling_test.cpp(43):
fatal error in "TestGetProvider": critical check sc failed
*** 1 failure detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/mqueue-test
Running 5 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/mqueue_test.cpp(211):
fatal error in "testPortConnections": critical check
mw1->createConnection(*mr2, policy) failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/mqueue_test.cpp(262):
fatal error in "testPortStreams": critical check mw1->createStream( policy )
failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/mqueue_test.cpp(364):
fatal error in "testVectorTransport": critical check vout.createStream(
policy ) failed
*** 3 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/plugins_test
Running 4 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/plugins_test.cpp(62):
error in "testTypePlugins": check pl->isLoaded("typekit_plugin") failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/plugins_test.cpp(63):
error in "testTypePlugins": check pl->isLoaded("TypesPluginTest") failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/plugins_test.cpp(71):
fatal error in "testTypePlugin": critical check
pl->loadTypekit("typekit_plugin", ".") failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/plugins_test.cpp(81):
error in "testServicePlugins": check pl->isLoaded("service_plugin") failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/plugins_test.cpp(82):
error in "testServicePlugins": check pl->isLoaded("serviceplugin") failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/plugins_test.cpp(90):
fatal error in "testServicePlugin": critical check
pl->loadService("serviceplugin", tc) failed
*** 6 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/program_test
Running 12 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testParseProgram": Parse error at line 7: Fatal Semantic
error: Cannot apply binary operation unknown_t == unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramCondition": Parse error at line 23: Semantic
error: "bool" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramBreak": Parse error at line 3: Fatal Semantic
error: Cannot apply binary operation unknown_t != unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramAnd": Parse error at line 2: Fatal Semantic
error: Cannot apply binary operation unknown_t && unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramTry": Parse error at line 3: Fatal Semantic
error: Cannot apply binary operation unknown_t && unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramToProgram": Parse error at line 3: Fatal Semantic
error: Cannot apply binary operation unknown_t == unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramCallFoo": Parse error at line 2: Fatal Semantic
error: Cannot apply unary operator "+" to unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testProgramDoFoo": Parse error at line 2: Fatal Semantic
error: Cannot apply unary operator "+" to unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/program_test.cpp(405):
fatal error in "testSend": Parse error at line 6: Semantic error:
"SendHandle" is an unknown type...
*** 9 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/property_loader_test
Running 4 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(69):
error in "testPropSaveLoad": check pl.configure(filename, &tc, true) failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(88):
error in "testPropSaveLoad": check pl.configure(filename, &tc, true) failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(119):
fatal error in "testPropLoading": critical check pl.load(filename, &tc)
failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(162):
error in "testPropStoring": check tc.provides()->hasProperty("pdoubles")
failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(168):
error in "testPropStoring": check bag.size() == 3 failed [2 != 3]
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(170):
error in "testPropStoring": check bag.find("pdoubles") failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_loader_test.cpp(177):
fatal error in "testPropStoring": critical check bagvector.ready() failed
*** 7 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/property_marsh_test
Running 3 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_marsh_test.cpp(114):
fatal error in "testPropMarshVect": critical check bag.ready() failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/property_marsh_test.cpp(143):
fatal error in "testPropMarshVectLegacy": critical check pd.deserialize(
source ) failed
*** 2 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/scripting_test
Running 1 test case...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/scripting_test.cpp(53):
fatal error in "TestGetProvider": critical check sc failed
*** 1 failure detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/state_test
Running 14 test cases...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testParseState": Parse error at line 2: Semantic error:
"int" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(974):
fatal error in "testStateFailure": critical check sm failed
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateChildren": Parse error at line 2: Semantic error:
"double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateTransitions": Parse error at line 3: Semantic
error: "int" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateTransitionStop": Parse error at line 4: Fatal
Semantic error: Cannot apply binary operation unknown_t == unknown_t.
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateGlobalTransitions": Parse error at line 2: Semantic
error: "int" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateSubStateVars": Parse error at line 2: Semantic
error: "double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateSubStateCommands": Parse error at line 2: Semantic
error: "double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateOperationSignalTransition": Parse error at line 2:
Semantic error: "double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateOperationSignalTransitionProgram": Parse error at
line 2: Semantic error: "double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateOperationSignalGuard": Parse error at line 2:
Semantic error: "double" is an unknown type...
/media/DD_data/home/ard/ros/orocos_toolchain_ros/rtt/build/orocos-toolchain-rtt/tests/state_test.cpp(955):
fatal error in "testStateEvents": Parse error at line 2: Semantic error:
"int" is an unknown type...
*** 12 failures detected in test suite "Master Test Suite"
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
./rtt/bin/types_test
Running 8 test cases...
unknown location(0): fatal error in "testStringCapacity": memory access
violation at address: 0x00000000: no mapping at fault address
*** 1 failure detected in test suite "Master Test Suite"
running rtt tests failed
On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
> Hi,
>
> I a a brand new installation of Orocos 2.2.1 made with the
> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos) env.sh
> scripts.
> I run the rtt_ros_integration_example (sh run.sh) to check everything is
> OK.
>
> I went into the rrt/bin directory where some tests are available. I run all
> of them and some success, some failed, some failed with memory access
> violation.
> Are these tests uptodate ? Do I have something wrong on my installation ?
Yes. The unit tests don't work in your environment because they can't find the
type kits. They don't test rigorously for that, and may segfault if none is
found.
I don't understand how the unit tests ended up in the rtt/bin dir or how
*anything* ended up in there... The tests should have been generated in
rtt/build/tests.
Steven, did you change something on the orocos_toolchain_ros branch that
modifies the RTT build logic ???
Peter
running rtt tests failed
2011/2/4 Peter Soetens <peter [..] ...>:
> On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
>> Hi,
>>
>> I a a brand new installation of Orocos 2.2.1 made with the
>> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos) env.sh
>> scripts.
>> I run the rtt_ros_integration_example (sh run.sh) to check everything is
>> OK.
>>
>> I went into the rrt/bin directory where some tests are available. I run all
>> of them and some success, some failed, some failed with memory access
>> violation.
>> Are these tests uptodate ? Do I have something wrong on my installation ?
>
> Yes. The unit tests don't work in your environment because they can't find the
> type kits. They don't test rigorously for that, and may segfault if none is
> found.
>
> I don't understand how the unit tests ended up in the rtt/bin dir or how
> *anything* ended up in there... The tests should have been generated in
> rtt/build/tests.
>
> Steven, did you change something on the orocos_toolchain_ros branch that
> modifies the RTT build logic ???
Nope...
It might have to do with an old version still on the
orocos_toolchain_ros master branch, which I updated this morning.
Willy, can you do a 'git pull origin' and try again?
Steven
>
> Peter
>
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
running rtt tests failed
2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
> 2011/2/4 Peter Soetens <peter [..] ...>:
> > On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
> >> Hi,
> >>
> >> I a a brand new installation of Orocos 2.2.1 made with the
> >> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos) env.sh
> >> scripts.
> >> I run the rtt_ros_integration_example (sh run.sh) to check everything is
> >> OK.
> >>
> >> I went into the rrt/bin directory where some tests are available. I run
> all
> >> of them and some success, some failed, some failed with memory access
> >> violation.
> >> Are these tests uptodate ? Do I have something wrong on my installation
> ?
> >
> > Yes. The unit tests don't work in your environment because they can't
> find the
> > type kits. They don't test rigorously for that, and may segfault if none
> is
> > found.
> >
> > I don't understand how the unit tests ended up in the rtt/bin dir or how
> > *anything* ended up in there... The tests should have been generated in
> > rtt/build/tests.
> >
> > Steven, did you change something on the orocos_toolchain_ros branch that
> > modifies the RTT build logic ???
>
> Nope...
> It might have to do with an old version still on the
> orocos_toolchain_ros master branch, which I updated this morning.
> Willy, can you do a 'git pull origin' and try again?
>
I agree with it, it is probably to do my use of an old ros branch. I will
test it.
>
> Steven
>
> >
> > Peter
> >
>
running rtt tests failed
2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>
>
> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
>
> 2011/2/4 Peter Soetens <peter [..] ...>:
>> > On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
>> >> Hi,
>> >>
>> >> I a a brand new installation of Orocos 2.2.1 made with the
>> >> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos) env.sh
>> >> scripts.
>> >> I run the rtt_ros_integration_example (sh run.sh) to check everything
>> is
>> >> OK.
>> >>
>> >> I went into the rrt/bin directory where some tests are available. I run
>> all
>> >> of them and some success, some failed, some failed with memory access
>> >> violation.
>> >> Are these tests uptodate ? Do I have something wrong on my installation
>> ?
>> >
>> > Yes. The unit tests don't work in your environment because they can't
>> find the
>> > type kits. They don't test rigorously for that, and may segfault if none
>> is
>> > found.
>> >
>> > I don't understand how the unit tests ended up in the rtt/bin dir or how
>> > *anything* ended up in there... The tests should have been generated in
>> > rtt/build/tests.
>> >
>> > Steven, did you change something on the orocos_toolchain_ros branch that
>> > modifies the RTT build logic ???
>>
>> Nope...
>> It might have to do with an old version still on the
>> orocos_toolchain_ros master branch, which I updated this morning.
>> Willy, can you do a 'git pull origin' and try again?
>>
>
> I agree with it, it is probably to do my use of an old ros branch. I will
> test it.
>
Peter you were rigth, there is nothing in this folder now. It was a
versionning problem with orocos_toolchain_ros due to my missuse of git.
Behind this problem I think it not so easy to know which version we are
using when you a the orocos folder pre-installed. It is not the first time I
face this. I think we should add something to know which version is compiled
of what. The easiest place would be in the task browser or with some
--version commands. Of course I could search in rtt documentation where is
the version.h of rtt but it's not a so easy-use
>
>
>
>>
>> Steven
>>
>> >
>> > Peter
>> >
>>
>
>
running rtt tests failed
On Friday 04 February 2011 17:00:04 Willy Lambert wrote:
> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>
> > 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
> >
> > 2011/2/4 Peter Soetens <peter [..] ...>:
> >> > On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
> >> >> Hi,
> >> >>
> >> >> I a a brand new installation of Orocos 2.2.1 made with the
> >> >> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos)
> >> >> env.sh scripts.
> >> >> I run the rtt_ros_integration_example (sh run.sh) to check everything
> >>
> >> is
> >>
> >> >> OK.
> >> >>
> >> >> I went into the rrt/bin directory where some tests are available. I
> >> >> run
> >>
> >> all
> >>
> >> >> of them and some success, some failed, some failed with memory access
> >> >> violation.
> >> >> Are these tests uptodate ? Do I have something wrong on my
> >> >> installation
> >>
> >> ?
> >>
> >> > Yes. The unit tests don't work in your environment because they can't
> >>
> >> find the
> >>
> >> > type kits. They don't test rigorously for that, and may segfault if
> >> > none
> >>
> >> is
> >>
> >> > found.
> >> >
> >> > I don't understand how the unit tests ended up in the rtt/bin dir or
> >> > how *anything* ended up in there... The tests should have been
> >> > generated in rtt/build/tests.
> >> >
> >> > Steven, did you change something on the orocos_toolchain_ros branch
> >> > that modifies the RTT build logic ???
> >>
> >> Nope...
> >> It might have to do with an old version still on the
> >> orocos_toolchain_ros master branch, which I updated this morning.
> >> Willy, can you do a 'git pull origin' and try again?
> >
> > I agree with it, it is probably to do my use of an old ros branch. I will
> > test it.
>
> Peter you were rigth, there is nothing in this folder now. It was a
> versionning problem with orocos_toolchain_ros due to my missuse of git.
>
> Behind this problem I think it not so easy to know which version we are
> using when you a the orocos folder pre-installed. It is not the first time
> I face this. I think we should add something to know which version is
> compiled of what. The easiest place would be in the task browser or with
> some --version commands. Of course I could search in rtt documentation
> where is the version.h of rtt but it's not a so easy-use
We all use this command prompt for identifying on which branch we are. It is
difficult to use git without this prompt:
export PS1="\[\e]0;\u@\h: \w\a\]\[\033[01;32m\]\h\[\033[01;34m\]
\w\[\033[31m\]$(__git_ps1 "(%s)") \[\033[01;34m\]$\[\033[00m\]"
The important part is $(__git_ps1 "(%s)") which prints out the git branch you
are on and if you're merging, rebasing etc. To test it, just do a:
echo $(__git_ps1 "(%s)")
Inside and outside a git repository.
Or copy paste the export statement above in a bash console and cd a bit
around, change a branch etc.
Peter
running rtt tests failed
2011/2/7 Peter Soetens <peter [..] ...>
> On Friday 04 February 2011 17:00:04 Willy Lambert wrote:
> > 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
> >
> > > 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
> > >
> > > 2011/2/4 Peter Soetens <peter [..] ...>:
> > >> > On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
> > >> >> Hi,
> > >> >>
> > >> >> I a a brand new installation of Orocos 2.2.1 made with the
> > >> >> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos)
> > >> >> env.sh scripts.
> > >> >> I run the rtt_ros_integration_example (sh run.sh) to check
> everything
> > >>
> > >> is
> > >>
> > >> >> OK.
> > >> >>
> > >> >> I went into the rrt/bin directory where some tests are available. I
> > >> >> run
> > >>
> > >> all
> > >>
> > >> >> of them and some success, some failed, some failed with memory
> access
> > >> >> violation.
> > >> >> Are these tests uptodate ? Do I have something wrong on my
> > >> >> installation
> > >>
> > >> ?
> > >>
> > >> > Yes. The unit tests don't work in your environment because they
> can't
> > >>
> > >> find the
> > >>
> > >> > type kits. They don't test rigorously for that, and may segfault if
> > >> > none
> > >>
> > >> is
> > >>
> > >> > found.
> > >> >
> > >> > I don't understand how the unit tests ended up in the rtt/bin dir or
> > >> > how *anything* ended up in there... The tests should have been
> > >> > generated in rtt/build/tests.
> > >> >
> > >> > Steven, did you change something on the orocos_toolchain_ros branch
> > >> > that modifies the RTT build logic ???
> > >>
> > >> Nope...
> > >> It might have to do with an old version still on the
> > >> orocos_toolchain_ros master branch, which I updated this morning.
> > >> Willy, can you do a 'git pull origin' and try again?
> > >
> > > I agree with it, it is probably to do my use of an old ros branch. I
> will
> > > test it.
> >
> > Peter you were rigth, there is nothing in this folder now. It was a
> > versionning problem with orocos_toolchain_ros due to my missuse of git.
> >
> > Behind this problem I think it not so easy to know which version we are
> > using when you a the orocos folder pre-installed. It is not the first
> time
> > I face this. I think we should add something to know which version is
> > compiled of what. The easiest place would be in the task browser or with
> > some --version commands. Of course I could search in rtt documentation
> > where is the version.h of rtt but it's not a so easy-use
>
> We all use this command prompt for identifying on which branch we are. It
> is
> difficult to use git without this prompt:
>
> export PS1="\[\e]0;\u@\h: \w\a\]\[\033[01;32m\]\h\[\033[01;34m\]
> \w\[\033[31m\]$(__git_ps1 "(%s)") \[\033[01;34m\]$\[\033[00m\]"
>
> The important part is $(__git_ps1 "(%s)") which prints out the git branch
> you
> are on and if you're merging, rebasing etc. To test it, just do a:
>
> echo $(__git_ps1 "(%s)")
>
> Inside and outside a git repository.
>
> Or copy paste the export statement above in a bash console and cd a bit
> around, change a branch etc.
>
thanks for this, I'll use it
But I was more thinking about the operationnal use of Orocos. When I go onto
my robot after a bootstraped installation, is it still usable ?
>
>
> Peter
>
running rtt tests failed
On Monday 07 February 2011 19:19:31 Willy Lambert wrote:
> 2011/2/7 Peter Soetens <peter [..] ...>
>
> > On Friday 04 February 2011 17:00:04 Willy Lambert wrote:
> > > 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
> > >
> > > > 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
> > > >
> > > > 2011/2/4 Peter Soetens <peter [..] ...>:
> > > >> > On Wednesday 02 February 2011 21:00:38 Willy Lambert wrote:
> > > >> >> Hi,
> > > >> >>
> > > >> >> I a a brand new installation of Orocos 2.2.1 made with the
> > > >> >> orocos_toolchain_ros. I sourced the (ROS) setup.sh and (Orocos)
> > > >> >> env.sh scripts.
> > > >> >> I run the rtt_ros_integration_example (sh run.sh) to check
> >
> > everything
> >
> > > >> is
> > > >>
> > > >> >> OK.
> > > >> >>
> > > >> >> I went into the rrt/bin directory where some tests are available.
> > > >> >> I run
> > > >>
> > > >> all
> > > >>
> > > >> >> of them and some success, some failed, some failed with memory
> >
> > access
> >
> > > >> >> violation.
> > > >> >> Are these tests uptodate ? Do I have something wrong on my
> > > >> >> installation
> > > >>
> > > >> ?
> > > >>
> > > >> > Yes. The unit tests don't work in your environment because they
> >
> > can't
> >
> > > >> find the
> > > >>
> > > >> > type kits. They don't test rigorously for that, and may segfault
> > > >> > if none
> > > >>
> > > >> is
> > > >>
> > > >> > found.
> > > >> >
> > > >> > I don't understand how the unit tests ended up in the rtt/bin dir
> > > >> > or how *anything* ended up in there... The tests should have
> > > >> > been generated in rtt/build/tests.
> > > >> >
> > > >> > Steven, did you change something on the orocos_toolchain_ros
> > > >> > branch that modifies the RTT build logic ???
> > > >>
> > > >> Nope...
> > > >> It might have to do with an old version still on the
> > > >> orocos_toolchain_ros master branch, which I updated this morning.
> > > >> Willy, can you do a 'git pull origin' and try again?
> > > >
> > > > I agree with it, it is probably to do my use of an old ros branch. I
> >
> > will
> >
> > > > test it.
> > >
> > > Peter you were rigth, there is nothing in this folder now. It was a
> > > versionning problem with orocos_toolchain_ros due to my missuse of git.
> > >
> > > Behind this problem I think it not so easy to know which version we are
> > > using when you a the orocos folder pre-installed. It is not the first
> >
> > time
> >
> > > I face this. I think we should add something to know which version is
> > > compiled of what. The easiest place would be in the task browser or
> > > with some --version commands. Of course I could search in rtt
> > > documentation where is the version.h of rtt but it's not a so easy-use
> >
> > We all use this command prompt for identifying on which branch we are. It
> > is
> > difficult to use git without this prompt:
> >
> > export PS1="\[\e]0;\u@\h: \w\a\]\[\033[01;32m\]\h\[\033[01;34m\]
> > \w\[\033[31m\]$(__git_ps1 "(%s)") \[\033[01;34m\]$\[\033[00m\]"
> >
> > The important part is $(__git_ps1 "(%s)") which prints out the git branch
> > you
> > are on and if you're merging, rebasing etc. To test it, just do a:
> >
> > echo $(__git_ps1 "(%s)")
> >
> > Inside and outside a git repository.
> >
> > Or copy paste the export statement above in a bash console and cd a bit
> > around, change a branch etc.
>
> thanks for this, I'll use it
>
> But I was more thinking about the operationnal use of Orocos. When I go
> onto my robot after a bootstraped installation, is it still usable ?
Well, it requires the sources to be there. I think it's best to add a --
version option to our tools as you suggest.
Peter