From: Romain Francoise <romain@orebokech.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin)
Date: Sun, 13 Apr 2008 11:31:49 +0200 [thread overview]
Message-ID: <87od8eje2i.fsf@elegiac.orebokech.com> (raw)
In-Reply-To: <4800B0B4.5070609@gmx.at> (martin rudalics's message of "Sat, 12 Apr 2008 14:53:08 +0200")
martin rudalics <rudalics@gmx.at> writes:
> After glimpsing at the BuildBot manual: It might make sense to
> (1) send a notification to emacs-devel as soon as a build of the trunk
> failed and temporarily increase the build frequency,
> (2) send another notification when the first build succeeds after that
> and decrease the build frequency to the standard value (maybe after
> another day).
Okay so there are two aspects here: (i) increase the build frequency
in case of problems, and (ii) send notifications when the build
state changes (from passing to failing and back).
Implementing (i) requires some hacking because I don't think
buildbot has a built-in scheduler that changes behavior based on
build status, so to keep things simple I just increased the
frequency (to four builds per day).
There is no existing functionality for (ii) either, but it was
trivial to implement and seems to be working okay.
Stefan, Yidong, is it okay to send these notifications to
emacs-devel?
next prev parent reply other threads:[~2008-04-13 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 9:06 Bootstrapping Emacs-23.0.60-trunk still fails (GNU/Linux, Cygwin) Angelo Graziosi
2008-04-12 7:45 ` Bootstrapping Emacs-23.0.60-trunk newly broken " Angelo Graziosi
2008-04-12 8:30 ` Eli Zaretskii
2008-04-12 9:18 ` Angelo Graziosi
2008-04-12 9:27 ` Juanma Barranquero
2008-04-12 11:46 ` Romain Francoise
2008-04-12 12:12 ` Juanma Barranquero
2008-04-12 12:16 ` martin rudalics
2008-04-12 13:41 ` Romain Francoise
2008-04-12 12:53 ` martin rudalics
2008-04-13 9:31 ` Romain Francoise [this message]
2008-04-13 14:03 ` Eli Zaretskii
2008-04-14 0:52 ` Richard Stallman
2008-04-12 13:45 ` Stefan Monnier
2008-04-12 14:06 ` Jason Rumney
2008-04-12 14:24 ` Eric Hanchrow
2008-04-12 10:08 ` Eli Zaretskii
2008-04-12 9:28 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87od8eje2i.fsf@elegiac.orebokech.com \
--to=romain@orebokech.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).