From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile-ncurses@gnu.org
Cc: 21677@debbugs.gnu.org
Subject: bug#21677: Guile-NCurses test failure when built against NCurses 6.0
Date: Tue, 13 Oct 2015 10:59:20 +0200 [thread overview]
Message-ID: <87a8rnrvo7.fsf@gnu.org> (raw)
In-Reply-To: <87fv1frvvj.fsf@gnu.org>
Hello,
Guile-NCurses 1.6 has one test failure when built against NCurses 6.0:
--8<---------------cut here---------------start------------->8---
================================================
GNU Guile-Ncurses 1.6: test/test-suite.log
================================================
# TOTAL: 71
# PASS: 70
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: curses_034_util
=====================
[?1049h[1;24r[m[4l[?7h[H[2J[6;6Hzzz[H[2J[24;1H[?1049l^[[?1l>UNRESOLVED: util: delay-output
PASS: util: curses-version
PASS: util: unctrl #\bel
PASS: util: unctrl x
PASS: util: unctrl xchar #\bel
PASS: util: unctrl xchar x
PASS: util: keyname #\bel
PASS: util: keyname x
PASS: util: keyname home
FAIL: getwin/putwin: putwin
ERROR: getwin/putwin: getwin - arguments: ((srfi-34 #<condition &curses-wrong-type-arg-error [arg: #f expected-type: window] e7d210>))
--8<---------------cut here---------------end--------------->8---
This was fine with NCurses 5.0.
Any ideas?
(Run ‘guix build guile-ncurses’ with current Guix master to reproduce.)
Thanks in advance!
Ludo’.
next prev parent reply other threads:[~2015-10-13 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:54 bug#21677: Guile-NCurses 1.6 test failure with ncurses 6.0 Ludovic Courtès
2015-10-13 8:59 ` Ludovic Courtès [this message]
2015-10-13 17:03 ` bug#21677: [Bug-guile-ncurses] Guile-NCurses test failure when built against NCurses 6.0 Mike Gran
2015-10-13 17:11 ` Ludovic Courtès
2015-10-13 17:40 ` Mike Gran
2015-10-17 16:50 ` Mike Gran
2015-10-18 10:20 ` Ludovic Courtès
2015-11-03 23:15 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8rnrvo7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21677@debbugs.gnu.org \
--cc=bug-guile-ncurses@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.