All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Make debugging python tests easier
Date: Fri, 15 May 2015 13:48:43 -0400	[thread overview]
Message-ID: <5556317B.4080604@redhat.com> (raw)
In-Reply-To: <1431667606-14467-1-git-send-email-famz@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 <module>
+    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

  reply	other threads:[~2015-05-15 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  5:26 [Qemu-devel] [PATCH] qemu-iotests: Make debugging python tests easier Fam Zheng
2015-05-15 17:48 ` John Snow [this message]
2015-05-18  1:32   ` Fam Zheng
2015-05-18 14:49     ` John Snow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5556317B.4080604@redhat.com \
    --to=jsnow@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.