You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today if you launch a process in the background from script with the way works, it ends up hanging the test because the process is not put to the background.
Solution Description
Either added a new primitive to start a process in the background, or maybe a better option is to add a flag to script allow forking a process to the background.
Alternatives
No response
Additional Context
No response
Slack discussion
No response
Research
I have searched other issues in this repository and mine is not recorded.
The text was updated successfully, but these errors were encountered:
For testing I build my operator with coverage so I can merge my chainsaw test code coverage with my unit test code coverage. Tell now I just run the operator in background before running the chainsaw tests, but I need to test migration code between versions of the operator, so I want to be able to in middle of the chainsaw test kill the old and start a new version of the operator binary to trigger the migration code, and also capture the code coverage stats. There are ways around this but way more involved.
Problem Statement
Today if you launch a process in the background from script with the way works, it ends up hanging the test because the process is not put to the background.
Solution Description
Either added a new primitive to start a process in the background, or maybe a better option is to add a flag to script allow forking a process to the background.
Alternatives
No response
Additional Context
No response
Slack discussion
No response
Research
The text was updated successfully, but these errors were encountered: