ci: set no color output during build#51653
Draft
dsanders11 wants to merge 1 commit into
Draft
Conversation
dsanders11
added
target/42-x-y
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of Change
At some point in the past week something changed (either Chromium roll or GitHub Actions change) and now macOS and Linux are defaulting to color output from clang during the build. This breaks the problem matcher we have for clang output since now there are ANSI escape characters in the raw output. Fix is to just disable color output explicitly during the build.
Checklist
Release Notes
Notes: none