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

Avoidance test failing since sitl-gazebo submodule update #13123

Closed
baumanta opened this issue Oct 8, 2019 · 13 comments
Closed

Avoidance test failing since sitl-gazebo submodule update #13123

baumanta opened this issue Oct 8, 2019 · 13 comments

Comments

@baumanta
Copy link
Contributor

baumanta commented Oct 8, 2019

Since commit
commit 91badce
Author: TSC21 n.marques21@hotmail.com
Date: Sun Oct 6 11:01:45 2019 +0100

Update submodule sitl_gazebo to latest Sun Oct 06 11:02:54 GMT 2019

The PX4/avoidance cannot be run anymore. Gazebo does not start up without giving any error message.
Running under Ubuntu 16.04 with gazebo7

@baumanta
Copy link
Contributor Author

baumanta commented Oct 8, 2019

@TSC21 do you have any clue what could have gone wrong?

@TSC21
Copy link
Member

TSC21 commented Oct 8, 2019

This was reported and being solved in #13113. I am already following with @mrivi on this.

@baumanta
Copy link
Contributor Author

baumanta commented Oct 8, 2019

It does not seem to be that same bug, the one you refer to was caused by bumping the CI container. The one I observe is only present since the mentioned commit of the sitl_gazebo update.

@TSC21
Copy link
Member

TSC21 commented Oct 8, 2019

@baumanta I don't see anything on sitl_gazebo that may cause a potential bug. Can you please describe what errors do you see? Have you tried to run the simulation with gdb?

@TSC21
Copy link
Member

TSC21 commented Oct 8, 2019

Besides, all the other tests on CI using Gazebo run as they should. So this needs to be tracked to the exact usage of Gazebo for Avoidance.

@mrivi
Copy link
Contributor

mrivi commented Oct 8, 2019

the avoidance tests are the only tests that simulate a camera and that has numerous implications.
The problem I see is the following: a container update broke the CI tests since the vehicle isn't spawing anymore. The PR was merged in a rushed way not allowing all the people involed to look at it and the tests were disabled. A subsequent PR that updates the sitl gazebo submodules breaks the avoidance for 16.04 setups. Those CI tests are in place exactly to catch these problems!

@TSC21
Copy link
Member

TSC21 commented Oct 8, 2019

So let's track them.

@baumanta
Copy link
Contributor Author

baumanta commented Oct 9, 2019

update: the bug seems to be present on 18.04 and 16.04. It seems to be a corner case in the model spawning. Models containing lidars as well as depth cameras do not work. Both elements individually seem to be fine

@mrivi
Copy link
Contributor

mrivi commented Oct 9, 2019

@dagar - please read my comment above

@TSC21
Copy link
Member

TSC21 commented Oct 9, 2019

update: the bug seems to be present on 18.04 and 16.04. It seems to be a corner case in the model spawning. Models containing lidars as well as depth cameras do not work. Both elements individually seem to be fine

As we spoke, I am bisecting this directly on the code blocks. This is a corner case on models that contain both lidar (and probably sonar models) together with depth camera models. The same problem does not happen when the model include just the lidar or just the depth camera. So that's why this only happens with the avoidance models. The changes on the gazebo lidar plugin may be causing this, but it's not confirmed. After the source is found, sitl_gazebo will be updated again.

@TSC21 TSC21 changed the title SITL ROS broken since sitl-gazebo submodule update Avoidance test failing since sitl-gazebo submodule update Oct 9, 2019
@TSC21 TSC21 added Feature: Avoidance Sim: gazebo classic Gazebo classic simulator labels Oct 9, 2019
@mrpollo mrpollo added this to the Release v1.10.0 milestone Oct 9, 2019
@TSC21
Copy link
Member

TSC21 commented Oct 11, 2019

This has already been solved with #13151 and should reactivate the CI stages as soon as #13113 gets merged. The only thing here missing is the Avoidance team to align if they want to do a new Avoidance release or keep track of the master branch on the CI tests.

@mrpollo
Copy link
Contributor

mrpollo commented Oct 15, 2019

Was this issue resolved with #13151 ?

@mrivi
Copy link
Contributor

mrivi commented Oct 15, 2019

fixed by #13113

@mrivi mrivi closed this as completed Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants