[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is
From: |
Kevin Cosgrove |
Subject: |
Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available |
Date: |
Sun, 06 May 2012 18:38:46 -0700 |
On 6 May 2012 at 19:19, Ken Hornstein <address@hidden>wrote:
> >On Mandriva 2007.0 I gett these errors from 'make check'.
>
> So, looking at those errors ...
>
> >FAIL: test/bad-input/test-header
>
> That _MIGHT_ be because you have a terminal wider than 80 characters; is
> that true? Obviously we should fix that. Actually, if you want to try
> fixing that yourself ... in test/bad-input/test-header, change:
>
> scan $msgnum > $actual 2>&1
>
> to
>
> scan -width 80 $msgnum > $actual 2>&1
I made sure that my window is 78 characters and reran the test. Now
I get:
FAIL: test/bad-input/test-header
FAIL: test/format/test-myhost
FAIL: test/format/test-mymbox
FAIL: test/inc/test-deb359167
4 of 46 tests failed
I used to only fail two test. The new failures are test-my*
Of course, I changed a lot of stuff in ~/Mail/.components and a bit
of stuff in ~/.mh_profile in order to try to make other things work.
I did make nmh work from command-line and from within exmh (with
Ken's help) but I must've done something with a 'make check' side
effect.
I backed out the one change in ~/.mh_profile
There are a number of one line changes in ~/Mail/.components/* all of
them being the addition of "From: %(localmbox)".
Oh, the other change is that nmh older than 1.5 was installed during
the first 'make check'. Then I installed nmh 1.5 RC2, after which I
came back to do the 80 character test. Is it possible for 'make
check' to use things outside the build tree? If so, that has changed.
> >FAIL: test/inc/test-deb359167
>
> Looking at this ...
>
> >==24349== Syscall param socketcall.send(msg) points to uninitialised byte(s)
> >==24349== at 0x41106A1: send (in /lib/i686/libc-2.4.so)
> >==24349== by 0x41401F6: (within /lib/i686/libc-2.4.so)
> >==24349== by 0x413E0D3: (within /lib/i686/libc-2.4.so)
> >==24349== by 0x413E3F7: (within /lib/i686/libc-2.4.so)
> >==24349== by 0x40D05F6: getpwuid_r (in /lib/i686/libc-2.4.so)
> >==24349== by 0x40CFEE7: getpwuid (in /lib/i686/libc-2.4.so)
> >==24349== by 0x8056000: getuserinfo (mts.c:368)
> >==24349== by 0x8056160: getusername (mts.c:308)
> >==24349== by 0x8059A4B: ismymbox (addrsbr.c:331)
> >==24349== by 0x80520DF: do_name (fmt_compile.c:507)
> >==24349== by 0x8052708: do_func (fmt_compile.c:564)
> >==24349== by 0x805249D: do_if (fmt_compile.c:713)
> >==24349== Address 0xBEE62F43 is on thread 1's stack
> >FAIL: test/inc/test-deb359167
>
> It looks like valgrind is complaining about something deep within the C
> library, specifically getpwuid(). I don't think this is our fault.
No problem. Thanks for looking!
--
Kevin
Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Kevin Cosgrove, 2012/05/06
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Ken Hornstein, 2012/05/06
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Ken Hornstein, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Kevin Cosgrove, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Ken Hornstein, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Kevin Cosgrove, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Ken Hornstein, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Ralph Corderoy, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Ken Hornstein, 2012/05/07
- Re: [Nmh-workers] [exmh-workers] Second release candidate for nmh 1.5 is now available, Kevin Cosgrove, 2012/05/07