-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
[DO NOT MERGE]: posix shutdown investigation/hacks #11525
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's all good.
And the unit tests don't stall anymore for me locally.
I don't understand the
|
The path seems to be wrong now. |
px4_daemon::Pxh::stop(); | ||
_exit_requested = true; | ||
|
||
px4_systemreset(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dagar , did you want this to be px4_system_reset
?
I did a quick test because I though it might fix #11027 but doesn't but it looks like a start. |
It's intended as a start. There's a lot more to do. |
What's the relation to unit tests failing with the new px4 work queue? #11261