From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/4] coverity: Improve and extend model
Date: Thu, 12 Feb 2015 15:11:48 +0100 [thread overview]
Message-ID: <54DCB4A4.2080201@redhat.com> (raw)
In-Reply-To: <87egpvbijy.fsf@blackfin.pond.sub.org>
On 12/02/2015 10:11, Markus Armbruster wrote:
> > Yes, the last patch seems to be the culprit. It failed immediately with
> > the __coverity_mark_as_afm_freed__(ptr, "g_free") model;
>
> Any diagnostics?
None. It just says roughly "the build had a temporary problem and will
be rescheduled".
> The alternative is to revert the patch for now.
No problem, the model file is anyway just documentation since you have
to upload it manually.
I'll ask the admins.
Paolo
prev parent reply other threads:[~2015-02-12 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 16:24 [Qemu-devel] [PULL 0/4] coverity: Improve and extend model Markus Armbruster
2015-02-05 16:24 ` [Qemu-devel] [PULL 1/4] coverity: Improve model for GLib memory allocation Markus Armbruster
2015-02-05 16:24 ` [Qemu-devel] [PULL 2/4] coverity: Model GLib string allocation partially Markus Armbruster
2015-02-11 18:41 ` Paolo Bonzini
2015-02-12 8:52 ` Markus Armbruster
2015-02-05 16:24 ` [Qemu-devel] [PULL 3/4] coverity: Model g_free() isn't necessarily free() Markus Armbruster
2015-02-05 16:24 ` [Qemu-devel] [PULL 4/4] MAINTAINERS: Add myself as Coverity model maintainer Markus Armbruster
2015-02-05 17:11 ` [Qemu-devel] [PULL 0/4] coverity: Improve and extend model Peter Maydell
2015-02-10 16:25 ` Paolo Bonzini
2015-02-11 14:45 ` Markus Armbruster
2015-02-11 18:29 ` Paolo Bonzini
2015-02-12 9:11 ` Markus Armbruster
2015-02-12 14:11 ` Paolo Bonzini [this message]
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=54DCB4A4.2080201@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.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 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).