From: Robert Schiele <rschiele@uni-mannheim.de>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: automatic bootstrap failure notification
Date: Wed, 14 Aug 2002 13:23:00 -0000 [thread overview]
Message-ID: <20020814202226.GA7028@schiele.local> (raw)
In-Reply-To: <20020814095508.A1785@us.ibm.com>
On Wed, Aug 14, 2002 at 09:55:08AM -0700, Janis Johnson wrote:
> On Tue, Aug 06, 2002 at 02:05:22PM +0200, Robert Schiele wrote:
> > Hello,
> >
> > as some may have already noticed, I am sending the results of the
> > regression tests after successful bootstrap processes to
> > gcc-testresults from my automatic build system for some time now.
> >
> > I am currently adding a feature to this build system that allows
> > sending automatic notification messages with some relevant information
> > when bootstraping fails.
> >
> > Would sending such messages to gcc-testresults be welcome or would
> > such messages be seen as annoying?
>
> I think this is a good idea. It would be useful if everyone who has
> automated builds regularly sending test results to gcc-testresults
> also sent mail there about bootstrap failures, particularly if they
> used the same (or similar) scripts to generate those messages so they
> had similar information.
Ok, I have simulated a bootstrap failure by killing make during
bootstrap. This made the system to send the message
http://gcc.gnu.org/ml/gcc-testresults/2002-08/msg00451.html to
gcc-testresults.
Feel free to send comments about the message contents.
To be complete I am attaching the script used for this purpose. But
be warned: This is currently just a fast and ugly bash hack. You may
do with the files what you like as long as it conforms with the GPL
and you remove my email address from the NOTIFY_FAILURE variable
_please_. But it might make sense to do a somewhat cleaner
implementation for general usage. But comments for the current script
are also welcome.
The file autobuild.common is the one that matters. This file should
never be called directly, but by a configuration script. I also
attached a sample of such a configuration script for reference. Up to
now I was too lazy to write real documentation. ;-)
Robert
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iQEVAwUBPVq8AsQAnns5HcHpAQHM7wgA0qnONIhcYNviK+A/8tQ2XaRE4TEdaAWs
HNQwimRF0YugVedBSUhHgvF6ni7gjbPYnc2CSqEt77dJb55EwFZP2wJlCRJXrbr6
RcjcuN7mqYm6LOxW3weixnpfbEnlwm9qWHeUaaLVu5b6v8VPq5HFzJVMh3dry3u4
OK2K21RiFeiRAfK87s4DTDh33t6PfdRJRgQ4g2FVp/RKUB4jBPuFvtkdJ1AMgmnE
4T4mEMh1bP3M4aVwa2+lsk1O7GFt0Or91zLgIHDoILo5M1SE+wmm+/Swt74fbXXX
92ZFeQzXW1ttBKbtIt32HQTbCPAfGoObBj1FEr2Z2LQEsGPiARAPDA==
=iJsK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-08-14 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 5:19 Robert Schiele
2002-08-06 5:56 ` Daniel Jacobowitz
2002-08-06 6:20 ` Robert Schiele
2002-08-14 9:53 ` Janis Johnson
2002-08-14 13:23 ` Robert Schiele [this message]
2002-08-14 20:38 ` Robert Schiele
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=20020814202226.GA7028@schiele.local \
--to=rschiele@uni-mannheim.de \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.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).