New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre-release test never got "SUCCESS" on Hydro #416
Comments
I think it is because ros build firm (including devel and pre-release) did not run omniorb-nameserver[1], so we have to manually start name server[2], but there might be some issues:
[1] ros-infrastructure/jenkins_scripts#67 (comment) |
Hmm, indeed.
Is there any reason why this patch is not yet applied? And where is this patch supposed to be applied? |
this should be patched against OpenRTM-aist-1.1.0/utils/rtm-naming/rtm-naming, but in order to keep original behavior, i think it is better to use command line option for proposed behavior. |
I see.
I see.
How is this achievable on buildfarm? |
|
(test-hironx-ros-bridge.test) Add omniNames script to start it on ros buildfarm (see start-jsk/rtmros_common#416 (comment))
http://jenkins.ros.org/view/Prerelease/job/prerelease-hydro-rtmros_common/
Since February 2014 up to now, no test ever succeeded; either unstable or failure.
Failure
is fine, since it definitely needs to be taken care of immediately. Now the problem isunstable
, since it makes our judgement difficult whether we can make a new release or not.Looking at the last pre-release test, what failed are:
__main__.TestOpenrtmTools.test_rtshell_setup
0.16 sec 5test_hironx*.xml
will be handled in start-jsk/rtmros_hironx#50.What about others?
The text was updated successfully, but these errors were encountered: