On Thu, 05 Dec 2013 19:07:50 -0500, David Levine said:
> More generally: if the test suite ("make check") passes, I'd
> have very high confidence that the checkout will work well.
Speaking of which, I just did a 'git pull', and now 'make check'
throws this interesting error:
PASS: test/mhbuild/test-header-encode
PASS: test/mhbuild/test-utf8-body
*** /home/valdis/src/nmh/test/testdir/test-mhfixmsg85284.expected
2013-12-06 17:57:01.941062052 -0500
--- /home/valdis/src/nmh/test/testdir/test-mhfixmsg85284.actual 2013-12-06
17:57:02.009061727 -0500
***************
*** 9,15 ****
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 8bit
! Need to go! Need ... to ... go!
------=_nmh-multipart
Content-Type: text/html; charset="Windows-1252"
--- 9,15 ----
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 8bit
! Need to go! Need ... to ... go!
------=_nmh-multipart
Content-Type: text/html; charset="Windows-1252"
./test/mhfixmsg/test-mhfixmsg: test failed, outputs are in
/home/valdis/src/nmh/test/testdir/test-mhfixmsg85284.expected and
/home/valdis/src/nmh/test/testdir/test-mhfixmsg85284.actual.
FAIL: test/mhfixmsg/test-mhfixmsg
PASS: test/mhlist/test-mhlist
I have zero clue why mhfixmsg is apparently adding 2 leading blanks to the line.
_______________________________________________
Nmh-workers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/nmh-workers
