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: Mon, 4 Aug 2008 17:49:01 +0000 (UTC) [thread overview]
Message-ID: <87sykiguzc.fsf__45993.8457854607$1217872198$gmane$org@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <86zlnszql2.fsf@lifelogs.com>
Ted Zlatanov writes:
> 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?
Because they don't happen much in practice on well-maintained 'bots,
which is what you want.
> It would condition them to ignore truly broken builds.
Excuse me, but isn't the problem that they already do?? (Yes, I know
that's specious. It's still true. Fix the bigger problem first. :-)
"Snappy Answers" aside, and acknowledging that broken builds are taken
very seriously by the maintainers, there's a real problem in the Emacs
build system. XEmacs and SXEmacs see *way* fewer "broken build"
reports, and when we do, the response is almost always that the
responsible developer pipes up with "oops, my bad, fixed" within 24
hours. I've *never* seen the kind of "Did you wait until the goat
died? You can't start the build before the sacrificial goat is dead!"
threads that are so common on emacs-devel.
> That's my concern.
There are sufficient broken builds in Emacs that that is not a worry.
If there is a 'bot spewing because of disk full, sentence the 'bot
owner to some public service like reading the entire Collected Works
of Richard Stallman (including the source code to all his programs)
out loud at the main gate of Microsoft.
If and when the rate of disk full reports reaches 10% of the rate of
genuine breakage, start forwarding them as bug reports to buildbot.
Also, it shouldn't be hard to construct a filter that recognizes
such and pings the 'bot owner. If you have access to the Mailman
pipeline, it can easily be installed in the list config (ie, without
risk to other Mailman lists) and set up to ping only interested
parties, and not forward it to the list.
next prev parent reply other threads:[~2008-08-04 17:49 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
2008-08-04 17:49 ` Stephen J. Turnbull [this message]
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='87sykiguzc.fsf__45993.8457854607$1217872198$gmane$org@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.