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

Feature/autoware health checker #1943

Merged
merged 44 commits into from
Feb 5, 2019
Merged

Conversation

hakuturu583
Copy link

Status

DEVELOPMENT

Description

autowarefoundation/autoware_ai#494

Todos

  • Tests
  • Documentation

Steps to Test or Reproduce

catkin_make
rosrun autoware_health_checker health_aggreator

Copy link

@yn-mrse yn-mrse left a comment

Choose a reason for hiding this comment

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

I approved this feature!

@sgermanserrano
Copy link

@hakuturu583 I have opened a PR #1956 to fix the CI failure. Can you also add unit tests for the new code? I can help you getting started with it.

@hakuturu583
Copy link
Author

@sgermanserrano Thank you for your advice!!
I add test code for health_checker.

@hakuturu583 hakuturu583 merged commit c7c88a1 into develop Feb 5, 2019
@hakuturu583 hakuturu583 deleted the feature/autoware_health_checker branch February 5, 2019 06:50
@yn-mrse yn-mrse mentioned this pull request Feb 15, 2019
2 tasks
@dejanpan dejanpan mentioned this pull request Feb 25, 2019
2 tasks
@dejanpan
Copy link

@hakuturu583 this feature seems very similar to http://wiki.ros.org/robot_monitor tool. Did you consider a robot_monitor tool when implementing this PR?


uint8_t test_function(double value)
{
if(value == 0.0)
Copy link

@dejanpan dejanpan Feb 25, 2019

Choose a reason for hiding this comment

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

you should not do the == comparison with float

@dejanpan
Copy link

@hakuturu583 @yn-mrse this PR changes 82 files in Autoware. For the entire PR there is but one test file. How can you be sure that you did not break something else by introducing such a big change?

Also:

  1. Why is there no doxygen comments?
  2. Why is there no design document about what this feature does?

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

Successfully merging this pull request may close these issues.

6 participants