Rene Rivera wrote:
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.
Took about an hour each for me: Wed Feb 1 19:45:38 GTBST 2017 :: Start of testing. [build_all] Wed Feb 1 19:45:38 GTBST 2017 :: Get tools. [build_setup] Wed Feb 1 19:45:38 GTBST 2017 :: Git; boost_root [build_setup] Wed Feb 1 19:47:09 GTBST 2017 :: Git; boost_regression [build_setup] Wed Feb 1 19:47:10 GTBST 2017 :: Git; boost_bb [build_setup] Wed Feb 1 19:47:12 GTBST 2017 :: Build tools. [update_tools] Wed Feb 1 19:50:50 GTBST 2017 :: Build results for branch develop. [build_results] Wed Feb 1 20:54:41 GTBST 2017 :: Build results for branch master. [build_results] Wed Feb 1 21:49:00 GTBST 2017 :: Upload results for branch develop. [upload_results] Wed Feb 1 21:49:00 GTBST 2017 :: Upload results for branch master. [upload_results] Wed Feb 1 21:49:00 GTBST 2017 :: End of testing. [build_all] but this is not a full run, because the programs started failing with "basic_ios::clear" once develop.zip and master.zip reached 2 GB in size. This occurs at Reading /cygdrive/d/tmp2/boost-reports/develop/incoming/develop/processed/teeks99-02-dg4.5-Docker-64on64.xml Merging expected results Generating links pages basic_ios::clear on develop and at Reading /cygdrive/d/tmp2/boost-reports/master/incoming/master/processed/teeks99-02-mg4.5-Docker-64on64.xml Merging expected results Generating links pages basic_ios::clear on master. FWIW. :-)