all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: eshell-defgroup.  Do we really need this?
Date: Mon, 04 Aug 2008 11:34:49 -0500	[thread overview]
Message-ID: <86zlnszql2.fsf@lifelogs.com> (raw)
In-Reply-To: 878wvgm4mw.fsf@uwakimon.sk.tsukuba.ac.jp

On Sat, 02 Aug 2008 13:18:15 +0900 "Stephen J. Turnbull" <stephen@xemacs.org> wrote: 

SJT> 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.

SJT> Romain's right, you don't need confirmation.  If a clean build breaks,
SJT> it's broke.  What to do about it is another question.

Builds can break for many reasons, some local (e.g. disk full).  Why
bother many people with a false report?  It would condition them to
ignore truly broken builds.  That's my concern.

SJT> XEmacs has a separate list for build reports, whether user-contributed
SJT> or automatic.  From Richard's comments about the BTS, I'd put money on
SJT> him wanting a separate list for this, too.  (That's 'cause I really
SJT> like the odds, not because I speak for Richard.)  Works for us.  (We
SJT> don't use buildbot, yet.)

SJT> Python core just assumes that people (and in particular the release
SJT> engineers) will be watching the buildbot's waterfall URL.  Works for
SJT> them.

SJT> Python also has a system of "community" (ie, apps written in Python)
SJT> buildbots with the intent of notifying somebody that the dev lines of
SJT> Python are breaking stable builds.  Current status is "failing
SJT> miserably", as nobody pays attention to them.  That is For reasons
SJT> that I don't think apply to Emacs, but for the sake of completeness I
SJT> include the case here.

Thanks for explaining.  I think the case for Emacs is simpler, but I am
certainly not the one to make any decisions about it.  I just want to
provide the service because I want to do something about broken builds.

Ted





  reply	other threads:[~2008-08-04 16:34 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
2008-08-04 16:34             ` Ted Zlatanov [this message]
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=86zlnszql2.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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.