-
Notifications
You must be signed in to change notification settings - Fork 312
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 spawner behaviour on failing controller activation or deactivation (backport #1941) #1968
Conversation
Cherry-pick of 038a05f has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
8a2df81
to
c740c9c
Compare
dbae78c
to
046e8b9
Compare
#1941) --------- Co-authored-by: Christoph Fröhlich <[email protected]>
046e8b9
to
75fc53a
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## humble #1968 +/- ##
==========================================
- Coverage 62.92% 62.87% -0.06%
==========================================
Files 109 109
Lines 12504 12589 +85
Branches 8481 8547 +66
==========================================
+ Hits 7868 7915 +47
- Misses 852 858 +6
- Partials 3784 3816 +32
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Thx for fixing!
Before the fix proposed in this PR, the spawner reports the controller activation as successful, if the activation is failed at the last stage after calling activate_controllers. This PR addresses the issue by proposing a fix and this should now properly fail at the spawner end as well
Before the fix:
With the proposed fix:
This is an automatic backport of pull request #1941 done by [Mergify](https://mergify.com).