From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 13/13] gnu: Add beets.
Date: Fri, 25 Mar 2016 13:27:00 -0400 [thread overview]
Message-ID: <20160325172659.GA10248@jasmine> (raw)
In-Reply-To: <87io0ak0gq.fsf@netris.org>
On Fri, Mar 25, 2016 at 12:04:53PM -0400, Mark H Weaver wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Thu, Mar 03, 2016 at 08:26:39PM -0500, Leo Famulari wrote:
> >> * gnu/packages/music.scm (beets): New variable.
> >
> > I did a final cleaning pass incorporating reviewers' suggestions,
> > satisfying the linter, and updating anything that had received an upstream
> > update since I started.
> >
> > Good thing, because I had forgotten that I'd packaged an old version of
> > python-responses with the intention of updating it later! [0] This involved
> > packaging python-cookies, as well.
> >
> > Pushed as 3bf429af2fd!
>
> Hydra failed to build this.
>
> http://hydra.gnu.org/build/1090043
> http://hydra.gnu.org/build/1098131
>
> Can you take a look?
Weird :(
Since beets is basically an interactive database, my understanding is
that the test suite tests a large variety of database operations.
I'd built it on two x86_64 machines at least half a dozen times while
testing the package, without any failures like this.
I just rebuilt successfully on those machines, and also cross-built for
i686-linux. One of the machine's CPUs was fully loaded throughout
(although no real I/O contention), so I don't think that CPU load could
cause this failure.
Maybe there is some problem caused by I/O load or a lack of RAM? I can
try again if you can tell me how to simulate heavy I/O and low RAM
conditions.
Otherwise, I'm stumped. The build logs don't have any errors messages at
all; the messages just stop and hydra reports failure. I didn't
experience this locally.
Should we just try to rebuild it again on hydra?
next prev parent reply other threads:[~2016-03-25 17:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 1:26 [PATCH 00/13] Add beets and its dependencies Leo Famulari
2016-03-04 1:26 ` [PATCH 01/13] gnu: Add python-mutagen Leo Famulari
2016-03-04 1:26 ` [PATCH 02/13] gnu: Add python-munkres Leo Famulari
2016-03-04 1:26 ` [PATCH 03/13] gnu: Add python-musicbrainzngs Leo Famulari
2016-03-04 1:26 ` [PATCH 04/13] gnu: Add python-flask Leo Famulari
2016-03-04 1:26 ` [PATCH 05/13] gnu: Add python-pyechonest Leo Famulari
2016-03-04 1:26 ` [PATCH 06/13] gnu: Add python-pylast Leo Famulari
2016-03-04 1:26 ` [PATCH 07/13] gnu: Add python-responses Leo Famulari
2016-03-04 1:26 ` [PATCH 08/13] gnu: Add python2-pathlib Leo Famulari
2016-03-04 1:26 ` [PATCH 09/13] gnu: Add python-mpd2 Leo Famulari
2016-03-04 1:26 ` [PATCH 10/13] gnu: Add python-jellyfish Leo Famulari
2016-03-04 1:26 ` [PATCH 11/13] gnu: Add python2-unicodecsv Leo Famulari
2016-03-04 1:26 ` [PATCH 12/13] gnu: Add python-rarfile Leo Famulari
2016-03-04 12:42 ` Ricardo Wurmus
2016-03-04 21:29 ` Leo Famulari
2016-03-13 22:00 ` Leo Famulari
2016-03-17 21:31 ` Ricardo Wurmus
2016-03-17 21:59 ` Leo Famulari
2016-03-18 6:44 ` Efraim Flashner
2016-03-18 16:24 ` Leo Famulari
2016-03-04 1:26 ` [PATCH 13/13] gnu: Add beets Leo Famulari
2016-03-18 18:29 ` Leo Famulari
2016-03-18 20:42 ` Ludovic Courtès
2016-03-25 16:04 ` Mark H Weaver
2016-03-25 17:27 ` Leo Famulari [this message]
2016-03-25 23:37 ` Alex Griffin
2016-03-26 0:30 ` Leo Famulari
2016-03-26 0:40 ` Leo Famulari
2016-03-26 11:41 ` Ludovic Courtès
2016-03-26 14:58 ` Alex Griffin
2016-03-27 21:36 ` Leo Famulari
2016-03-27 22:25 ` Leo Famulari
2016-03-28 16:25 ` Ludovic Courtès
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=20160325172659.GA10248@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@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).