From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtJj7-0000e6-37 for qemu-devel@nongnu.org; Fri, 15 May 2015 13:48:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YtJj6-00014D-6T for qemu-devel@nongnu.org; Fri, 15 May 2015 13:48:48 -0400 Message-ID: <5556317B.4080604@redhat.com> Date: Fri, 15 May 2015 13:48:43 -0400 From: John Snow MIME-Version: 1.0 References: <1431667606-14467-1-git-send-email-famz@redhat.com> In-Reply-To: <1431667606-14467-1-git-send-email-famz@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Make debugging python tests easier List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng , qemu-devel@nongnu.org Cc: Kevin Wolf , qemu-block@nongnu.org, mreitz@redhat.com On 05/15/2015 01:26 AM, Fam Zheng wrote: > Adding "-d" option. The output goes to "tee" so it appears in your > console. Also, raise the verbosity of unnitest runner. > > When testing a topic branch, it's possible that a bug introduced by a > code change makes the python test case hang, with debug output, it is > much easier to locate the problem. > > This can also be helpful if you want to watch the progress of a python > test, it offers you a way to sense the speed of each test case method > you're writing. > Awesome idea! Unfortunately, it explodes when I run ./check -v -d -qcow2 124: +Traceback (most recent call last): + File "124", line 363, in + iotests.main(supported_fmts=['qcow2']) + File "/home/bos/jhuston/src/qemu/tests/qemu-iotests/iotests.py", line 367, in main + sys.stderr.write(re.sub(r'Ran (\d+) tests? in [\d.]+s', r'Ran \1 tests', output.getvalue())) +AttributeError: 'file' object has no attribute 'getvalue' Failures: 124 Failed 1 of 1 tests --js