Re: [Nmh-workers] Announcing the second release candidate of nmh 1.7.1

[Andy Bradford]

Thus said Ken Hornstein on Mon, 22 Jan 2018 14:20:32 -0500:

> This is a  patch release for 1.7, and fixes  some output problems with
> the format engine, issues with rcvdist(1) passing switches to post(8),
> and a number of problems discovered with the test suite.

Speaking of the test suite, I ran  it (on OpenBSD 6.1) and encountered a
failure I don't recall seeing previously:

first named test failure: replacement character in parameter value
FAIL: test/mhshow/test-charset
...
=======================================
2 of 104 tests failed
(8 tests were not run)
Please report to address@hidden
=======================================

I'm not sure why it failed,  and while reading through test/common.sh, I
saw the following:

#### If you're reading this .... you can set MH_TEST_NOCLEANUP to prevent
#### the test suite from cleaning up the results of a test run, if you need
#### to do manual debugging on a test.


So I then ran:

env MH_TEST_NOCLEANUP=1 make check

And got a whopping 34 failures... not  sure if that's expected or not. 2
of the test cases asked me interactively for Disposition of a message (I
opted for replace because I didn't know one way or the other).

=======================================
34 of 104 tests failed
(8 tests were not run)
Please report to address@hidden
=======================================


So, then I decided to run it a third time, again without the environment
variable and  got 4 failures (2  more than before without  the variable)
among which:

inc: field name 
"ThisHeaderFieldNameIsWaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaayTooLong"
 exceeds 997 bytes
??Format error (message 12) in component 5
inc: m_getfld() called with bogus state of -2
FAIL: test/folder/test-packf

And

inc: field name 
"ThisHeaderFieldNameIsWaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaayTooLong"
 exceeds 997 bytes
??Format error (message 24) in component 5
inc: m_getfld() called with bogus state of -2'
FAIL: test/inc/test-inc-scanout

Maybe  the environment  variable  to  not clean  up  corrupted the  test
environment and  I need  some way  to clean  it up?  I can  rerun ``make
check'' multiple  times and get  a consistent 2  failures, but if  I use
that environment  variable it  then hits 34  failures, and  then without
again 4.

Also, how do I check just a single test?

Thanks,

Andy
-- 
TAI64 timestamp: 400000005a66dde6