[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nmh-workers] mhshow/test-charset failures in nmh-1.7 (`Can't convert ?u
From: |
Leonardo Taccari |
Subject: |
[Nmh-workers] mhshow/test-charset failures in nmh-1.7 (`Can't convert ?us-ascii to UTF-8') |
Date: |
Mon, 20 Nov 2017 15:01:10 +0100 |
Dear nmh community,
first of all thank you very much for working and releasing nmh-1.7!
In the process of updating mail/nmh package in pkgsrc I've rerun
the tests (as I've done periodically for the three 1.7 RCs) and with
nmh-1.7 I have found this - maybe - new test failure (this is on
a not-so-current NetBSD-current amd64 8.99.1, not sure if that
matter though, it's the same version where I have run the previous
test for 1.7 RCs):
*** .../test/testdir/21398.expected Mon Nov 20 13:27:20 2017
--- .../test/testdir/21398.actual Mon Nov 20 13:27:20 2017
***************
*** 3,6 ****
--- 3,8 ----
MIME-Version: 1.0
+ mhshow: Can't convert ?us-ascii to UTF-8
+ mhshow: unable to convert character set from ?us-ascii, continuing...
[ part - text/plain - 0B ]
./test/mhshow/test-charset: test failed, outputs are in
.../test/testdir/21398.expected and .../test/testdir/21398.actual.
first named test failure: replacement character in parameter value
FAIL: test/mhshow/test-charset
It seems that the unexpected output `+ mhshow: ...' are printed to the
stderr but also ends up in the `*.actual' file.
Is this (accidentally) expected, should I try to investigate if I
have some weird local configuration that is picked up (that's
probable! :)) or, can you reproduce it as well?
For completeness I will attach also the 21398.{expected,actual}
files but I'm pretty happy to help debugging/testing possible patch
so feel free to contact me if you can't reproduce that!
Thank you for the attention and thanks again for nmh-1.7!
21398.actual
Description: 21398.actual
21398.expected
Description: 21398.expected
- [Nmh-workers] mhshow/test-charset failures in nmh-1.7 (`Can't convert ?us-ascii to UTF-8'),
Leonardo Taccari <=