20 Sep
2017
20 Sep
'17
4:20 p.m.
On 20/09/2017 15:45, Peter Dimov via Boost wrote:
Ion Gaztañaga wrote:
Shouldn't the hole boost repo be tested when a library changes?
This isn't feasible as CI jobs have a time limit of 49 minutes on Travis, which is sometimes insufficient for testing even a single library.
I think this is the problem with this approach: any non-trivial library will quickly run out of time on the CI servers, some of which are rather slow. Certainly Math and Multiprecision libraries had to be split into multiple jobs to get through CI testing. I'm sure there are many others with similar issues. Best, John. --- This email has been checked for viruses by AVG. http://www.avg.com