From: Joshua Branson <jbranso@dismail.de>
To: "Jonathan McHugh" <indieterminacy@libre.brussels>
Cc: "Andy Tai" <atai@atai.org>, help-guix@gnu.org
Subject: Re: building but skipping tests?
Date: Tue, 21 Sep 2021 15:31:58 -0400 [thread overview]
Message-ID: <87v92tn2s1.fsf@dismail.de> (raw)
In-Reply-To: <e0cacea2f11409ec8b12de830346c749@libre.brussels> (Jonathan McHugh's message of "Tue, 21 Sep 2021 07:35:46 +0000")
"Jonathan McHugh" <indieterminacy@libre.brussels> writes:
> Hi Joshua,
>
> Is there any published guidance covering what test responses are considered as flagging up?
>
> For instance, would problems be sent to bug-guix@gnu.org as a matter of principle? And what should and should not be included?
https://guix.gnu.org/manual/en/html_node/Tracking-Bugs-and-Patches.html
There's no hard fast rule about what should or should not be sent. If
it feels like a bug, go ahead and submit it.
It's typically good to put the output of "guix describe" and "guix
system describe" and what hardware you are using when describing a bug.
:)
>
> Kind regards,
>
> ====================
> Jonathan McHugh
> indieterminacy@libre.brussels
>
> September 21, 2021 8:46 AM, "Joshua Branson" <jbranso@dismail.de> wrote:
>
>> Andy Tai <atai@atai.org> writes:
>>
>>> Hi, if I try to install a package and that may trigger building a
>>> number of dependencies (when no substitutes for some reason but that
>>> is outside the concern of this question), I notice that since the
>>> build processes would run the tests by default, that takes a lot of
>>> time. I wonder if it is possible to skip tests when building
>>> locally? Of course running tests are good but if I am not a
>>> developer of the packages being built running the tests may not be of
>>> much utility to me.
>>
>> Note that you can disable the tests. BUT enabling said tests, lets you
>> find errors, which you can report, which is really valuable to guix
>> developers. :)
>>
>>> Thanks for the info on this.
>>
>> --
>> Joshua Branson (jab in #guix)
>> Sent from Emacs and Gnus
>> https://gnucode.me
>> https://video.hardlimit.com/accounts/joshua_branson/video-channels
>> https://propernaming.org
>> "You can have whatever you want, as long as you help
>> enough other people get what they want." - Zig Ziglar
>
--
Joshua Branson (jab in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
prev parent reply other threads:[~2021-09-21 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 23:31 building but skipping tests? Andy Tai
2021-08-08 8:20 ` Guillaume Le Vaillant
2021-09-21 6:46 ` Joshua Branson
2021-09-21 7:35 ` Jonathan McHugh
2021-09-21 19:31 ` Joshua Branson [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v92tn2s1.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=atai@atai.org \
--cc=help-guix@gnu.org \
--cc=indieterminacy@libre.brussels \
/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).