From: Fam Zheng <famz@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tests: make docker-test-debug@fedora run sanitizers
Date: Tue, 13 Mar 2018 01:41:02 +0800 [thread overview]
Message-ID: <20180312174102.GD8326@lemon.usersys.redhat.com> (raw)
In-Reply-To: <CAJ+F1CKugGNH7kdchrpuF+GXSPMd4s2-w7bSCpH3UNHiwQGR1A@mail.gmail.com>
On Mon, 03/12 18:17, Marc-André Lureau wrote:
> Hi
>
> On Mon, Mar 12, 2018 at 6:11 PM, Fam Zheng <famz@redhat.com> wrote:
> > On Mon, 03/12 15:11, Marc-André Lureau wrote:
> >> Hi Fam,
> >>
> >> It would be great if patchew could run the debug/sanitizer build.
> >> Unfortunately, except x86 target, the run is full of ASAN leaks or
> >> warnings.
> >>
> >> Do you think patchew could learn to do regression testing? By that I
> >> mean that patchew could compare a patchset output with the current
> >> master (that output should be cached for multiple tests). The output
> >> to compare here would be the errors reported by ASAN during the build.
> >> (eventually, this could be used for other metrics some day). If so,
> >> would you be willing to help me implementing it?
> >
> > The question is can we simply rely on the exit code of cmp or diff for that kind
> > of comparison? If there is any out-of-order texts, that simple diff won't work.
>
> If the tests are run sequentially, i think it should produce the same
> output when run multiple times (to be verified).
In that case the test will last for a long time. Currently patchew isn't very
good as multi-tasking. But that is one option we can explore (like we can devote
one VM for asan test).
>
> However, if there are leaks already, and the address of allocation or
> symbols change, this may produce diff on existing lines.
Maybe we can come up with a 'make docker-test-debug-filtered@fedora' or a
relatively simple 'make docker-test-debug@fedora | sed -e "..."' command that
can be fed to diff.
>
> What I would like to see is the diff of added (or removed) lines.
>
> I suppose that should be possible, I'll do some experiments.
>
> > Anything more intelligent/sensible should go as a policy, and patchew should
> > continue focus on mechanisms.
>
> hmm ok :)
Like said above, I think it's possible to postprocess the output to make it easy
to diff/cmp. By mechanism/policy I mean the place to draw a line to code
Patchew. However patchew has a database where we can write test script snippets
(as configurations) that is "the policy".
Fam
prev parent reply other threads:[~2018-03-12 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 12:08 [Qemu-devel] [PATCH] tests: make docker-test-debug@fedora run sanitizers Marc-André Lureau
2018-03-12 14:11 ` Marc-André Lureau
2018-03-12 17:11 ` Fam Zheng
2018-03-12 17:17 ` Marc-André Lureau
2018-03-12 17:41 ` Fam Zheng [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=20180312174102.GD8326@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=marcandre.lureau@gmail.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 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.