Reduce noise in community build logs #11068
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This permits test output from munit to be controlled by the LogLevel setting of sbt.
smarter
approved these changes
Jan 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use the sbt logger for the munit test framework, bringing it in line with others such as scalatest and scalacheck.
This means that output from munit-based tests will be affected by the sbt
logLevelsetting for the community build (currently set toLevel.Error):https://github.com/lampepfl/dotty/blob/0f1d350a3b521b80759ddf4307977c5193756493/community-build/src/scala/dotty/communitybuild/projects.scala#L155
In particular, several projects in
community_build_bhave munit test suites that generate a tremendous amount of output at "info" level, which will now be filtered out by the above setting.Extracted from #10731