I would expect that this breakage is due to the CRLF issues; Finally formalise our defacto line-ending policy by ldrumm · Pull Request #86318 · llvm/llvm-project · GitHub caused files to be checked out with CRLF newlines on Windows. This was soon reverted, but the changes to .gitattributes only take effect when files are checked out again. I.e. the changes apply immediately if you do a new clone, but if updating a new workdir, the incorrect newlines linger around until there’s an actual change to one of those files.
@boomanaiden154-1 How much pain and effort would it be to restart the cluster or otherwise force it to re-checkout all files?
There’s some effort ongoing to try to fix up the issues in the individual tests - that works somewhat for issues in LLVM (where there was a handful of tests failing), but within Clang, the number of failing tests is much bigger, so I’m not sure if we reasonably can patch forward there. (See e.g. [llvm-rc] Handle Windows line endings in tag-html test by dpaoliello · Pull Request #113000 · llvm/llvm-project · GitHub and [gitattributes] Mark some llvm-rc inputs as requiring LF newlines by mstorsjo · Pull Request #113222 · llvm/llvm-project · GitHub for efforts around this.)