I first noticed this issue when I saw that the clippy check in a proprietary NZXTCorp repo was failing, but with no items shown in the generated report.
While this PR is active I will keep my clippy-check-windows-lf-failures repo open as an MRE, so that I can demonstrate the breakage and fix proposed here via failed public repo checks. For convenience, the interesting files of the repo are inlined below:
Currently, running
clippy-check
on awindows-latest
runner will fail to generate any report items because NodeJS'os.EOL
is set to CRLF line endings (which thestdline
listener in@actions/exec
uses for line buffering), andclippy
only emits LF line endings.Fix this by using the
stdout
listener instead with a modified version of@action/exec
's line-buffering algorithm that only uses LF line endings.I first noticed this issue when I saw that the
clippy
check in a proprietary NZXTCorp repo was failing, but with no items shown in the generated report.While this PR is active I will keep my
clippy-check-windows-lf-failures
repo open as an MRE, so that I can demonstrate the breakage and fix proposed here via failed public repo checks. For convenience, the interesting files of the repo are inlined below: