-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix the Rest of the Windows Driver Tests #23116
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
Conversation
@swift-ci please test |
This looks great to me, the only thing that stands out is the use of |
Build failed |
Fixed the pylint import order issue. |
Passing -fansi-escape-codes doesn't do anything on non Windows platforms, on Unix, clang calls
On Windows, it toggles using ANSI instead of SetConsoleMode. The actual choice to emit them is a different option. |
Oh, yeah, we shouldn't use |
@swift-ci please test and merge |
Fair to say that |
@swift-ci please test macOS platform |
Build failed |
@@ -716,6 +716,8 @@ addCommonInvocationArguments(std::vector<std::string> &invocationArgStrs, | |||
invocationArgStrs.push_back(importerOpts.IndexStorePath); | |||
} | |||
|
|||
invocationArgStrs.push_back("-fansi-escape-codes"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be conditionalized on DiagnosticOptions::UseColor, no? Or will it just not use the escape codes if they never come up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly, if color is emitted, it'll use ansi escapes instead of SetConsoleMode, but it doesn't actually trigger the use of color.
This (along with #23040) makes driver tests now pass on Windows: