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

Remove an unused variable from the tf2_eigen test. #215

Merged
merged 1 commit into from
Apr 13, 2017
Merged

Remove an unused variable from the tf2_eigen test. #215

merged 1 commit into from
Apr 13, 2017

Conversation

clalancette
Copy link
Contributor

While we are in here, also kill off some trailing whitespace.

Signed-off-by: Chris Lalancette [email protected]

While we are in here, also kill off some trailing whitespace.

Signed-off-by: Chris Lalancette <[email protected]>
@clalancette
Copy link
Contributor Author

clalancette commented Mar 28, 2017

The kinetic build is "unstable", but in the same way that all previous builds are; it looks like it mostly comes from the eigen compatibility stuff for older distributions. So I don't think we need to worry about that one w.r.t. this pull request.

The jade one also is "unstable", for the same reason as the kinetic one. The odd thing is that all the previous (and subsequent) builds are marked green, while just this one is flagged for being unstable. Not sure what is going on there.

@mikaelarguedas
Copy link
Member

The jobs are marked as unstable if there are compiler warning only since kinetic (so not for Jade and Indigo).
The jade failure is unrelated to the warning, it's due to a test failure

@clalancette
Copy link
Contributor Author

Oh, right, now I see. I must have clicked on the wrong thing before. Thanks for the heads up. That failing test looks unrelated to this PR; tf2_ros doesn't depend on tf2_eigen in any way, and I didn't touch any other code that would change that (as far as I can tell).

@mikaelarguedas
Copy link
Member

Yes it looks like a flaky test based on the job history. The compiler warning should be fixed though because otherwise the maintainer will receive an email for every PR opened and commit added to this repo

@clalancette
Copy link
Contributor Author

Yeah, I agree. @k-okada ended up doing a fairly nice solution for eigen_stl_containers; I'll look at porting that over to tf2_eigen.

In any case, that problem is independent of this PR, so we can address it separately.

@tfoote
Copy link
Member

tfoote commented Mar 30, 2017

@ros-pull-request-builder retest this please

1 similar comment
@tfoote
Copy link
Member

tfoote commented Apr 13, 2017

@ros-pull-request-builder retest this please

@tfoote tfoote merged commit 89c15a9 into ros:indigo-devel Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants