unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Csepp <raingloom@riseup.net>
To: Timothy Washington <twashing@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Howto disable unit test runs, when building custom Python packages
Date: Sun, 02 Jul 2023 11:21:15 +0200	[thread overview]
Message-ID: <87sfa6hdla.fsf@riseup.net> (raw)
In-Reply-To: <CAADtM-ZmJd2CUjDJuMBAgmigTOwANkty6+QDH_3LvSBP1ZF8sA@mail.gmail.com>


Timothy Washington <twashing@gmail.com> writes:

> I'm trying to figure out "Howto disable unit test runs, when building
> custom Python packages".
> I am trying to create a custom guix package of maurosoria/dirsearch
> <https://github.com/maurosoria/dirsearch>.
> Using this config
> <https://github.com/twashing/dotfiles/blob/main/guix/packages/dirsearch.scm>,
> "guix build" seems to work, except that it runs the project's unit tests.
> But iIt fails when running the project's unit tests, with these logs
> <https://snippet.host/fzavuc>.
>
> Details are in this SO post
> <https://stackoverflow.com/questions/76595986/howto-disable-unit-test-runs-when-building-custom-python-packages>
> .
> But basically, when building a custom (Github hosted) Python package, how
> can we disable unit test runs?
>
> Thanks
> Tim

Usually it should be as simple as:
(arguments '(#:tests? #f))
If it runs the tests as part of the build step, then you'll need to
either create a patch for it, use a custom source, or use substitute* to
patch it programmatically.


  reply	other threads:[~2023-07-02  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-01 22:45 Howto disable unit test runs, when building custom Python packages Timothy Washington
2023-07-02  9:21 ` Csepp [this message]
2023-08-19 12:56   ` Simon Tournier

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=87sfa6hdla.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=twashing@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.
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).