tag:help.appveyor.com,2012-11-13:/discussions/problems/19285-appveyor-build-fails-whereas-local-build-succeedsAppVeyor: Discussion 2019-01-19T20:09:04Ztag:help.appveyor.com,2012-11-13:Comment/468062972019-01-15T18:42:25Z2019-01-15T18:42:25ZAppveyor build fails whereas local build succeeds<div><p>Can you go to last successful build and hit <code>RE-BUILD COMMIT</code> and let us know the result.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/468062972019-01-15T19:23:22Z2019-01-15T19:23:22ZAppveyor build fails whereas local build succeeds<div><p>Same result. Might be something with the env/machine?</p></div>godrosetag:help.appveyor.com,2012-11-13:Comment/468062972019-01-16T16:18:19Z2019-01-16T16:18:19ZAppveyor build fails whereas local build succeeds<div><p>I can't see anything obvious that could be causing this. The builds look exactly the same but some UI tests are now failing.</p>
<p>Can you try switching to <code>Previous Visual Studio 2017</code> image for one build and see if the result is the same.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/468062972019-01-17T13:09:51Z2019-01-17T13:09:51ZAppveyor build fails whereas local build succeeds<div><p>Unable to use it<br>
<a href="https://ci.appveyor.com/project/LogoFX/samples-specifications/builds/21690039">https://ci.appveyor.com/project/LogoFX/samples-specifications/build...</a></p></div>godrosetag:help.appveyor.com,2012-11-13:Comment/468062972019-01-18T18:43:42Z2019-01-18T18:43:42ZAppveyor build fails whereas local build succeeds<div><p>It must be a problem of resource usage that is coming close to some boundary that causes failure.</p>
<p>I forked your repo and tried some builds with <code>APPVEYOR_BUILD_WORKER_CLOUD: GCE</code> set as an environment variable so that the build runs on our Google compute engine build worker cloud, which has slightly more performant machines and the build succeeded.</p>
<p>You could try the same and/or try running your tests with parallelism disabled. See <strong>Changing Default Behaviour</strong> <a href="https://xunit.github.io/docs/running-tests-in-parallel">here</a></p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/468062972019-01-19T20:02:36Z2019-01-19T20:02:36ZAppveyor build fails whereas local build succeeds<div><blockquote>
<p>It must be a problem of resource usage that is coming close to some boundary that causes failure.</p>
</blockquote>
<p>Could be yet the usage hasn't changed since the last working commit so it's highly unlikely</p>
<blockquote>
<p>I forked your repo and tried some builds with APPVEYOR_BUILD_WORKER_CLOUD: GCE set as an environment variable so that the build runs on our Google compute engine build worker cloud, which has slightly more performant machines and the build succeeded.</p>
</blockquote>
<p>Ok, I will try this approach</p>
<blockquote>
<p>You could try the same and/or try running your tests with parallelism disabled. See Changing Default Behaviour</p>
</blockquote>
<p>This suite doesn't run in parallel. It can't run in parallel - the tests are all E2E with single instance app which is started and stopped for every test/scenario. Again it's highly unlikely that this is the root cause in this case.</p></div>godrosetag:help.appveyor.com,2012-11-13:Comment/468062972019-01-19T20:09:04Z2019-01-19T20:09:04ZAppveyor build fails whereas local build succeeds<div><p>GCE approach was successful.<br>
Can this approach be used as permanent one or is it just a temporary measure?</p></div>godrose