From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <glommer@gmail.com>
Cc: Erik de Castro Lopo <mle+tools@mega-nerd.com>,
qemu-devel@nongnu.org,
"Balazs Attila-Mihaly (Cd-MaN)" <x_at_y_or_z@yahoo.com>
Subject: Re: [Qemu-devel] Suggestion for testing framework
Date: Wed, 04 Jun 2008 15:36:53 +0300 [thread overview]
Message-ID: <48468C65.5040805@qumranet.com> (raw)
In-Reply-To: <5d6222a80806040532o4672be48y4d9e91cdadb5686c@mail.gmail.com>
Glauber Costa wrote:
>> Even that is tremendously useful. Once you identify a regression, it is
>> easy to bisect and pinpoint the offending patch, which also locates the
>> author.
>>
>
> Not that easy, regarding bisection. Qemu does not have an as strict
> commit policy as the linux kernel, and you bet most of the commits
> won't build fine by their own.
>
If we have such a testsuite, the motivation for bisect friendly commits
will increase.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-06-04 12:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 20:59 [Qemu-devel] Suggestion for testing framework Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 21:50 ` Erik de Castro Lopo
2008-06-03 21:53 ` Anthony Liguori
2008-06-03 22:02 ` Paul Brook
2008-06-03 22:05 ` Glauber Costa
2008-06-03 22:17 ` Anthony Liguori
2008-06-03 22:25 ` Paul Brook
2008-06-03 22:35 ` Thiemo Seufer
2008-06-04 6:41 ` Laurent Desnogues
2008-06-04 7:49 ` Laurent Desnogues
2008-06-04 9:44 ` Edgar E. Iglesias
2008-06-04 10:28 ` Avi Kivity
2008-06-04 12:32 ` Glauber Costa
2008-06-04 12:36 ` Avi Kivity [this message]
2008-06-05 10:13 ` Ian Jackson
2008-06-05 12:42 ` Avi Kivity
2008-06-04 10:36 ` Fabrice Bellard
2008-06-15 18:52 ` [Qemu-devel][Patch] " Stefan Weil
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=48468C65.5040805@qumranet.com \
--to=avi@qumranet.com \
--cc=glommer@gmail.com \
--cc=mle+tools@mega-nerd.com \
--cc=qemu-devel@nongnu.org \
--cc=x_at_y_or_z@yahoo.com \
/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.