Skip to content
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

jenkins: pub_test needs to start px4 in daemon mode #12483

Merged
merged 1 commit into from
Jul 16, 2019

Conversation

lamping7
Copy link
Member

Addressing #12475. I remember this occurring in the past with our other tests. Jenkinsfile-SITL_tests are all run in daemon mode.

It looks like Jenkins does something weird with the interactive shell that shuts down px4.

Copy link
Member

@bkueng bkueng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging now, as it fixes CI, thanks @lamping7.

I'm also seeing

[ERROR] [1563203867.630207499, 1.876000000]: ODOM: Ex: The tf tree is invalid because it contains a loop.

on the Catkin build on ROS.

<include file="$(find px4)/launch/mavros_posix_sitl.launch">
<arg name="gui" value="false"/>
<arg name="interactive" value="false"/>
<arg name="verbose" value="true"/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we want the verbose gazebo output?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do. It's useful for sitl_gazebo issues. We have this for all other CI SITL testing.

@bkueng bkueng merged commit efad34e into PX4:master Jul 16, 2019
@lamping7
Copy link
Member Author

That error is mavros related I believe.

@lamping7 lamping7 deleted the pr-jenkins_pub_test branch July 16, 2019 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants