From: Luiz Capitulino <lcapitulino@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] check-qdict and check-qjson fail
Date: Fri, 26 Aug 2011 14:43:25 -0300 [thread overview]
Message-ID: <20110826144325.0a41947a@doriath> (raw)
In-Reply-To: <4E57CE74.5070708@siemens.com>
On Fri, 26 Aug 2011 18:48:52 +0200
Jan Kiszka <jan.kiszka@siemens.com> wrote:
> Hi all,
>
> current master has some qregressions:
>
> # ./check-qdict
> Running suite(s): QDict test-suite
> 93%: Checks: 16, Failures: 1, Errors: 0
> check-qdict.c:289:F:Stress Test:qdict_stress_test:0: Assertion 'test_file != NULL' failed
I guess you build qemu from a different directory, right? This test only
works from the source dir. I'll fix it (actually I thought I had already fixed it!).
> # ./check-qjson
> Running suite(s): QJSON test-suite
> 95%: Checks: 21, Failures: 1, Errors: 0
> check-qjson.c:59:F:String Literals:escaped_string:0: / != \/
I found this problem while reading the parser code and added the test
so that we don't forget fixing it. However, at the time I looked at the
issue, I didn't know how to fix it.
Michael, would you mind to take a look at it?
>
> Already known?
>
> Jan
>
next prev parent reply other threads:[~2011-08-26 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 16:48 [Qemu-devel] check-qdict and check-qjson fail Jan Kiszka
2011-08-26 17:43 ` Luiz Capitulino [this message]
2011-08-26 17:52 ` [Qemu-devel] [PATCH] Fix qjson test of solidus encoding Jan Kiszka
2011-08-26 17:58 ` Luiz Capitulino
2011-08-26 17:58 ` Luiz Capitulino
2011-08-29 14:19 ` Michael Roth
2011-08-29 16:58 ` Luiz Capitulino
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=20110826144325.0a41947a@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=mdroth@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).