[src/trunk]: src/tests/lib/libcurses/tests tests/libcurses: "fix" test mvwin

[rillig <rillig%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/e35ae477ee8f
branches:  trunk
changeset: 952337:e35ae477ee8f
user:      rillig <rillig%NetBSD.org@localhost>
date:      Sat Feb 13 08:37:21 2021 +0000

description:
tests/libcurses: "fix" test mvwin

The test mvwin previously expected an endless stream of bytes, by
comparing the actual output with /dev/zero.  This didn't make sense as
the curses output does not contain '\0' in any of the test cases.

Compare with /dev/null instead.  This is as wrong as before, but the
curses test framework currently ignores this situation, as for many
other test cases.  See the numerous "Excess" messages in atf-run.log.

diffstat:

 tests/lib/libcurses/tests/mvwin |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (19 lines):

diff -r 81f789fddd0e -r e35ae477ee8f tests/lib/libcurses/tests/mvwin
--- a/tests/lib/libcurses/tests/mvwin   Sat Feb 13 08:26:12 2021 +0000
+++ b/tests/lib/libcurses/tests/mvwin   Sat Feb 13 08:37:21 2021 +0000
@@ -2,11 +2,11 @@
 call OK wmove $win1 1 1
 call OK wprintw $win1 "%s" "xxxx"
 call OK wrefresh $win1
-compare /dev/zero
+compare /dev/null
 call OK refresh
-compare /dev/zero
+compare /dev/null
 call OK mvwin $win1 4 7
 call OK wrefresh $win1
-compare /dev/zero
+compare /dev/null
 call OK refresh
-compare /dev/zero
+compare /dev/null