From: Tomas Volf <~@wolfsden.cz>
To: 72380@debbugs.gnu.org
Subject: bug#72380: srfi-64: test-end does not uninstall runner if on-final was modified
Date: Tue, 30 Jul 2024 21:51:58 +0200 [thread overview]
Message-ID: <ZqlEXoJwUsoCTOzA@ws> (raw)
Hello,
I think I found a bug in (srfi srfi-64) module shipped with GNU Guile.
The specification for test-end says:
> Additionally, if the matching test-begin installed a new test-runner, then the
> test-end will uninstall it, after reporting the accumulated test results in an
> implementation-defined manner.
However in following example it fails to do so:
(use-modules (srfi srfi-64))
(pk (eq? #f (test-runner-current)))
(test-begin "x")
(test-runner-on-final! (test-runner-current) (λ (_) #t))
(test-end)
(pk (eq? #f (test-runner-current)))
Resulting in:
;;; (#t)
%%%% Starting test x (Writing full log to "x.log")
;;; (#f)
I see no provision in the specification that would justify this.
Have a nice day
Tomas Volf
next reply other threads:[~2024-07-30 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 19:51 Tomas Volf [this message]
2024-10-01 22:34 ` bug#72380: srfi-64: test-end does not uninstall runner if on-final was modified Taylan Kammer
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=ZqlEXoJwUsoCTOzA@ws \
--to=~@wolfsden.cz \
--cc=72380@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).