Re: Anything more for 2.3.0?
Raphael Geissert <geissert@debian.org> writes:
> I wonder if we shouldn't setup a daily cronjob somewhere that runs the
> whole testsuite if any change was committed since the last run,
> reporting any failure to the mailing list.
> This should of course not be used as an excuse to not to run the
> testsuite. The problem is that nowadays it takes too long to run the
> whole testsuite to be feasible to run it all after every change. I do
> of course run the related tests I find, but there's always the
> possibility of missing something.
> What do you and the others think?
I use runtests onlyrun=<case> or, increasingly, check-tag tag=<case>, and
then run the whole test suite usually after I've just finished a batch of
changes. That seems to work okay, and I don't really mind it. We could
do something on lintian.d.o and mail the output to the list if other
people would find it useful, though. Hm, assuming that lintian.d.o has
all the packages installed required to make the test suite work. Ah, and
lintian.d.o is an amd64 system, so we have the problem with testing
non-PIC code in shared libraries.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: