From: Tomas Volf <~@wolfsden.cz>
To: 72365@debbugs.gnu.org
Subject: bug#72365: srfi-64: test-on-bad-end-name-simple is not allowed to raise an exception
Date: Tue, 30 Jul 2024 21:51:53 +0200 [thread overview]
Message-ID: <ZqlEWVHOKQWg6j-m@ws> (raw)
Hello,
I think I found a bug in (srfi srfi-64) module shipped with GNU Guile.
The specification says the following about the simple test runner:
> Creates a new simple test-runner, that prints errors and a summary on the
> standard output port.
It does not mention that it can signal errors, so I believe the following should
just print to the terminal:
(use-modules (srfi srfi-64))
(test-on-bad-end-name-simple (test-runner-null) "x" "y")
However is signals an error instead:
Backtrace:
In ice-9/boot-9.scm:
1752:10 6 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _)
In unknown file:
5 (apply-smob/0 #<thunk 7f6cf05a9300>)
In ice-9/boot-9.scm:
724:2 4 (call-with-prompt ("prompt") #<procedure 7f6cf05b6280 at ice-9/eval.scm:330:…> …)
In ice-9/eval.scm:
619:8 3 (_ #(#(#<directory (guile-user) 7f6cf05acc80>)))
In ice-9/boot-9.scm:
2836:4 2 (save-module-excursion #<procedure 7f6cf059d300 at ice-9/boot-9.scm:4393:3 ()>)
4388:12 1 (_)
In srfi/srfi-64/testing.scm:
375:14 0 (test-on-bad-end-name-simple _ _ _)
srfi/srfi-64/testing.scm:375:14: In procedure test-on-bad-end-name-simple:
test-end x does not match test-begin y
Have a nice day
Tomas Volf
next reply other threads:[~2024-07-30 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 19:51 Tomas Volf [this message]
2024-09-30 13:24 ` bug#72365: srfi-64: test-on-bad-end-name-simple is not allowed to raise an exception Taylan Kammer
2024-10-02 12:28 ` Tomas Volf
2024-10-02 21:07 ` Taylan Kammer
2024-10-02 22:17 ` Tomas Volf
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZqlEWVHOKQWg6j-m@ws \
--to=~@wolfsden.cz \
--cc=72365@debbugs.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).