From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: hydra python2-numpy-1.9.1 failure Date: Wed, 10 Dec 2014 13:33:21 -0500 Message-ID: <87lhmf9wy6.fsf@yeeloong.lan> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40400) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xym6u-00069n-Cm for guix-devel@gnu.org; Wed, 10 Dec 2014 13:35:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xym6o-0005dV-1P for guix-devel@gnu.org; Wed, 10 Dec 2014 13:35:40 -0500 Received: from world.peace.net ([50.252.239.5]:35096) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xym6n-0005dG-TP for guix-devel@gnu.org; Wed, 10 Dec 2014 13:35:33 -0500 In-Reply-To: (Federico Beffa's message of "Wed, 10 Dec 2014 19:06:16 +0100") 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: Federico Beffa Cc: Guix-devel Federico Beffa writes: > I've noticed that on hydra python2-numpy-1.9.1 for x86_64-linux (and > other architectures) fails to pass the test procedure (really the > module local version without documentation called > python2-numpy-bootstrap-1.9.1): > > http://hydra.gnu.org/build/172563 > > So, I've built it locally to investigate and on my machine it builds > without errors. The hash in the store is the same as on hydra > > /gnu/store/wyzv0xw9fi0hks5x1kagy2nl2sykbr7l-python2-numpy-bootstrap-1.9.1 > > so the inputs should be the same. > > I'm at commit 57c3f71632692d1e2e12e5d2db5c2cc4c6e075c9 (of today). The > only part which is not up to date on my system is the daemon which is > still from the 0.7 release (back then I've setup an init script to > start it automatically at boot). > > Any hint at what could be going wrong on hydra? It's not uncommon for some tests to fail occasionally in certain packages. Reasons I've seen include: timeouts set too short, race conditions, randomized tests that fail for some values, and dependencies on the kernel version and/or configuration. We've had to debug these problems on a case-by-case basis. Sometimes we've disabled the unreliable tests, or even disabled the entire test suite. Mark