On 2010-06-08 at 09:43 -0400, John Jetmore wrote:
> I have another new error in the test suite. I looked at the checkins
> for appendfile.c and didn't see an obvious culprit, but having not
> done the work and having done it last night when I was sleepy, I may
> have missed the obvious.
>
> Test 5007
>
> paniclog (which is suppoed to be empty):
> 2010-06-08 08:34:56 1OLyxE-00007l-Gt == userx@??? R=r1 T=t1 defer
> (-1): quota value 3221225472 is too large (overflow) in t1 transport
>
> mainlog (note that the diff is opposite of what I would expect, the
> "-" lines are the actual output, the "+" lines are the expected
> output):
> --- test-mainlog-munged 2010-06-08 08:41:27.000000000 -0500
> +++ log/5007 2006-02-10 10:29:20.000000000 -0600
> @@ -1,2 +1,3 @@
> 1999-03-02 09:44:33 10HmaX-0005vi-00 <= CALLER@??? U=CALLER P=local S=sss
> -1999-03-02 09:44:33 10HmaX-0005vi-00 == userx@??? R=r1 T=t1 defer
> (-1): quota value 3221225472 is too large (overflow) in t1 transport
> +1999-03-02 09:44:33 10HmaX-0005vi-00 => userx <userx@???> R=r1 T=t1
> +1999-03-02 09:44:33 10HmaX-0005vi-00 Completed
>
> Phil, does this leap out at you from any changes?
No.
So, the problem appears to be that a 3G quota is exceeding the quota
size limit for Exim. So, unexpectedly: sizeof(off_t) <= 4
What does { exim -bV } report as the size of off_t in the test
environment?
Per ChangeLog for 4.61, PH/21 & PH/22, the panic is expected and the
tests should not be invoked unless off_t is reported to be large enough.
The closest I've come to touching this is cleanup in the format strings
for reporting the sizes, in buildconfig.c. I haven't done anything that
would affect the system off_t size, which is what is explicitly being
used in src/transports/appendfile.c.
Something strange in $PATH where the version of Exim being asked for its
size isn't the version invoked for the test? Sorry, I really don't know
the test suite.
-Phil
