tag:help.appveyor.com,2012-11-13:/discussions/problems/17301-stochastic-failure-on-python-34-and-35-buildsAppVeyor: Discussion 2018-12-15T21:00:19Ztag:help.appveyor.com,2012-11-13:Comment/462036462018-10-05T21:30:38Z2018-10-05T21:30:38ZStochastic failure on Python 3.4 and 3.5 builds<div><p>There have been <a href="https://www.appveyor.com/updates/">several platform updates</a> since June 8th. Perhaps you can start looking through them to guess at any changes that might be affecting your build.</p>
<p>Also, can you try simplifying your matrix to problematic jobs and then add <code>appveyor_build_worker_cloud: gce</code> to your environment variables. I enabled this different build worker cloud, which has higher spec VMs, on your account in case we're dealing with a threading/resource issue.</p>
<p>Note, though that these workers take a little longer time to be provisioned so your builds will lag a bit at the beginning.</p>
<p>Run some tests like this and let us know how it goes.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/462036462018-10-06T11:58:50Z2018-10-06T11:58:50ZStochastic failure on Python 3.4 and 3.5 builds<div><p>Thanks for the response. I added the environment variable (just to be sure, it wasn't supposed to be all-caps?), and the errors exhibited again in Python 3.5: <a href="https://ci.appveyor.com/project/nipy/nibabel/build/1.0.521">https://ci.appveyor.com/project/nipy/nibabel/build/1.0.521</a></p>
<p>I looked through the updates, and didn't see any relevant changes to Python 3.4 and 3.5 in the time frame. There was an update to 3.5.4 in the preceding month, so that's possible, but no updates to Python 3.4 since 2017. I'll have a more detailed look through when I have time.</p></div>Chris Markiewicztag:help.appveyor.com,2012-11-13:Comment/462036462018-10-08T15:17:16Z2018-10-08T15:17:16ZStochastic failure on Python 3.4 and 3.5 builds<div><p>Ah, and just to be clear, here's the branch we're using to test. I've bumped some empty commits to re-run a few times. It seems less likely to fail but not resolved by using GCE.</p>
<p><a href="https://github.com/nipy/nibabel/pull/676">https://github.com/nipy/nibabel/pull/676</a></p></div>Chris Markiewicztag:help.appveyor.com,2012-11-13:Comment/462036462018-10-13T01:55:36Z2018-10-13T01:55:36ZStochastic failure on Python 3.4 and 3.5 builds<div><p>Sorry for the delay in responding.</p>
<p>Given that some of the comments at numpy suggest a threading issue, it seems a good one to rule out. The GCE build workers don't actually provide any more cores than the standard workers.</p>
<p>I could enable our new premium Quad VM's on your account just for the purpose of testing the result on stability of your builds.</p>
<p>This is a paid option and we can not provide it free outside of a short testing window (1 or 2 days), but at least it will make it clear whether or not we are dealing with a threading issue.</p>
<p>Let me know if and when you are ready to test this option.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/462036462018-10-15T14:03:07Z2018-10-15T14:03:07ZStochastic failure on Python 3.4 and 3.5 builds<div><p>Hi, just a quick note: I won't be able to devote concerted effort to this, this week. I'll see if I can carve out some time next week.</p></div>Chris Markiewicztag:help.appveyor.com,2012-11-13:Comment/462036462018-10-15T14:14:32Z2018-10-15T14:14:32ZStochastic failure on Python 3.4 and 3.5 builds<div><p>Ok. We'll wait for news from you.</p></div>Owen McDonnell