Remote Execution: Don't ignore stdout and stderr
Open
enhancement
remote execution
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/797)
In GitLab by [[Gitlab user @juergbi]](https://gitlab.com/juergbi) on Nov 29, 2018, 17:58
The remote execution client currently ignores `stdout` and `stderr` in the `ActionResult`.
Contributor guide
Research direction
Start by locating the remote execution client and the handling of stdout and stderr in the ActionResult. Trace how the result is consumed and identify the existing tests for remote execution. Done means the client's behavior no longer ignores both output streams and the relevant tests verify it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100