[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: prepare Automake's test suite for parallelization
From: |
Jim Meyering |
Subject: |
Re: prepare Automake's test suite for parallelization |
Date: |
Sun, 04 Nov 2007 19:25:08 +0100 |
Ralf Wildenhues <address@hidden> wrote:
> FWIW2, we could use subdirectories named after the test name rather than
> using the PID. However, I've found myself running the same test in
> parallel sometimes:
> make check TESTS=foo.test # Stop with C^Z, then run same command again
>
> and it causes weird output if you later `fg' the first `make'. Arguably
> this is PEBCAK. So really if you don't like using the PID, please speak
> up, I'm all open here.
Hi Ralf,
I've considered and rejected both, partly because in some unusual cases
I've had to create directories in directories that are also writable
by others. Instead, I used the mkdtemp script that I recently removed
from coreutils: there, I can now rely on the mktemp binary instead.
Using mkdtemp here is almost certainly overkill here, but who knows...
- prepare Automake's test suite for parallelization, Ralf Wildenhues, 2007/11/04
- Re: prepare Automake's test suite for parallelization,
Jim Meyering <=
- Re: prepare Automake's test suite for parallelization, Benoit SIGOURE, 2007/11/04
- Re: prepare Automake's test suite for parallelization, Ralf Wildenhues, 2007/11/04
- Re: prepare Automake's test suite for parallelization, Ralf Wildenhues, 2007/11/10
- signal handling (was: prepare Automake's test suite for parallelization), Ralf Wildenhues, 2007/11/12
- Re: signal handling, Bob Proulx, 2007/11/12
- Re: signal handling, Ralf Wildenhues, 2007/11/12
- Re: signal handling, Ralf Wildenhues, 2007/11/18