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

Tracking bug for reverting changes made to ported packages for field initialization #422

Closed
11 of 20 tasks
clalancette opened this issue Nov 2, 2017 · 5 comments
Closed
11 of 20 tasks
Labels
enhancement New feature or request

Comments

@clalancette
Copy link
Contributor

clalancette commented Nov 2, 2017

During the development of ROS2 beta2 and beta3, we fixed a bunch of flaky tests by manually initializing fields in the test code. Now that the zero initialization work has gone in (ros2/rosidl#236), we can revert those changes. In some cases, these repositories are forks from upstream ROS1 versions, so these reverts will get the forks closer to upstream. While we are at it, we should probably consider merging fixes from the ROS2 forked versions to their upstreams, and merging fixes from their upstreams to the ROS2 forked versions.

@mikaelarguedas
Copy link
Member

@clalancette is it something that's still on your radar?

@mikaelarguedas mikaelarguedas added the enhancement New feature or request label Mar 8, 2018
@clalancette
Copy link
Contributor Author

While this would be a good thing to do to get us back closer to the respective upstreams, it is not a priority for me right now.

@dirk-thomas
Copy link
Member

Please prioritize this item in order to close it out and reduce the difference of the ROS 2 forks/branches.

@mikaelarguedas
Copy link
Member

@clalancette FYI I reverted the changes on the first few repos and updated the issue description accordingly.

Can you please use permalinks in the future? (several links were dead making it harder to track down the changes)
Thanks!

@clalancette
Copy link
Contributor Author

The first half of this was done long ago. The remaining items either are old (and need an update to bring up to new ROS 2 anyway), deprecated, or already done. Because of all of that, I'm going to go ahead and close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants