Re: [Boost-testing] Much longer linux regression run times

Subject: Re: [Boost-testing] Much longer linux regression run times
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2017-03-01 03:08:27

On Tue, Feb 28, 2017 at 8:55 PM, Tom Kent via Boost-Testing <
boost-testing_at_[hidden]> wrote:

>
> I'm not really sure how to trace this down. Is there any way to log the
> time it takes the various libraries to complete their test suites?
>

Not currently. The individual tests can run in parallel. To give you that
number we would have to save the information as part of the regression data
and sum it up as part of the regression reports.

> I'm guessing that will show one library that is using 3+ hours. Although,
> it is possible that a change went in to a higher level library that just
> adds a few seconds to each call and is used across many of the libraries.
>
> Thoughts?
>

Binary search manually? You can limit what tests you run on the command
line by using the "--include-tests" b2 option <
https://github.com/boostorg/boost/blob/develop/status/Jamfile.v2#L18>. So
start off by only running tests for [a-m] or [n-z], then [a-g], and so on.
Until you find the time hog.

Other than that, maybe it's one of the libraries tested on Travis <
https://travis-ci.org/boostorg/boost>. And maybe check the length of those
first if they are long on Travis perhaps they are also long on regular
tests.

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