Python test failures under windows now report the exit code

[david-seiler]

Description

While working on PR-14617, I hit an obscure Windows-only crash. Adding the $LastExitCode to the error message helped me debug it; a hex-formatted version of that change appears here.

Checklist

Essentials

• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• The only changes are on the error paths for ci/windows/test_*.ps1, so the PR doesn't test all that well. In the first version I've deliberately broken test_py2_gpu.ps1 (see line 27), so we should see that test fail and report an exit code of 0x0. Assuming that behaves as expected, I'll amend the PR to make it pass.

Comments

• No rush to merge this, I just promised Marco I'd give it its own PR.

[piyushghai]

@david-seiler Thanks for your contributions. Could you look into the CI failure on windows-gpu ?

@mxnet-label-bot Add [pr-awaiting-review, Test]

[david-seiler]

@david-seiler Thanks for your contributions. Could you look into the CI failure on windows-gpu ?

@mxnet-label-bot Add [pr-awaiting-review, Test]

That was the planned failure described in the section under test coverage. My change only touches error paths, so I wanted to prove that the Throw() did the right thing. That worked as expected, you can see the result here:

http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/windows-gpu/branches/PR-15147/runs/2/nodes/115/steps/186/log/?start=0

The latest version should be good to merge; we'll see in an hour or so.