From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: 23364@debbugs.gnu.org
Subject: bug#23364: python-statsmodels build failures
Date: Sat, 10 Feb 2018 20:07:01 -0500 [thread overview]
Message-ID: <20180211010701.GA28859@jasmine.lan> (raw)
In-Reply-To: <87mv0gmrco.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On Sat, Feb 10, 2018 at 05:07:03PM -0500, Mark H Weaver wrote:
> reopen 23364
> thanks
>
> Andreas Enge <andreas@enge.fr> writes:
>
> > This has probably been fixed in the following commit:
> >
> > commit 25b2c47d753efd0761a4e16519dce38d828789f5
> > Author: Hartmut Goebel <h.goebel@crazy-compilers.com>
> > Date: Sun Oct 16 18:40:58 2016 +0200
> >
> > gnu: python-statsmodels: Fix build
> >
> > * gnu/packages/statistics.scm (python-statsmodels): [check] set
> > PYTHONPATH prior to running tests.
> >
> > In any case the package did compile in 2017, and was updated later to 0.8.0.
>
> No, there have been over 200 nondeterministic build failures of
> python-statsmodels since that commit, including over 140 failures of
> 0.8.0. I usually have to ask Hydra to attempt to rebuild it several
> times before it finally succeeds.
I wonder if the test suite is really worth running in this case? Maybe
we should just report the failures upstream and skip the tests.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-11 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 21:27 bug#23364: python-statsmodels build failures Mark H Weaver
2016-04-24 22:12 ` Cyril Roelandt
2018-02-09 21:33 ` Andreas Enge
2018-02-10 22:07 ` Mark H Weaver
2018-02-11 1:07 ` Leo Famulari [this message]
2020-08-17 4:34 ` Maxim Cournoyer
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=20180211010701.GA28859@jasmine.lan \
--to=leo@famulari.name \
--cc=23364@debbugs.gnu.org \
--cc=mhw@netris.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).