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
Tom,
I’m not certain who we’d contact, but I suppose sup...@travis-ci.com is the place to start.
I’m willing to contact them on behalf of the project (although I think it would be better if you did this because you know more of what we need).
What can you tell me about our OS X resources/requirements/quota or resources/requirements/quota generally that I should know before contacting them? Do we have an account name/number/identifier of some type?
Jon
--
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 boost-steerin...@googlegroups.com.
To post to this group, send email to boost-s...@googlegroups.com.
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/CAArKS8gEiuYw1OUBkFRf3MD6DVkg7GufZR_jpBCgvfLXS8Q6WQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Louis,
Sorry that I didn’t see this message until just now.
Please do.
Jon
From: Boost Steering Committee <boost-s...@googlegroups.com> on behalf of Louis Dionne <ldio...@gmail.com>
Reply-To: Boost Steering Committee <boost-s...@googlegroups.com>
Date: Friday, November 10, 2017 at 8:27 PM
To: Boost Steering Committee <boost-s...@googlegroups.com>
Subject: [boost-steering] Re: [boost] PSA: Travis OS X bottleneck, <cxxstd> new Boost.Build feature
John,
--
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 boost-steerin...@googlegroups.com.
To post to this group, send email to boost-s...@googlegroups.com.
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.
In this light, I think it makes more sense to ask Boost users
who are using Boost on Mac OS to contribute hardware resources
for CI testing.
On Wed, Nov 29, 2017 at 3:10 AM, Boris Kolpackov <bo...@codesynthesis.com> wrote:
In this light, I think it makes more sense to ask Boost users
who are using Boost on Mac OS to contribute hardware resources
for CI testing.I think this is a great idea. There is already some Mac OS runners in the testing matrix, but they don't seem to execute that often. Maybe someone who is a Mac user could volunteer to set one up and the steering committee can fund a Mac mini for them?