From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: eshell-defgroup. Do we really need this?
Date: Sat, 02 Aug 2008 13:18:15 +0900 [thread overview]
Message-ID: <878wvgm4mw.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <86iquk1nsk.fsf@lifelogs.com>
Ted Zlatanov writes:
> On Fri, 01 Aug 2008 19:08:04 +0200 Romain Francoise <romain@orebokech.com> wrote:
> RF> My experience with running this buildbot (and others) suggests that
> RF> there is little value in doing this; buildbot does a clean build
> RF> every time so if it fails then we can be fairly sure that CVS is
> RF> broken.
>
> You think so even considering the large amount of people that would get
> this report? I'd rather be cautious and have at least one confirmation
> of the failure before reporting it. But, of course, it's your
> choice--as long as we report something.
Romain's right, you don't need confirmation. If a clean build breaks,
it's broke. What to do about it is another question.
XEmacs has a separate list for build reports, whether user-contributed
or automatic. From Richard's comments about the BTS, I'd put money on
him wanting a separate list for this, too. (That's 'cause I really
like the odds, not because I speak for Richard.) Works for us. (We
don't use buildbot, yet.)
Python core just assumes that people (and in particular the release
engineers) will be watching the buildbot's waterfall URL. Works for
them.
Python also has a system of "community" (ie, apps written in Python)
buildbots with the intent of notifying somebody that the dev lines of
Python are breaking stable builds. Current status is "failing
miserably", as nobody pays attention to them. That is For reasons
that I don't think apply to Emacs, but for the sake of completeness I
include the case here.
next prev parent reply other threads:[~2008-08-02 4:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:27 eshell-defgroup. Do we really need this? Alan Mackenzie
2008-07-31 19:17 ` Ted Zlatanov
2008-07-31 19:18 ` Lennart Borgman (gmail)
2008-08-01 15:34 ` Ted Zlatanov
2008-08-01 17:08 ` Romain Francoise
2008-08-01 20:30 ` Ted Zlatanov
2008-08-02 4:18 ` Stephen J. Turnbull [this message]
2008-08-04 16:34 ` Ted Zlatanov
2008-08-04 17:49 ` Stephen J. Turnbull
2008-08-04 18:38 ` Ted Zlatanov
2008-08-05 8:20 ` Stephen J. Turnbull
2008-08-05 13:57 ` buildbots (was: eshell-defgroup. Do we really need this?) Ted Zlatanov
2008-08-05 20:25 ` Stephen J. Turnbull
2008-08-08 15:26 ` place to send build failure reports? (was: buildbots) Ted Zlatanov
2008-08-08 15:58 ` place to send build failure reports? Chong Yidong
2008-08-03 19:02 ` eshell-defgroup. Do we really need this? Romain Francoise
2008-08-04 16:31 ` Ted Zlatanov
2008-08-01 16:10 ` Progress: " Alan Mackenzie
2008-08-07 19:25 ` Stefan Monnier
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=878wvgm4mw.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.