[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new test failures
From: |
Jim Meyering |
Subject: |
Re: new test failures |
Date: |
Fri, 17 Feb 2012 09:59:30 +0100 |
Akim Demaille wrote:
> Le 17 févr. 2012 à 08:53, Jim Meyering a écrit :
>
>> FAIL: examples/calc++/test
>> ==========================
>>
>> --(end of buffer or a NUL)
>> --accepting rule at line 46 ("1")
>> --accepting rule at line 39 ("+")
>> --accepting rule at line 46 ("2")
>> --accepting rule at line 40 ("*")
>> --accepting rule at line 46 ("3")
>> --accepting rule at line 36 ("
>> ")
>> --accepting rule at line 54 ("=")
>
> Thanks for the report. I don't understand it
> at all: it looks like the test suite are
> inverted: this looks like the input of the test
> for mfcalc! Not calc++.
>
> Ah, bummer, both are using "input" as input file
Hi Akim,
Good catch!
This is a good reason to run each test in its own sandbox.
Have you looked at gnulib's init.sh framework?
It creates (and automatically removes upon termination)
a temporary directory for each test. To use it, you add
a line like this at the top of your script:
. "${srcdir=.}/init.sh"; path_prepend_ ../src
where in the above example, ../src specifies a directory
to prepend to your shell's search path, so you don't have to
use long absolute (risky, hard to reproduce) or often-unreadable
relative file names for programs you test.
> name. I guess you ran it -j. Will fix this, thanks
> a lot!
I always run make with -j$N ;-) (N > 1)
> Do you have some buildbot or something on Bison somewhere?
No, I just happened to update/build the last couple days.
> I'm sorry to have face all these failures, I'd be happy to
> monitor such a tool if there is one somewhere available.
No, but for bison, I'll bet the nice folks tending the nixos/hydra
buildbot wouldn't mind adding an entry to their DB.
They've been autobuilding coreutils for a long time:
http://hydra.nixos.org/jobset/gnu/coreutils-master
When I break "./configure && make && make check", it sends me mail.
Oh! I've just looked and see that bison is already there:
http://hydra.nixos.org/jobset/gnu/bison-master
Now, all you need to do is request that a few names (or mailing list
address) be added to its config so that you are notified of state
changes. The address@hidden mailing list is probably a good
place to start.