From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:35135) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gpYBm-0001O7-Na for qemu-devel@nongnu.org; Fri, 01 Feb 2019 07:44:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gpYBl-0003A8-PR for qemu-devel@nongnu.org; Fri, 01 Feb 2019 07:44:58 -0500 Date: Fri, 1 Feb 2019 13:44:43 +0100 From: Kevin Wolf Message-ID: <20190201124424.GE5730@localhost.localdomain> References: <20190131123810.10233-1-berto@igalia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190131123810.10233-1-berto@igalia.com> Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qtest.py: Wait for the result of qtest commands List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alberto Garcia Cc: qemu-devel@nongnu.org, Eduardo Habkost , qemu-block@nongnu.org, Markus Armbruster , Peter Xu , Max Reitz , Cleber Rosa Am 31.01.2019 um 13:38 hat Alberto Garcia geschrieben: > The cmd() method of the QEMUQtestProtocol class sends a qtest command > to QEMU but doesn't wait for the return message ("OK", "FAIL", "ERR"). > Because of this, it can return control to the caller before the > command has actually finished. > > In cases like clock_step or clock_set this means that cmd() can return > before all the timers triggered by the clock change have been fired. > This can be fixed by making cmd() wait for the output of the qtest > command. > > This fixes iotests 093 and 136, which are flaky since commit > 8258292e18c39480b64eba9f3551 when the machine is under heavy workload. > > Signed-off-by: Alberto Garcia Thanks, applied to the block branch. Kevin