Boost Testing :
Subject: Re: [Boost-testing] BenPope x86_64 runners + runner requirements
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2015-03-21 10:29:55
Le 21/03/15 13:37, Niklas Angare a écrit :
> "Raffi Enficiaud" <raffi.enficiaud_at_[hidden]> wrote:
>> Le 20/03/15 20:55, Rene Rivera a écrit :
>>> So.. I'd rather see those results. For the basic reason that having some
>>> information is better than having none and wasting work.
> I agree with Rene that it's best if failures show quickly and clearly in
> the results table.
>> I haven't had a look to this machinery. But I was thinking of a
>> requirement target that checks, in run.py or in the /status jam files,
>> that the requirements are met before proceeding further the tests.
>> This would save 100% of everything, plus unclutter the dashboard from
>> the noise generated by the runner setup time (+faster feedback for those
>> people in their setup).
> If the results file is still uploaded, as I think it should be, that
> would turn those columns mostly white, right? In what way has the table
> been uncluttered, then?
Yes, the clutter is caused by false negative (in general any erroneous
information caused by the setup of the runners).