Boost Testing :
Subject: Re: [Boost-testing] GCC runners failing (and stopping)
From: Tom Kent (lists_at_[hidden])
Date: 2014-07-02 22:18:04
On Wed, Jul 2, 2014 at 8:55 PM, Tom Kent <lists_at_[hidden]> wrote:
> Both of my linux-development runners (teeks99-03, teeks99-04) are locking
> up during their runs.
> Here's the end of the output:
> # Using bjam binary in
> # Getting test case results out of
> boost_root: /home/tomkent/teeks99-03/a/boost_root
> locate_root: /home/tomkent/teeks99-03/a/results
> *****Warning - missing test path: boost-test(RUN) "timer/inspect"
> ["always_show_run_output"] :
> (Usually occurs when bjam doesn't know how to make a target)
> At this point, the everything has stopped and the run doesn't progress (or
> timeout!), so it blocks the next runner from starting.
> Any ideas?
Update, I'm also seeing it on windows, but the build doesn't keep going
after that. It *immediately* starts processing the logs.
*****Warning - missing test path: boost-test(RUN) "timer/inspect"
(Usually occurs when bjam doesn't know how to make a target)
# Collecting test logs into