Basic tests vs CoreCLR require catching an exception

[AndyAyersMS]

In the current CoreCLR/CoreFX drops, tests that write to the console will require the jit to generate code that can handle exceptions, unless the current code page is 65001 (my cmd shell defaults to CP 437).

In particular we see a throw from a protected block in System.Text.Encoding.GetEncoding(int32 codePage) with a local catch.

Given that MSILC won't be in a position to generate correct code for catches for a while, we need a workaround -- either set the code page when running the tests, avoid tests that write to the console, get CoreFx to look at whether this behavior is reasonable, or blacklist that method in our jit and allow the production jit to handle it.

[AndyAyersMS]

Opened an issue for CoreCLR guys to look into this.

[AndyAyersMS]

There's a fix coming. Will update this when I know specifically where it shows up.

[AndyAyersMS]

I am pretty sure this is fixed. The fix has been in CoreFX for a while but couldn't make it into the build of the CoreCLR tests until that build was switched over to the new nuget schema.

I'll verify this and then remove the chcp's from our various scripts.

[AndyAyersMS]

I haven't been doing the chcp thing in a long time. Will PR updating the test script not to do it either.