The trick here is the difference between being on Windows and being on Unix. Generally speaking, Git is configured to use native line endings, so in the repo, all files are stored with Unix line endings ("\n"), but on Windows, the local copy would have a Windows new line ending ("\r\n"). Inside the test in question, we try to split things into lines using only the Unix line ending ("\n"), so everything works as expected on Unix machines. However, on Windows, you’re left with that pesky carriage return ("\r") that can be seen at the very end of the text of the “Expected” message in the error @gcliff reported.
1 Like