Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update from origin #1
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
Uh oh!
There was an error while loading. Please reload this page.
Update from origin #1
Changes from 1 commit
d68f263ce371a6fbb4b3acf80430dd2d739f726c3157fb51f2f5ef3de193daf027db9045a1ba6036fb33a807b5c0bbef40337dc6809ec51944d7c07fdded21e51722cb6d1345758c55edd66f34e843c030f26618400fa2043ca2627d49fd41dce6ab696079531c598c530a1875f42c692727efc55167919e23302d2f5c3308c9b40b8786d3f506daa1b7c4fbab95335ed48cffc8b1d9697fa266477a13da3accd79bca9e7c59b32c1fc3d92643c928498df336010090083b45ec704656acc3202b9512b619f2ff7256d37dd31bd7de3d5ef0b9ac6417702967d6ba5321ac46e14383bb1e5fc83d1e497d6b1c65dfc8570fcebf4d590209a2f3ae3a0299c5f61954041dc52ae9fd58036f04ea39a90fd90eaf2896ba22f591f93314b5ea96e5f2b42f7b1fe1916a8681e0a86ac897f6114fb66220729c3e45b5f80188f841056f092a79595de9cea8dbee8355b00ace64a011b308e8954746dd6091f502e83f808c10588bfe797c61d78b914d83f8c4c8d4be084f4a8899b614ead9f90b539c1880863d088e07f161e02b64732ca77618129d65306c02ffe53ec5afbfe96056abe9ef18bcdf75b01bafc4ee5d1ed486f037b4887ba2d2aa9a090857331597771f189a45e17c4149300100b998f51f3a38cd0ae92e6298481812e84965f988f61f460b795266acb3fd82b91f472be334d8e2d5b65745e4b5e0b38c4e4a4f0e8870c314ccfc8a204a98e232076d1db85edeb7fff93641cb9925f1c83ed217642edc899ebb3ebb2af758d55d64092c13218f8009a2baa69736b8daefb3d32b36701fdb6d5e7763626bc79e1c011fb312402f9ec026b073e6e76d60981e92448c940b7017517461fe19f142b9909a8e0129e314c7a19bc12ec05887f5ec9d0b42a17dced2e7a733ba6bca1829ba44772b7090e4068c5f0f0cdabfa9d2c6c43a5cd0c3d3c892f0c28281cc3c53c5ec619680b5d2ef58ab598a71e0e326e3c4f48f8db4470692f63395d1ef4405fe31e52d9a4b75a1304ef90b28445e5435563eb675cf40966f6d93a7d9490e7a12791cdc7b8640558169cd5dc3b174f1405117a3fc2549636716d75176cfb89e46048aae841afbb7d3a3bffbf8fecd22e9a78953fece8dcb8aea6dcdbd62bc85fa035eec1e67df7a8f99fbfbd489c9134b6b6b294b836e9d6351797c24830d3309442364e4984015dbb62aaa76e84c034caa5f9ac6da793f048334ea0c30362219File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
The mock process runner used in most of the tests had poor handling of stdout/stderr: - By default it would return the `List<int>` output from the mock process, which was never correct since the parent process runner interface always sets encodings, thus the `dynamic` should always be of type `String` - The process for setting output on a `MockProcess` was awkward, since it was based on a `Stream<Lint<int>>`, even though in every case what we actually want to do is just set the full output to a string. - A hack was at some point added (presumably due to the above issues) to bypass that flow at the process runner level, and instead return a `String` set there. That meant there were two ways of setting output (one of which that only worked for one of the ways of running processes) - That hack wasn't updated when the ability to return multiple mock processes instead of a single global mock process was added, so the API was even more confusing, and there was no way to set different output for different processes. This changes the test APIs so that: - `MockProcess` takes stdout and stderr as strings, and internally manages converting them to a `Stream<List<int>>`. - `RecordingProcessRunner` correctly decodes and returns the output streams when constructing a process result. It also removes the resultStdout and resultStderr hacks, as well as the legacy `processToReturn` API, and converts all uses to the new structure, which is both simpler to use, and clearly associates output with specific processes.Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.