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

Fix/autoware shutdown #1077

Merged
merged 18 commits into from
Feb 8, 2024
Merged

Fix/autoware shutdown #1077

merged 18 commits into from
Feb 8, 2024

Conversation

yamacir-kit
Copy link
Collaborator

@yamacir-kit yamacir-kit commented Aug 24, 2023

Types of PR

  • New Features
  • Upgrade of existing features
  • Bugfix

Description

Fixed two known issues with simulator shutdown of Autoware.

1

When the simulator was shutting down Autoware, if an Autoware node became unresponsive due to a segmentation fault or other reason, the simulator could wait indefinitely for that node. This pull request changes such a case to send a SIGKILL only once to the process group that includes the launch process of Autoware, and then proceed to the subsequent process. This change also eliminates the problem that Autoware nodes were sometimes not properly terminated (typically, the rviz2 process was often not terminated).

2

In the simulator shutdown process, there is a process that takes a very long time. During such a process, the simulator becomes unresponsive and is judged "not good" by status_monitor. This is believed to be the cause of the "health check failed" problem that has been reported recently on Autoware Evaluator. To address this, this pull request changes the threshold at which status_monitor judges "not good" when starting a long process (common::StatusMonitor::overrideThreshold).

@yamacir-kit yamacir-kit added the bug Something isn't working label Aug 24, 2023
@yamacir-kit yamacir-kit self-assigned this Aug 24, 2023
@yamacir-kit yamacir-kit linked an issue Aug 24, 2023 that may be closed by this pull request
@yamacir-kit
Copy link
Collaborator Author

TODO: When promoting SIGINT to SIGKILL, kill the process group instead of the ros2 launch process.

@yamacir-kit
Copy link
Collaborator Author

TODO: When promoting SIGINT to SIGKILL, kill the process group instead of the ros2 launch process.

Done.

@yamacir-kit yamacir-kit requested a review from HansRobo February 6, 2024 04:42
@yamacir-kit yamacir-kit marked this pull request as ready for review February 6, 2024 04:43
@yamacir-kit yamacir-kit merged commit b842a1a into master Feb 8, 2024
8 checks passed
@yamacir-kit yamacir-kit deleted the fix/autoware-shutdown branch February 8, 2024 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

scenario_test_runner seems not killing rviz
2 participants