Re: [Nmh-workers] Call for testing of nmh 1.7 release candidate 3

[Kevin Cosgrove]

On 26 August 2017 at 11:28, Ralph Corderoy <address@hidden> wrote:

> Hi Kevin,
> 
> > - To: address@hidden
> > - From: address@hidden
> > - Subject: mhfixmsg pass through on parse error
> > - MIME-Version: 1.0
> > - Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
> > - 
> > - ------- =_aaaaaaaaaa0
> > - Content-Type: text/plain; charset="iso-8859-1
> > - Content-Disposition: attachment; filename="test1.txt"
> > - Content-Transfer-Encoding: quoted-printable
> > - 
> > - This is the=
> > -  text/plain part.
> > - 
> > - ------- =_aaaaaaaaaa0--
> ...
> > ./test/mhfixmsg/test-mhfixmsg: test failed, outputs are in
> > /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/Mail/inbox/31
> > and
> > /home/local/src/INCOMING/BUILD/nmh-1.7-RC3/test/testdir/test-mhfixmsg32378.actual.
> > first named test failure: pass through message with relative folder
> > path with parse error
> > FAIL: test/mhfixmsg/test-mhfixmsg
> 
> Can you arrange to do a similar test but with strace?  Extract that
> 15-line email above into your current nmh folder.
> 
>     sed '1,/unable to parse message 31/d' test/mhfixmsg/test-mhfixmsg |
>     sed -n '1,/^cat/d; /^EOF$/q; p' >`mhpath new`
> 
> Running the local mhfixmsg that the test script uses should produce an
> empty output file based on how the test failed.
> 
>     uip/mhfixmsg last -outfile /tmp/out   # Is /tmp/out zero bytes long?
> 
> If so, re-run, but under strace(1).
> 
>     strace -o /tmp/st -e desc uip/mhfixmsg last -outfile /tmp/out
> 
> And send us /tmp/st.  You might want to peruse for secrets first.


Yes, I'll have a look at that.  But, I'm booked now until Wednesday.

--
Kevin