From: "Ludovic Courtès" <ludo@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Problems with the test suite
Date: Mon, 05 Oct 2020 14:30:44 +0200 [thread overview]
Message-ID: <87tuv8zwgb.fsf@gnu.org> (raw)
In-Reply-To: <6b4b14a2-2b85-f9b6-7125-285244dfac9e@gmail.com> (Jesse Gibbons's message of "Fri, 25 Sep 2020 15:51:52 -0600")
Hi,
Jesse Gibbons <jgibbons2357@gmail.com> skribis:
> I'm still working on making 43193 ready to apply. I added a test, and
> it looks like my to the build script --with-source option broke
> something. I am getting error messages, but I don't know where in the
> code they are occurring. Is there any way I can get a stack trace when
> errors are raised during tests? I also noticed nearly all of the tests
> assert multiple things simultaneously, compounded by the `and`
> function. When one of those things is found to be false, the test
> fails, but I don't know which part of the assertion is false.
Could you show exactly the output you’re getting?
SRFI-64 ‘test-assert’ & co. report exceptions but they don’t show you
the backtrace. The trick you can use to see the exception is to “lift”
your test expression outside ‘test-assert’:
(test-assert "test my stuff
(begin my code …))
=>
(begin my code …)
> Are there any advantages to using Guix's custom testing API over other
> testing APIs like SRFI-64? If not, why not transition the test suite
> to use one of them?
Guix uses plain SRFI-64.
HTH,
Ludo’.
prev parent reply other threads:[~2020-10-05 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 21:51 Problems with the test suite Jesse Gibbons
2020-10-05 12:30 ` Ludovic Courtès [this message]
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=87tuv8zwgb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jgibbons2357@gmail.com \
/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.