Not going to comment on the aspect of purchasing a machine. But will point out that the real benefit to having dedicated machines is that of having non-traditional setups (OS+toolset). I.e. dedicated machines give you coverage.On Sat, Dec 12, 2015 at 8:08 PM, 'Tom Kent' via Boost Steering Committee <firstname.lastname@example.org> wrote:I also think that, like Niall said, we should move towards CI style testing where every commit is tested, but that is going to be a *huge* transition.I wouldn't say huge.. Maybe "big".I would love to see direction on this in general from the steering committee, and am encouraged that almost all new libraries already have this.I can't speak for the committee. But as testing manager I can say moving Boost to CI is certainly something I work on a fair amount.Retrofitting it onto all the existing libraries will be an undertaking.Working on that. Getting closer and closer.
I would suggest that as an interim step, we update our existing regression facility so that the runners just specify what their configuration is (msvc-12.0, gcc-4.9-cpp14, clang-3.3-arm64-linux, etc) and we have a centralized server that gives them a commit to test (and possibly a specific test to run).Not sure what you mean by that.They would also send their results back to this server (via http post, no more ftp!) in a format (json) that can be immediately displayed on the web without interim processing.It's not actually possible to eliminate the processing. Although it's possible to reduce it to a much shorter time span than what it is now. That processing is what adds structure and statistics that we see now in results. Without it theres considerably less utility in the results. And I can say that because..
Even this kind of intermediate step would be a lot of development for someone....and I don't have time to volunteer for it.I've been working on such a testing reporting system for more than 5 years now. This past year I've been working on it daily. Mind you only being able to devote a very limited amount of time daily. Recently I've been working on processing performance, in trying to get processing of 100 test results to happen in under 3 seconds (running the Google cloud infrastructure).