unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre-Antoine Bouttier <Pierre-Antoine.Bouttier@univ-grenoble-alpes.fr>
To: help-guix <help-guix@gnu.org>
Subject: python-mpi4py and check phase
Date: Mon, 12 Apr 2021 10:04:02 +0200	[thread overview]
Message-ID: <4A3C904B-6022-4E6C-8735-1FD5CE3BD69B@univ-grenoble-alpes.fr> (raw)

Dear all,

I try to install the « python-mpi4py » package (from the guix e18e2e4). The build fails during the check phase (which seems to be pretty common with python-packages). 

As I really need this package, I run:
$ guix install —without-tests=python-mpi4py python-mpi4py

and, as intended, it works. 

But, now, I want to install a package, which stands in our own channel, called python-h5py-mpi (available in this module : https://gricad-gitlab.univ-grenoble-alpes.fr/bouttiep/gricad_guix_packages/-/blob/master/common/python-packages.scm <https://gricad-gitlab.univ-grenoble-alpes.fr/bouttiep/gricad_guix_packages/-/blob/master/common/python-packages.scm>). This package depends on python-mpi4py.

So, this first command fails (as intended), at the check phase of the python-mpi4py building : 
$ guix install python-h5py-mpi

But, more surprisingly, it fails also in the same way if I do:
$ guix install —without-tests=python-mpi4py python-h5py-mpi

When I look the mpi4py derivation that guix try to build in both case, it is the same. As if the —without-tests arg was not taken in account. 

Do you have an idea on whatis going on, here?

Best regards
---
Pierre-Antoine Bouttier
GriCAD Research Engineer

GriCAD - https://gricad.univ-grenoble-alpes.fr/
Batiment IMAG
CS 40700
38058 Grenoble CEDEX 9

+33 4 57 42 18  66


                 reply	other threads:[~2021-04-12  8:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4A3C904B-6022-4E6C-8735-1FD5CE3BD69B@univ-grenoble-alpes.fr \
    --to=pierre-antoine.bouttier@univ-grenoble-alpes.fr \
    --cc=help-guix@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.
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).