tag:help.appveyor.com,2012-11-13:/discussions/problems/10297-memory-allocation-errors-on-32-bit-instancesAppVeyor: Discussion 2018-08-25T02:25:32Ztag:help.appveyor.com,2012-11-13:Comment/442373242017-12-06T18:42:02Z2017-12-06T18:42:02ZMemory allocation errors on 32 bit instances<div><p>Maybe you could look at <a href="https://www.appveyor.com/docs/parallel-testing/">parallel testing</a>. It is actually different builds (on different VMs), very similar to the <a href="https://www.appveyor.com/docs/build-configuration/#build-matrix">build matrix</a>. For free accounts it will run sequentially, but you will get full isolation between groups of tests.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/442373242017-12-06T20:20:17Z2017-12-06T20:20:17ZMemory allocation errors on 32 bit instances<div><p>Thanks Ilya, I'll have a look at those.</p>
<p>In the meantime, is there an easy way to specify that the test_script<br>
section should only be ran for some members of the build matrix?</p></div>jonathan.underwoodtag:help.appveyor.com,2012-11-13:Comment/442373242017-12-06T21:03:02Z2017-12-06T21:03:02ZMemory allocation errors on 32 bit instances<div><p>I think I just answered that <a href="https://help.appveyor.com/discussions/questions/14397-how-to-run-test_script-only-for-certain-membersjobs-of-build-matrix">here</a> but you can play with environment variables any way you want. For example you can check for specific values of that variable, and do it inside `build.cmd, it is up to you.</p></div>Ilya Finkelshteyn