Don't filter gradle's stderr anymore #860
Merged
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.
Motivation and Context
When building the project by running
gradlew
, we filter its output onstderr
to omit a specific diagnostic message. This complicated refactorings in the past and also affects upcoming refactorings regardingQ
andsuperspawn
.The reason this code exists is a weak one IMHO. The Visual Studio integration deemed the build to have failed if anything has been output on
stderr
. Thus the aforementioned diagnostic message onstderr
caused successful builds to count as failed ones.IMHO, the current behavior should be removed for various reasons:
stderr
are not uncommon, so the success of the command should be determined from the returnedPromise
or the process' exit code respectivelyprogress
. Butsuperspawn
callsnotify
for everychunk
it receives in adata
event onstderr
. AFAIK it is not guaranteed that these chunks will be individual and complete lines.Description
This PR removes all output filtering in
ProjectBuilder.prototype.build
.Testing
Automated tests still pass.