From: Andrew Cagney <cagney@redhat.com>
To: Stan Cox <scox@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: Automated build and test system (overview)
Date: Mon, 12 Mar 2007 18:59:00 -0000 [thread overview]
Message-ID: <45F5A30F.4060506@redhat.com> (raw)
In-Reply-To: <1173714324.27599.136.camel@multics.rdu.redhat.com>
GCC's regression tester is a well cited example of how to not report
test results ;-) It e-mails everyone that made a change, no matter how
irrelevant, having the effect of crying wolf :-(
Testing such as being discussed here gives us access to higher level
trend data. Examining that data allows us to identify emerging
problems, for instance constant breakage with a specific compiler,
kernel breakages. When applicable we can then adjust our processes do
address persistent problems.
Andrew
Stan Cox wrote:
> On Mon, 2007-03-12 at 13:23 +0100, Mark Wielaard wrote:
>
>> Having something that can pinpoint when
>> which test result flipped from PASS/FAIL would be great.
>>
>
> Perhaps something like the gcc regression tester which posts regressions
> along with ChangeLog entries since the last run:
> http://gcc.gnu.org/ml/gcc-regression
> ?
>
>
>
next prev parent reply other threads:[~2007-03-12 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 17:15 Kris Van Hees
2007-03-12 12:23 ` Mark Wielaard
2007-03-12 15:45 ` Stan Cox
2007-03-12 18:59 ` Andrew Cagney [this message]
2007-03-12 19:09 ` Stan Cox
2007-03-12 17:45 ` Kris Van Hees
2007-03-17 19:10 ` Mark Wielaard
2007-03-20 17:19 ` Andrew Cagney
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=45F5A30F.4060506@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=scox@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).