From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: buildbot setup Date: Thu, 01 Jul 2010 08:00:15 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87r5jn5pcw.fsf@lifelogs.com> References: <4BEBC372.5010402@alice.it> <4BEDBF5C.1040306@alice.it> <838w7lfzdo.fsf@gnu.org> <831vddfjp9.fsf@gnu.org> <4BEE984A.4090005@gmx.at> <87eihd143p.fsf@elegiac.orebokech.com> <8739wcjosg.fsf@lifelogs.com> <87eifo9y2j.fsf_-_@lifelogs.com> <87y6dw8hmz.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1277989459 30536 80.91.229.12 (1 Jul 2010 13:04:19 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 1 Jul 2010 13:04:19 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 01 15:04:16 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OUJR9-0004qY-Oj for ged-emacs-devel@m.gmane.org; Thu, 01 Jul 2010 15:04:16 +0200 Original-Received: from localhost ([127.0.0.1]:51292 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OUJR9-0001ep-63 for ged-emacs-devel@m.gmane.org; Thu, 01 Jul 2010 09:04:15 -0400 Original-Received: from [140.186.70.92] (port=57422 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OUJNW-0000GM-B7 for emacs-devel@gnu.org; Thu, 01 Jul 2010 09:00:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OUJNT-0001dr-OU for emacs-devel@gnu.org; Thu, 01 Jul 2010 09:00:29 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:37829) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OUJNT-0001di-Bq for emacs-devel@gnu.org; Thu, 01 Jul 2010 09:00:27 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OUJNR-0002eh-0H for emacs-devel@gnu.org; Thu, 01 Jul 2010 15:00:25 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 01 Jul 2010 15:00:24 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 01 Jul 2010 15:00:24 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 59 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:jDfwuHCG0FfEAg7s5EgOVFWktNU= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:126615 Archived-At: On Wed, 30 Jun 2010 23:34:45 +0200 Lennart Borgman wrote: LB> 2010/6/30 Ted Zlatanov : >> We could use a tag.  But as I mentioned there's a lot of complexity to a >> "success" especially if we care about more than one platform and set of >> libraries. LB> Would it be possible to write a web page with something like this below? LB> To get last successful builds: LB> GNU/Linux: bzr branch http://bzr.savannah.gnu.org/r/emacs/trunk -r nnnnn1 LB> w32: bzr ... -r nnnn2 LB> ... etc Buildbot can do that, I think. I don't think it's *useful*. Do you expect users to go to this web page, read it, copy the revision, then do a checkout? They are just going to check out the trunk and complain if it doesn't work. On Thu, 01 Jul 2010 03:43:06 +0200 Stefan Monnier wrote: >> I'm not crazy about using a branch to announce a build success. SM> That's OK. You can also use a tag, of course. I'm not crazy about using a DVCS (specifically the Emacs Bazaar repo) to announce build results. My point is that it clutters the DVCS with extraneous information; if we publish builds with tags then why not publish a "best-performing-this-year" tag based on profiling results? >> How do we test multiple platforms and coordinate a push when >> they are all successful? SM> The "tested" branch should correspond to "no known problem during SM> build&test", so if there's a problem on one platform it should probably be SM> considered as a global failure. But I don't think such problems matter SM> much at this stage. I do. It may work for one platform but soon enough we'll have 20 jammed into this system and then it will just be confusing for users and developers alike. See the CPAN testers reports (http://cpantesters.org/distro/E/Every.html for example). >> I think it's better and less confusing to simply announce failures >> through another channel, perhaps as bugs. Then silence will be the >> default, which is good for everyone, and builds will not have any >> effect on the repository. SM> Many people who track Emacs's trunk don't read the mailing-list (or not SM> regularly enough) and they get annoyed when the build fails. OK, I think I see the misunderstanding. You want something for the users. I want something for the developers that can actually fix the problem and read the mailing list. My target for reporting a broken build is everyone who comitted since the last successful build and perhaps it makes sense to simply CC them on the report. If users benefit by tracking these announcements, great, but I don't think they should be targeted by an automatic build system. Ted