From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51192) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gLAHG-0006IY-Cd for qemu-devel@nongnu.org; Fri, 09 Nov 2018 12:09:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gLAHA-0007Vd-Qx for qemu-devel@nongnu.org; Fri, 09 Nov 2018 12:09:02 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41525) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gLAHA-0007Da-AX for qemu-devel@nongnu.org; Fri, 09 Nov 2018 12:08:56 -0500 References: <20181109153002.597-1-crosa@redhat.com> <20181109153002.597-2-crosa@redhat.com> <20181109155640.GA12624@flamenco> From: Cleber Rosa Message-ID: Date: Fri, 9 Nov 2018 12:08:13 -0500 MIME-Version: 1.0 In-Reply-To: <20181109155640.GA12624@flamenco> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH 1/2] tests/test-qht-par: test gets stuck intermittently on OSX List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Emilio G. Cota" Cc: qemu-devel@nongnu.org, Fam Zheng , Eduardo Habkost , =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= , =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= , Wainer dos Santos Moschetta , programmingkidx@gmail.com, Caio Carrara , =?UTF-8?Q?Alex_Benn=c3=a9e?= On 11/9/18 10:56 AM, Emilio G. Cota wrote: > On Fri, Nov 09, 2018 at 10:30:01 -0500, Cleber Rosa wrote: >> To be fully honest, this may not be a OSX (alone) condition, but may >> be a situation that only happens with OSX on Travis-CI, were resources >> are quite limited. >> >> I have personal experience with tests that exercise parallelism or >> depend on timing to fail on Travis. Because I'm not 100% certain that >> this is a situation that only happens with OSX on Travis-CI, and >> because I'm not certain that we should be skipping tests because >> they're running on Travis-CI, let's disable them on OSX as a whole. >> >> A small note: this type of change makes me believe that there should >> be a list of testing related caveats or TODO list tracked on the >> documentation. >> >> Signed-off-by: Cleber Rosa > > Is there a way to know where it hangs? > > Also, are these the g_test_quick tests, or the other ones? It it's > just a matter of the program taking too long to run, we could just > reduce the length of the !quick tests (currently at 5s vs. 1s for > the quick ones). > > Thanks, > > Emilio > Looks like the common cause was fixed a458774ad711bceabefb, as pointed out by Peter. - Cleber.