Re: merging regtests

2011-09-05 Thread Graham Percival
On Mon, Sep 05, 2011 at 11:41:37PM +0200, David Kastrup wrote: > So using a recent enough kernel should get rid of that annoyance. No; although recent kernels have no maximum length of arguments in total, they still impose a maximum length of a *single* argument. And our build system puts all the

Re: merging regtests

2011-09-05 Thread Reinhold Kainhofer
On Mo.,  5. Sep. 2011 23:41:37 CEST, David Kastrup wrote: > So using a recent enough kernel should get rid of that annoyance. I'm using 2.6.38-11 on ubuntu and I could reproduce the problem... Cheers, Reinhold ___ lilypond-devel mailing list lilypond

Re: merging regtests

2011-09-05 Thread David Kastrup
Reinhold Kainhofer writes: > Am Montag, 5. September 2011, 23:09:14 schrieb Janek Warchoł: >> May i ask for a very short explanation of what was wrong? Were there >> too many regtest files in the directory and this made it impossible to >> compile them, and therefore check them? > > The makefile

Re: merging regtests

2011-09-05 Thread Janek Warchoł
2011/9/5 Reinhold Kainhofer : > Am Montag, 5. September 2011, 23:09:14 schrieb Janek Warchoł: >> May i ask for a very short explanation of what was wrong?  Were there >> too many regtest files in the directory and this made it impossible to >> compile them, and therefore check them? > > The makefil

Re: merging regtests

2011-09-05 Thread Reinhold Kainhofer
Am Montag, 5. September 2011, 23:09:14 schrieb Janek Warchoł: > May i ask for a very short explanation of what was wrong? Were there > too many regtest files in the directory and this made it impossible to > compile them, and therefore check them? The makefile in input/regression/ collects all re

Re: merging regtests

2011-09-05 Thread Janek Warchoł
2011/8/30 Graham Percival : > We haven't had a release in a month.  More to the point, we > haven't had a regtest comparison in a month.  But we've had lots > of patches go in. > > I will bet money that we have at least 3 regressions.  I will also > bet money that at least 1 of them is from a devel

Re: merging regtests

2011-09-04 Thread Graham Percival
On Sun, Sep 04, 2011 at 01:15:15AM +0200, Reinhold Kainhofer wrote: > Am Tuesday, 30. August 2011, 07:39:06 schrieb Graham Percival: > > This abomination was pushed as > > a330f10f9fdf00408598031f4b2cb691039b2c92 > > Can we revert this regtest merge again, now that the build should work in > that

Re: merging regtests

2011-09-03 Thread Reinhold Kainhofer
Am Tuesday, 30. August 2011, 07:39:06 schrieb Graham Percival: > On Tue, Aug 30, 2011 at 06:25:44AM +0100, Graham Percival wrote: > > As a temporary workaround, I will now reduce the number of > > regression tests. In particular, I will merge the segfault > > regtests -- we don't care about the ou

Re: merging regtests

2011-08-30 Thread Phil Holmes
- Original Message - From: "Graham Percival" To: Sent: Tuesday, August 30, 2011 8:10 AM Subject: Re: merging regtests On Tue, Aug 30, 2011 at 06:39:06AM +0100, Graham Percival wrote: On Tue, Aug 30, 2011 at 06:25:44AM +0100, Graham Percival wrote: > As a temporary

Re: merging regtests

2011-08-30 Thread Graham Percival
bad27 d8aeaf1879b7ded03c3f96803e4f8419a8cf64ed c28c0c9f5d43b32e77ee060288e5006ee6be8b5b GUB is now compiling the docs, so the current crisis is over. I estimate that this has "bought us" another 1-2 weeks. At that point, we'll be back to the non-release situation again. I tried to make sure I was

Re: merging regtests

2011-08-29 Thread Graham Percival
On Tue, Aug 30, 2011 at 06:25:44AM +0100, Graham Percival wrote: > As a temporary workaround, I will now reduce the number of > regression tests. In particular, I will merge the segfault > regtests -- we don't care about the output of those; we just want > to make sure that lilypond doesn't crash.

merging regtests

2011-08-29 Thread Graham Percival
We haven't had a release in a month. More to the point, we haven't had a regtest comparison in a month. But we've had lots of patches go in. I will bet money that we have at least 3 regressions. I will also bet money that at least 1 of them is from a developer who is going on vacation soon. (n