Re: [Rdkit-devel] travis build timeouts

I tried using ninja for the builds in stead of make, after an evening of not building I successfully had two builds: https://travis-ci.org/bp-kelley/rdkit/builds/242399233 Commit: https://github.com/bp-kelley/rdkit/blob/baac00bc1eb7f66413011aed239413fe74da3388/.travis.yml Note that the default

Re: [Rdkit-devel] travis build timeouts

On Tue, Jun 13, 2017 at 3:24 PM, Brian Kelley wrote: > I'm unsure if that staging will help, aren't the builds and tests already > done in parallel effectively? > Kind of. There are currently two jobs that run in parallel: - job 1: build the core library, the python 2.7

Re: [Rdkit-devel] travis build timeouts

Given that the current variability is almost a factor of two I don't think smaller changes are going to help. What I'm likely going to try is doing staged builds: - stage 1: build and test core library - stage 2a: build and test python 2.7 wrappers - stage 2b: build and test python 3.5 wrappers -

[Rdkit-devel] travis build timeouts

Dear all, We're getting more and more timeouts with RDKit builds on travis. I'm reasonably sure that this is due to some variability in the performance of the VMs that the builds end up running on. A good demonstration of that is this particular build (on a branch where I'm playing with