Re: [Boost-testing] Test results processing transition..

Subject: Re: [Boost-testing] Test results processing transition..
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2015-01-15 13:33:00

I added some basic time tracking to the script and here's what I see when
doing a clean run followed by a second run:

=====-----=====-----=====-----=====-----=====-----
Thu Jan 15 11:14:28 CST 2015 :: Start of testing. [build_all]
Thu Jan 15 11:14:28 CST 2015 :: Get tools. [build_setup]
Thu Jan 15 11:14:28 CST 2015 :: Git; boost_root [build_setup]
Thu Jan 15 11:21:07 CST 2015 :: Git; boost_regression [build_setup]
Thu Jan 15 11:21:08 CST 2015 :: Git; boost_bb [build_setup]
Thu Jan 15 11:21:10 CST 2015 :: Build tools. [update_tools]
Thu Jan 15 11:23:14 CST 2015 :: Build results for branch develop.
[build_results]
Thu Jan 15 11:34:39 CST 2015 :: Build results for branch master.
[build_results]
Thu Jan 15 11:42:31 CST 2015 :: Upload results for branch develop.
[upload_results]
=====-----=====-----=====-----=====-----=====-----
Thu Jan 15 11:43:11 CST 2015 :: Start of testing. [build_all]
Thu Jan 15 11:43:11 CST 2015 :: Get tools. [build_setup]
Thu Jan 15 11:43:11 CST 2015 :: Git; boost_root [build_setup]
Thu Jan 15 11:44:34 CST 2015 :: Git; boost_regression [build_setup]
Thu Jan 15 11:44:34 CST 2015 :: Git; boost_bb [build_setup]
Thu Jan 15 11:44:36 CST 2015 :: Build tools. [update_tools]
Thu Jan 15 11:45:33 CST 2015 :: Build results for branch develop.
[build_results]
Thu Jan 15 11:51:35 CST 2015 :: Build results for branch master.
[build_results]
Thu Jan 15 11:55:59 CST 2015 :: Upload results for branch develop.
[upload_results]

They stop at upload as I avoided doing the actual upload. So it's..

First run (total) ~28.0 min
Second run (total) ~13.0 min

First run (git) ~6.5 min
Second run (git) ~1.5 min

First run (build_results) ~19.0 min
Second run (build_results) 10.5 min

Hence, the core of building the results is most of the time. But there's
still some considerable overhead. I did notice that the result build tool
is compiled every time for some reason. And it's not supposed to be :-( As
for the core result building.. From eyeing it, it seems the slow part is
the XML reading. And then there's git.. We could probably reduce that time
by only getting selected portions of Boost (enough to build the tools).

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail