From mboxrd@z Thu Jan 1 00:00:00 1970 From: Willem Jan Withagen Subject: Re: Compiling for FreeBSD, runtimes for seperate tests. Date: Thu, 3 Dec 2015 10:50:39 +0100 Message-ID: <5660106F.90202@digiware.nl> References: <565B3999.3050302@digiware.nl> <565B4A7F.60301@digiware.nl> <20151130065812.GA20205@gmail.com> <565D7FA8.3010301@digiware.nl> <565DA3B5.1070608@digiware.nl> <565DC9D4.7060701@digiware.nl> <565DEC36.10102@digiware.nl> <565F5E28.8020706@digiware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from smtp.digiware.nl ([31.223.170.169]:27348 "EHLO smtp.digiware.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932854AbbLCKDe (ORCPT ); Thu, 3 Dec 2015 05:03:34 -0500 In-Reply-To: <565F5E28.8020706@digiware.nl> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Sage Weil , Ceph Development On 2-12-2015 22:10, Willem Jan Withagen wrote: > Running gmake check Now I start wondering how long certain tests are able to run: I've killed: unittest_chain_xattr because it was running already voor 12 hours. And unittest_lfnindex is also running for > 20 minutes.... Is there a way to specify something like a max runtime for these tests? So that I am able to run the testset repeatedly, to monitor regression once I start changing code. I saw Loic talk about some of the expected test runtimes. But having a better feeling per specific test would be useful in getting the test to progress Thanx, --WjW