From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: 69376@debbugs.gnu.org
Subject: [bug#69376] [PATCH go-team] build-system/go: Allow providing additional test flags.
Date: Thu, 07 Mar 2024 22:59:38 +0000 [thread overview]
Message-ID: <87cys54pid.fsf@gmail.com> (raw)
In-Reply-To: <87a5noaot3.fsf@troyfigiel.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Hi Troy,
Thank you for the work!
The patch looks reasonable. Does it allow us to run all available tests
as we discussed in
<https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00128.html>?
One nitpick about this section:
--8<---------------cut here---------------start------------->8---
+;; go test builds a test binary (or multiple binaries), vets the code and then
+;; runs the test binary. Build, test and test binary flags can be provided as
+;; test-flags. See "go help test" and "go help testflag" for more details.
--8<---------------cut here---------------end--------------->8---
It is a good material for documentation section, how about to move it
from this comment and compile a proper documentation note describing
#:test-flags for go-build-system?
Something like this:
--8<---------------cut here---------------start------------->8---
#:test-flags is added. The default is '(). These flags are passed as
arguments to the test command. Note that flags for verbose output is
always enabled on supported backends.
--8<---------------cut here---------------end--------------->8---
Sourced from <https://guix.gnu.org/manual/en/html_node/Build-Systems.html>
WDYT?
--
Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2024-03-07 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 9:06 [bug#69376] [PATCH go-team] build-system/go: Allow providing additional test flags Troy Figiel
2024-02-25 9:23 ` Troy Figiel
2024-03-07 22:59 ` Sharlatan Hellseher [this message]
2024-03-08 9:06 ` Troy Figiel
2024-03-10 19:52 ` Sharlatan Hellseher
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=87cys54pid.fsf@gmail.com \
--to=sharlatanus@gmail.com \
--cc=69376@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.
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.