Skip to content

Conversation

statementreply
Copy link
Contributor

Fixes #981.

This PR tries to decode output from test commands as UTF-8 first, and then as the active code page encoding if the output is not valid UTF-8.

I'm trying both encodings because cl outputs in the active code page, but cl /BE outputs in UTF-8 🙄. This is enough to fix the test issue at least on the machine where I encountered #981.

@statementreply statementreply requested a review from a team as a code owner August 21, 2021 07:54
@StephanTLavavej StephanTLavavej added the test Related to test code label Aug 21, 2021
@StephanTLavavej StephanTLavavej self-assigned this Aug 26, 2021
@StephanTLavavej
Copy link
Member

I'm mirroring this to an MSVC-internal PR. Please notify me if any further changes are pushed.

@StephanTLavavej StephanTLavavej merged commit a7d9019 into microsoft:main Aug 27, 2021
@StephanTLavavej
Copy link
Member

Thanks for fixing this test harness bug! ✔️ 🐞 😻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Related to test code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tests: Tests could return UNRESOLVED on non-English Windows set to non UTF-8 encoding
3 participants