Windows compilation flow produces wrong check files

[soronpo]

When a check file is generated on a Windows platform, it will mismatch the eventual check done on a Linux machine (like the CI process):

• The Windows check file ends lines with CRLF whereas the Linux ends with just LF (workaround is to manually run dos2unix on the check file).
• The Windows check file uses backslash for paths instead of forward slash (e.g. \neg\ instead of /neg/).

The check file generation should be more explicit when generating the outputs and ignore the underlying platform it runs on.

[michelou]

In principle I fully agree but can you be more specific on the affected check files ?

Note : In my case I generate many Scala 3 distros on Windows (Snapshot builds) several times in a week and the current errors are listed on the page OPENJDK.md.

[michelou]

Ok, I've just seen one example with your fix 6d7c825.

[soronpo]

I generate many Scala 3 distros on Windows (Snapshot builds) several times in a week and the current errors are listed on the page OPENJDK.md.

I think I know where the gap is. It's not that the tests don't work on my machine. They do. But when I change the compiler/tests and a new check.out file is generated so I can use it as a new .check file, then that file is wrong as I described above.