appveyor treats job as failed even though nosetests succeeded

[FelixSchwarz]

I used this demo app to get started with appveyor. Builds seem to work (nosetests succeeds to run the test, xunit xml was uploaded) but I still see a red bar on the left in the appveyor web ui. Also the job is marked as "failed" (e.g. failure notification via email).

I assume this comes from nosetests' output on stderr:

copying build\lib.win32-2.7\pyappveyordemo\extension.pyd -> pyappveyordemo
python.exe : .
At line:2 char:1
+ &$env:PYTHON\python setup.py nosetests --with-xunit
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
----------------------------------------------------------------------
Ran 1 test in 0.031s
OK
Command executed with exception: ----------------------------------------------------------------------
Ran 1 test in 0.031s
OK
# this uploads nosetests.xml produced in test_script step
$wc = New-Object 'System.Net.WebClient'

I there anything we can do about this? I like nosetests for my projects so that is fine but I hope there is a way to tell appveyor that stderr output is fine if the exit code is 0.

[FelixSchwarz]

As far as I know this (treating a job as failed if there is output on STDERR) is a powershell "feature". My workaround right now is to replace the ps call in test_script with:

 - "python setup.py nosetests --with-xunit"