Re: PSA: Travis OS X bottleneck, <cxxstd> new Boost.Build feature
On 11/29/17 1:10 AM, Boris Kolpackov 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.
This is the right idea. Let's go the full monte and take it to it's
a) Encourage users to run tests on the libraries they use by making
testing more user friendly.
b) Create a CMake or CMake-like dashboard where users can more or less
automagically post their results to a common database. Presumable boost
regression.py does something similar already.
c) Create a program to permit display of this giant "data cube"
according to the needs of the user/developer.
My personal contribution to moving in this direction can be found at
a) recent tests on all platforms actually being used regardless of how
b) an easily browsable data base of test results.
c) less dependency on centralized CI testing resources
d) less pressure on boost testers
e) more people participating and being a member of the boost community -
helping to promote the "Boost Brand (c)"
f) Since Appveyor, Travis, regression.py, and individual users would be
posting all results to a common database, we'd be decoupling test
results presentation from any particular testing platform.
g) Should CMake solution every get accepted, it could easily be adjusted
to post the the database as well.