Mangled Output Formatting In Powershell

[martindevans]

Something seems to have gone terribly wrong with the formatting of rustc output to powershell!

As you can see from the image above it seems like rustc has totally lost the plot formatting the first error.

I'm using a surface pro 4, windows 10, powershell. My powershell is not in legacy mode, window is 80 chars wide and buffer is also 80 chars wide. Unfortunately I don't have access to another PC to test this on right now but if you tell me any additional information you'd like I'll try to provide it.

[sfackler]

It looks like output from two rustc processes interleaved. I've seen this before when running cargo test in certain configurations when it tries to build the lib and the test binary at the same time.

[martindevans]

Ahh interesting, is there a quick easy fix?

[sfackler]

I just run cargo build instead of cargo test to fix the errors and then jump back to cargo test.

[jonas-schievink]

I think doing cargo test -j1 will execute rustc in series, so it should work as well

[martindevans]

Cargo build then cargo test seems to be working. Thanks for your help guys.

Merry Christmas 🎅

[retep998]

Unfortunately we let the rustc instances write to the console directly because if they were redirected to pipes colors wouldn't work due to conhost using API calls rather than escape codes for colors.