From: Ricardo Wurmus <rekado@elephly.net>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: gwl-devel@gnu.org
Subject: Re: [PATCH v2] tests/examples: Add running of workflow examples
Date: Fri, 03 Jun 2022 17:46:10 +0200 [thread overview]
Message-ID: <874k117ns7.fsf@elephly.net> (raw)
In-Reply-To: <87v8thao3c.fsf@laura>
Olivier Dion <olivier.dion@polymtl.ca> writes:
> What about skipping the group instead of running the tests?
>
> (when (getenv "GWL_SKIP_INTEGRATION_TESTS")
> (test-skip "full-examples"))
>
> (test-group "full-examples"
> (test-example "simple.scm")
> (test-example "simple-wisp.w")
> ;; ...
> )
That would work, too. I’d apply a patch to that effect :)
--
Ricardo
prev parent reply other threads:[~2022-06-03 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 17:55 [PATCH] tests/examples: Add running of workflow examples Olivier Dion
2022-04-29 20:32 ` Ricardo Wurmus
2022-04-29 21:05 ` Olivier Dion via
2022-05-07 6:46 ` Ricardo Wurmus
2022-05-07 16:47 ` [PATCH v2] " Olivier Dion
2022-06-03 9:06 ` Ricardo Wurmus
2022-06-03 13:11 ` Olivier Dion via
2022-06-03 15:46 ` Ricardo Wurmus [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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k117ns7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).