From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 13/13] gnu: Add beets. Date: Fri, 25 Mar 2016 13:27:00 -0400 Message-ID: <20160325172659.GA10248@jasmine> References: <20160318182939.GB32474@jasmine> <87io0ak0gq.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55717) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ajVVr-00037d-6M for guix-devel@gnu.org; Fri, 25 Mar 2016 13:27:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ajVVn-0004Ei-5D for guix-devel@gnu.org; Fri, 25 Mar 2016 13:27:07 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:49430) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ajVVm-0004Ed-V0 for guix-devel@gnu.org; Fri, 25 Mar 2016 13:27:03 -0400 Content-Disposition: inline In-Reply-To: <87io0ak0gq.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Mark H Weaver Cc: guix-devel@gnu.org On Fri, Mar 25, 2016 at 12:04:53PM -0400, Mark H Weaver wrote: > Leo Famulari 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?