But I did not run unit tests locally...
Many unit tests are failing on windows due to line ending differences in error message string compares. Here's one example:

[ RUN ] EnergyPlusFixture.HeatBalanceIntRadExchange_CarrollMRT
C:\ci\runs\clone_branch\tst\EnergyPlus\unit\Fixtures\EnergyPlusFixture.cc(204): error: Expected: expected_string
Which is: " ** Severe ** Geometry not compatible with Carroll MRT Zone Radiant Exchange method.\r\n"
To be equal to: stream_str
Which is: " ** Severe ** Geometry not compatible with Carroll MRT Zone Radiant Exchange method.\n"
C:\ci\runs\clone_branch\tst\EnergyPlus\unit\HeatBalanceIntRadExchange.unit.cc(128): error: Value of: compare_err_stream(error_string, true)
Actual: false
Expected: true

expected_string is constructed with EnergyPlusFixture::delimited_string which is using DataStringGlobals::NL as the default delimiter.

DataStringGlobals::NL is used in main.cc, InputProcessor.cc, EnergyPlusFixture.hh, and IdfParserFixture.hh. And IdfParser.cc is rolling it's own local NL.

@mjwitte All those uses of NL can be changed to the new approach. I just did it in various spots to be consistent with the rest of EnergyPlus previously.

@lefticus Will you be able to address this?

@mjwitte it looks like you are saying there is still a step to be made to fix up the unit tests, is that still the case here?

@Myoldmopar Yes, this still needs more work. See the lastest Windows CI results

OK, I can tackle that cleanup. I built and ran it on Linux but the unit tests run fine. I'll need to build and run on Windows to see it, which isn't a big problem. I'll try to do that soon. Unless @lefticus is already making these changes...

OK, on Windows the unit test suite now passes. I just moved all the failing tests and worker functions to use plain old \n. @mbadams5 if you could bless my changes in f9823b8 that would be great.

@Myoldmopar The changes seem reasonable and the unit tests seem to pass.

@mjwitte do you want to re-run with my fix? It looks like it is good to go to me.

Sorry, missed this ongoing conversation @Myoldmopar the changes you made are inline with similar changes I've had to make as I've updated each output file to being in text mode instead of binary mode.

@Myoldmopar I've re-run with this branch. Output files look good. Converted between idf and epJSON in both directions and the converted files look good. Other than the failed movefile_test on windows this is good to go. I'm assuming that's a random test failure. The test passes locally.

Thanks @lefticus and @mjwitte, merging this in now.