Bruno Haible wrote:
> Hi Eric, Jim,
>
>> >> This ensures that long-running tests are executed last. So that the user
>> >> gets the maximum of information as quickly as possible.
>> >
>> > That goes counter to the idea of parallel execution, where you want the
>> > long-running tests front-loaded s
Hi Bruno,
* Bruno Haible wrote on Sat, Apr 03, 2010 at 12:13:12AM CEST:
> - I was assuming a sequential execution (since this is the default with
> "make") and the goal of maximizing the information that is available
> within a short time after starting the test.
Your goal is worthy but
Hi Eric, Jim,
> >> This ensures that long-running tests are executed last. So that the user
> >> gets the maximum of information as quickly as possible.
> >
> > That goes counter to the idea of parallel execution, where you want the
> > long-running tests front-loaded so that the shorter tests can
Eric Blake wrote:
> On 04/02/2010 12:08 PM, Bruno Haible wrote:
>> This ensures that long-running tests are executed last. So that the user
>> gets the maximum of information as quickly as possible.
>
> That goes counter to the idea of parallel execution, where you want the
> long-running tests fro
On 04/02/2010 12:08 PM, Bruno Haible wrote:
> This ensures that long-running tests are executed last. So that the user
> gets the maximum of information as quickly as possible.
That goes counter to the idea of parallel execution, where you want the
long-running tests front-loaded so that the short
This ensures that long-running tests are executed last. So that the user
gets the maximum of information as quickly as possible.
2010-04-02 Bruno Haible
gnulib-tool: Ensure that long-running tests are executed last.
* gnulib-tool (func_emit_tests_Makefile_am): Emit the code
