From: Kris Van Hees <kris.van.hees@oracle.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
frysk <frysk@sources.redhat.com>
Subject: Re: Automated build-and-test summary report (2007/05/23)
Date: Thu, 24 May 2007 07:50:00 -0000 [thread overview]
Message-ID: <20070523214658.GB16276@ca-server1.us.oracle.com> (raw)
In-Reply-To: <46545CB3.6000509@redhat.com>
I may be missing something, but I honestly do not understand the issue
here. Obviously, an automated build-and-test system that performs
nightly builds is hardly any use if the results are only emailed out
once a week. The continuing existence of tests that show intermittent
failures, and the continued failure of the dist-builds (that you in fact
suggested be added to the list of configuration) indicates that we (as
developers) are not detecting and reporting all problems. The automated
system is performing a full-scale test, and extracts the relevant output
from the tests, consolidating those in clear reports.
However, if receiving a daily report in email places an undue burden on
you, I can certainly disable the scheduling of nightly builds for Frysk.
There is no point in running tests when you don't want the results
distributed to the developers.
Cheers,
Kris
On Wed, May 23, 2007 at 11:24:35AM -0400, Andrew Cagney wrote:
> Kris,
>
> Does this really need to be semi-daily? I thought it was happily
> posting weekly summaries. As developers we can more directly detect and
> report immediate problems.
>
> Andrew
>
next prev parent reply other threads:[~2007-05-23 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 15:04 Kris Van Hees
2007-05-23 21:47 ` Andrew Cagney
2007-05-24 7:50 ` Kris Van Hees [this message]
2007-05-24 19:25 ` Andrew Cagney
2007-05-24 20:39 ` Kris Van Hees
2007-05-28 19:35 ` Andrew Cagney
2007-05-29 18:50 ` Andrew Cagney
2007-05-30 12:07 ` Kris Van Hees
2007-05-30 12:53 ` Mark Wielaard
2007-05-30 21:10 ` Kris Van Hees
2007-06-01 15:27 ` Andrew Cagney
2007-05-30 13:31 ` Andrew Cagney
2007-05-30 16:08 ` Andrew Cagney
2007-05-31 8:17 ` Kris Van Hees
2007-05-31 18:05 ` Mark Wielaard
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=20070523214658.GB16276@ca-server1.us.oracle.com \
--to=kris.van.hees@oracle.com \
--cc=cagney@redhat.com \
--cc=frysk@sources.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).