Louis,

 

Sorry that I didn’t see this message until just now.

 

Please do.

 

Jon

 

From: Boost Steering Committee <[email protected]> on behalf of 
Louis Dionne <[email protected]>
Reply-To: Boost Steering Committee <[email protected]>
Date: Friday, November 10, 2017 at 8:27 PM
To: Boost Steering Committee <[email protected]>
Subject: [boost-steering] Re: [boost] PSA: Travis OS X bottleneck, <cxxstd> new 
Boost.Build feature

 

John,

 

If that's okay with you, I'd like to contact Travis on behalf of the Steering 
Committee asking them to increase our limits as an open source organization 
(for free). Our Travis queue is incredibly backed up and it's very crippling 
for developers.

 

Louis


On Friday, October 27, 2017 at 11:04:59 AM UTC-6, Tom Kent wrote:

It seems like this would be a great instance where the steering committee could 
allocate some of the organization's funds to directly improve the 
infrastructure being used by our team. I believe that we could upgrade our 
Travis account to a paid one for a couple hundred a month to get more build 
resources. 

 

They also claim on https://travis-ci.org/ that:

> Testing your open source project is 10000% free

> Seriously. Always. We like to think of it as our way of giving back to a 
> community that gives us so much as well.

 

Maybe we just need to have someone on the project contact them and get our free 
quota raised? 

 

Tom

 

 

On Thu, Oct 26, 2017 at 11:43 AM, Peter Dimov via Boost <[email protected]> 
wrote:

Travis's OS X resources for open source projects seem to be insufficient, so OS 
X jobs are very slow and seem to be falling further and further behind. 
Therefore, library authors are encouraged to keep the OS X jobs to the minimum 
necessary. Spawning many OS X jobs takes hours (~25 minutes waiting time per 
job at a quick estimate).

On a not entirely unrelated note, Rene Rivera has added a new feature <cxxstd> 
to Boost.Build that controls the C++ standard in use. So for instance, instead 
of the old

   b2 libs/mylib/test toolset=gcc cxxflags=-std=c++11

one can now use

   b2 libs/mylib/test toolset=gcc cxxstd=11

In addition to being more convenient, this also allows several invocations to 
be combined into one:

   b2 libs/mylib/test toolset=clang cxxstd=03,11,14,1z

which can be leveraged to cut down on the number of jobs.

An example of using cxxstd in .travis.yml can be seen here:

https://github.com/boostorg/system/blob/develop/.travis.yml 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

 

-- 
The Boost Steering Committee webpage: 
https://sites.google.com/a/boost.org/steering/
--- 
You received this message because you are subscribed to the Google Groups 
"Boost Steering Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/boost-steering.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/boost-steering/ef0809d2-bb27-4c42-ad36-6fa9b4ea77db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
The Boost Steering Committee webpage: 
https://sites.google.com/a/boost.org/steering/
--- 
You received this message because you are subscribed to the Google Groups 
"Boost Steering Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/boost-steering.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/boost-steering/46A04C7F-0F1A-4890-945B-427BEAA6EE17%40boost.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to