From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: GNUnet build failure on mips64el
Date: Fri, 21 Feb 2014 19:20:07 +0100
Message-ID: <20140221182007.GA2364@debian>
References: <87d2ih6l4f.fsf@netris.org> <20140221112701.GA26961@debian>
	<53074E2E.5080102@totakura.in> <87d2igiit6.fsf@gnu.org>
	<20140221153928.GA31681@debian> <87ob20gxu0.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59872)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1WGulM-00046E-Io
	for guix-devel@gnu.org; Fri, 21 Feb 2014 13:23:59 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1WGulF-0002VE-5d
	for guix-devel@gnu.org; Fri, 21 Feb 2014 13:23:52 -0500
Content-Disposition: inline
In-Reply-To: <87ob20gxu0.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=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: Ludovic =?iso-8859-15?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

On Fri, Feb 21, 2014 at 06:49:43PM +0100, Ludovic Courtès wrote:
> > The same holds for Qt - its build times out after 2 hours, when it is simply
> > not finished. Could we raise the timeout on hydra?
> IIUC the code, there’s not absolute timeout by default, only a
> timeout-on-silence.  Which one do we hit here?

Things seem to stop after exactly two hours, and the last line of the log
looks as if this happens in the middle of compilation.

> > Another thing: We have "four cores" (I suppose actually two hyperthreaded
> > ones) on hydra. On my machine, "top" shows four times 100%. On hydra, I get
> > the impression that only one core is working. Is this normal (due to outside
> > load, maybe), or do we need to tweak something?
> It’s supposed to use all the cores.  What makes you think only one core
> is used?

"top" does not reach the 4 times 100%, but is usually rather below 100%.

Andreas