On 1/31/17 7:22 PM, Rene Rivera wrote:
If someone is interested in an optimization challenge here's your opportunity. Currently the program(s) that generate the test results take a long time to run. In both the live setup of a 4 core 16 GB ram VM it takes about 40 minutes to generate the reports for master and develop branches. On my 4 core 16 GB ram real hardware SSD HD machine it also takes about 40 minutes.
Assuming that the 40 min includes building all libraries and tests and running the tests, that doesn't seem to be all that long as far as I'm concerned. Here at home I use b2 and library_status to incrementally and run build tests for one library. (usually but not always the serialization library, naturally). It takes couple of minutes for a complete build on my more or less modern desktop - Mac mini with 256GB SSD and 4 cores. I don't think that's a major problem. When I'm working on fixing problems, most of the build/test cycles are incremental so in practice it's not problem at all. FWIW I use XCode project generated from CMake for debugging and b2 to check with gcc compilers before I checkin. Both seem to take a similar amount of time. Robert Ramey