Hi Greg,
On 03/12/2016 13:16, Greg Landrum wrote:
Builds do take a while, but there is *no way* they should be taking 2
hours unless they are running on extremely overloaded hardware. The
travis builds, which include running all the tests, typically take
less than 40 minutes.
yes on my normal
Lest my previous reply be mis-interpreted: I agree that it would be great
if the builds were quicker - I end up needing to do a large number of them
before each release - but I don't see much that can really be done other
than removing a bunch of functionality.
On Sat, Dec 3, 2016 at 8:42 AM,
Builds do take a while, but there is *no way* they should be taking 2 hours
unless they are running on extremely overloaded hardware. The travis
builds, which include running all the tests, typically take less than 40
minutes.
If, for some reason, you do still need to deal with this, I would
On Fri, Dec 2, 2016 at 6:29 PM, Tim Dudgeon wrote:
> But since I've been working with the Release_2016_09_2 release my Docker
> image builds on Docker Hub [1] are timing out as they sometimes exceed
> the 2 hour limit. If I try at a quiet time I can sometimes get them to
>
Of course builds from source are never fast enough, and the RDKit one is
pretty big.
So far I've lived with this and made cups of coffee.
But since I've been working with the Release_2016_09_2 release my Docker
image builds on Docker Hub [1] are timing out as they sometimes exceed
the 2 hour
5 matches
Mail list logo