When running tests, the check_clang_tidy script encodes the output string, making it hard to read when debugging checks. This removes the .encode() call.
Test Plan:
Making a new default check for testing (as of right now, it includes a failing test):
[~/llvm-project/clang-tools-extra] python3 clang-tidy/add_new_check.py bugprone example <...>
Pre-changes:
[~/llvm-project/build] ninja check-clang-tools <...> ------------------------ clang-tidy output ----------------------- b"1 warning generated.\n/data/users/nvankempen/llvm-project/build/Debug/tools/clang/tools/extra/test/clang-tidy/checkers/Output/bugprone-example.cpp.tmp.cpp:4:6: warning: function 'f' is insufficiently awesome [bugprone-example]\nvoid f();\n ^\n/data/users/nvankempen/llvm-project/build/Debug/tools/clang/tools/extra/test/clang-tidy/checkers/Output/bugprone-example.cpp.tmp.cpp:4:6: note: insert 'awesome'\nvoid f();\n ^\n awesome_\n" ------------------------------------------------------------------ <...>
Post-changes:
[~/llvm-project/build] ninja check-clang-tools <...> ------------------------ clang-tidy output ----------------------- 1 warning generated. /data/users/nvankempen/llvm-project/build/Debug/tools/clang/tools/extra/test/clang-tidy/checkers/Output/bugprone-example.cpp.tmp.cpp:4:6: warning: function 'f' is insufficiently awesome [bugprone-example] void f(); ^ /data/users/nvankempen/llvm-project/build/Debug/tools/clang/tools/extra/test/clang-tidy/checkers/Output/bugprone-example.cpp.tmp.cpp:4:6: note: insert 'awesome' void f(); ^ awesome_ ------------------------------------------------------------------ <...>