POC for better metrics gathering from build_runner #371
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.
Proof of concept form jam work Feb 2022. We would like to be able to get some more information out of build_runner and how long things take. At a minimum, we'd like to be able to get the information that is printed to stdout. However, it's hard to capture that without disrupting the nice terminal display of the build progress. This is a POC of that.
The way build_runner works is that the executable does almost nothing but cause generation of the build script, and then execute that script. And the API call to generate the script takes a function that generates it. So we can make a very stripped-down version of that executable, and invoke that instead of the build_runner. It can generate its own build script, which it does by taking the regular build script and injecting a log listener that writes to a file. Then we can read that file back and we have the log information.
test
command.