On Mon, 2023-04-03 at 14:36 +0200, Alejandro Colomar wrote:
> - Being part of the make targets, it would enable running them in
> parallel, taking around 1/4th the time it takes now.
Up until this morning this could not work because all the tests run in
the same directory and they create tempo
Hi Paul,
On 4/3/23 14:26, Paul Smith wrote:
> On Sun, 2023-04-02 at 18:14 +0200, Alejandro Colomar wrote:
>> I wonder if you could use the Makefile to run the tests, rather
>> than calling a script from a .PHONY target that runs them all the
>> time. Why not run them only once? You can touch emp
On Sun, 2023-04-02 at 18:14 +0200, Alejandro Colomar wrote:
> I wonder if you could use the Makefile to run the tests, rather
> than calling a script from a .PHONY target that runs them all the
> time. Why not run them only once? You can touch empty files
> when a test succeeds to make make(1) ha
On 4/2/23 16:15, Paul Smith wrote:
> On Sun, 2023-04-02 at 16:13 +0200, Alejandro Colomar wrote:
>> I can reproduce it by running `make check`, interrupting it
>> at this specific point, and then running again `make check`
>> (no -j needed):
>
> This is a known limitation with the test suite.
I w
On Sun, 2023-04-02 at 16:13 +0200, Alejandro Colomar wrote:
> I can reproduce it by running `make check`, interrupting it
> at this specific point, and then running again `make check`
> (no -j needed):
This is a known limitation with the test suite.
Hi Paul,
On 4/2/23 16:04, Paul Smith wrote:
> On Sun, 2023-04-02 at 14:52 +0200, Alejandro Colomar wrote:
>> If I build make from source and run the checks in parallel, some
>> fail. Is this expected, or is it a bug in the Makefile?
>
> The test suite is invoked as a single target, so there's no
On Sun, 2023-04-02 at 14:52 +0200, Alejandro Colomar wrote:
> If I build make from source and run the checks in parallel, some
> fail. Is this expected, or is it a bug in the Makefile?
The test suite is invoked as a single target, so there's no way that
enabling parallelism could impact it. Also
