From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52127) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fBdEy-0005Wp-27 for qemu-devel@nongnu.org; Thu, 26 Apr 2018 05:31:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fBdEv-0003Um-Fd for qemu-devel@nongnu.org; Thu, 26 Apr 2018 05:31:00 -0400 Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]:46148) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fBdEv-0003UQ-8r for qemu-devel@nongnu.org; Thu, 26 Apr 2018 05:30:57 -0400 Received: by mail-wr0-x236.google.com with SMTP id d1-v6so56005100wrj.13 for ; Thu, 26 Apr 2018 02:30:57 -0700 (PDT) References: <20180424152405.10304-1-alex.bennee@linaro.org> <20180424152405.10304-44-alex.bennee@linaro.org> <84e43559-54ee-315b-24c9-c7e62e5a6d64@linaro.org> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: <84e43559-54ee-315b-24c9-c7e62e5a6d64@linaro.org> Date: Thu, 26 Apr 2018 10:30:54 +0100 Message-ID: <87604el3g1.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v3 43/46] tests/tcg/Makefile: update to be called from Makefile.target List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Henderson Cc: peter.maydell@linaro.org, cota@braap.org, famz@redhat.com, berrange@redhat.com, f4bug@amsat.org, balrogg@gmail.com, aurelien@aurel32.net, agraf@suse.de, qemu-devel@nongnu.org Richard Henderson writes: > On 04/24/2018 05:24 AM, Alex Benn=C3=A9e wrote: >> +run-%: % >> + $(call quiet-command, $(QEMU) $< > $<.out, "TEST", "$< on $(TARGET_NAM= E)") > > I've just had an x86_64 guest test run for 70 minutes. We need to limit = the > amount of time spent here in some way, with excessive time reported as te= st > failure. > > One potential way would be to add "ulimit -t $TIMEOUT" to the subshell be= fore > running qemu. A default TIMEOUT might be e.g. 15 seconds. I'm not sure = what > we should expect for the largest test on the smallest hosts... Sounds reasonable - test-i386-fprem is probably the longest - I'm not sure it needs to be so exhaustive. > > > r~ -- Alex Benn=C3=A9e