-
Notifications
You must be signed in to change notification settings - Fork 215
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
Add support for host process stdio. #5056
Conversation
When an application launches a process on the host, it now has the option to attach a bytestring which will be passed on the process' standard input. Additionally, the standard output and error of the process are captured and printed in CCF's log. This makes it a lot easier to monitor and diagnose issues in production.
plietar/host-proc-stdio@66100 aka 20230228.39 vs main ewma over 20 builds from 65395 to 66092 Click to see tablemain
plietar/host-proc-stdio
|
I'm not sure if it really needs be marked as such, since it isn't particularly long to run from what I can tell, but I don't really know what the criteria is. |
if it's less than 30 seconds, please remove that condition. |
If writing as two separate commands, the Python script could read the partial file, leading to a test failure.
Test was marked as LONG_TESTS, meaning it only ran on the Daily CI. It seems to run pretty fast (<10 seconds), so this seems unnecessary.
It's about 10 seconds, so I've changed it |
613dfc4
to
e0f5b1e
Compare
@plietar please add an entry to the changelog if you are going to backport this. Also note the auto-backporting is currently broken due to a restriction put in place on the org that forbids PR creation from GH actions unfortunately. You will need to run the backport CLI. |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
1 similar comment
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 9461128) # ------------------------ >8 ------------------------ # Do not modify or remove the line above. # Everything below it will be ignored. # # Conflicts: # .daily_canary # CHANGELOG.md
When an application launches a process on the host, it now has the option to attach a bytestring which will be passed on the process' standard input.
Additionally, the standard output and error of the process are captured and printed in CCF's log. This makes it a lot easier to monitor and diagnose issues in production.