tag:help.appveyor.com,2012-11-13:/discussions/problems/20963-test-script-with-exit-status-of-1-on-ubuntu-imageAppVeyor: Discussion 2019-07-23T21:01:11Ztag:help.appveyor.com,2012-11-13:Comment/470266802019-03-05T00:27:44Z2019-03-05T00:27:44ZTest script with exit status of 1 on Ubuntu image<div><p>Just double-checked and do not see such behavior. Please provide a link to the specific build and build configuration in YAML format (use <code>Export YAML</code> button if you use UI).</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/470266802019-03-06T05:30:11Z2019-03-06T05:30:11ZTest script with exit status of 1 on Ubuntu image<div><p>Here is a link to a build that I had to manually cancel because of this issue</p>
<p> <a href="https://ci.appveyor.com/project/danielgerlag/workflow-core/builds/22786698">https://ci.appveyor.com/project/danielgerlag/workflow-core/builds/2...</a></p></div>Daniel Gerlagtag:help.appveyor.com,2012-11-13:Comment/470266802019-03-06T20:43:10Z2019-03-06T20:43:34ZTest script with exit status of 1 on Ubuntu image<div><p>I am not sure build stuck because of <code>exit 1</code> command was called (not sure it was called at all). Can you please remove <code>if [ $? -ne 0 ] then exit 1 fi</code> expressions and re-build the same commit?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/470266802019-03-13T03:29:09Z2019-03-13T03:29:09ZTest script with exit status of 1 on Ubuntu image<div><p>If I do that, then a failing test will not cause the script to fail and it will publish artifacts that it should not…. This was the whole reason that I had to add the explicit “exit 1”, which causes it to hang… which is better than not failing at all.</p></div>Daniel Gerlagtag:help.appveyor.com,2012-11-13:Comment/470266802019-03-13T06:21:51Z2019-03-13T06:21:51ZTest script with exit status of 1 on Ubuntu image<div><p>I propose that to see what actually stuck, <code>exit 1</code> command or something else.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/470266802019-03-17T01:46:47Z2019-03-17T01:46:48ZTest script with exit status of 1 on Ubuntu image<div><p>Can you suggest an alterative to AppVeyor that can run .net core tests on a Linux image and doesn’t get stuck or report fails as passes?</p></div>Daniel Gerlagtag:help.appveyor.com,2012-11-13:Comment/470266802019-05-22T08:48:17Z2019-05-22T08:48:18ZTest script with exit status of 1 on Ubuntu image<div><p>Even I have the same issue. Im running ubuntu image with dotnet test. The dotnet test is actually throwing an error but the build is still passing.</p></div>msathyanarayantag:help.appveyor.com,2012-11-13:Comment/470266802019-05-22T23:41:25Z2019-05-22T23:41:25ZTest script with exit status of 1 on Ubuntu image<div><p><strong>@msathyanarayan, @Daniel Gerlag</strong> can you guys please help with a simple repro when failed tests pass? Please see very basic <a href="https://github.com/IlyaFinkelshteyn/UnitTestProject1">repro</a> I created with intentionally failing <a href="https://github.com/IlyaFinkelshteyn/UnitTestProject1/blob/master/UnitTestProject1/UnitTest1.cs#L11">test</a> and it <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/unittestproject1/builds/24743916">fails on all images</a>.</p>
<p>Please feel free to create a PR to this repository so we have a falsely successful build to investigate.</p></div>Ilya Finkelshteyn