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 23:19:03 -0500 Message-ID: <87k31y24zs.fsf@netris.org> References: <87lhmf9wy6.fsf@yeeloong.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42259) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyvDS-0007io-0J for guix-devel@gnu.org; Wed, 10 Dec 2014 23:19:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyvDM-0007FM-F9 for guix-devel@gnu.org; Wed, 10 Dec 2014 23:19:01 -0500 Received: from world.peace.net ([50.252.239.5]:33367) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyvDM-0007ED-BR for guix-devel@gnu.org; Wed, 10 Dec 2014 23:18:56 -0500 In-Reply-To: (Federico Beffa's message of "Wed, 10 Dec 2014 22:19:52 +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: > On Wed, Dec 10, 2014 at 7:33 PM, Mark H Weaver wrote: >> 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. > > Thanks for the input! It looks like on hydra the failure is > reproducible. I would therefore tend to discard randomized tests. Do > you happen to know the timeout for tests? The test fails after > 17seconds which is not very long. Any such timeout would be built in to the test suite of that package. IIRC, the only relevant timeout that guix-daemon imposes is this: if the build is silent (no output) for 1 hour, the build is aborted. > Now that you mention race conditions, I remember having a hard time > with parallel builds in ATLAS; and numpy makes use of it. I may try > adding '#:parallel-tests? #f'. It's worth a try. We currently need that in over 20 packages. Mark