From owner-freebsd-current Mon Apr 17 14:49:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 903EA37B6C3 for ; Mon, 17 Apr 2000 14:49:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA02329; Mon, 17 Apr 2000 14:51:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 23:17:15 +0200." <12411.956006235@critter.freebsd.dk> Date: Mon, 17 Apr 2000 14:51:20 -0700 Message-ID: <2326.956008280@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a machine which isn't doing much right now, so I have decided > to set it up as an automatic "FreeBSD Build checker". Welcome to the current.freebsd.org game. :) > Once per day the machine cvsups, checks out a virgin source tree, > tries to build GENERIC, GENERIC98, LINT and world. If any of these > builds fail it will send a report like this. > > On Sundays the report will always be sent. > > Once I have this tested a bit more, I will start mailing the the > reports directly to current@freebsd.org And now we get into a slightly twitchy area... These error messages can be quite long and annoying, far too detailed for the likes of the -current mailing list, which is why I've been sending them only to an opt-in alias called "build-reports@freebsd.org" which sends a success/failure summary like yours and include the last 100 lines of failure output for debugging. It also does this for both the RELENG_4 branch and -current. That said, I've also done a singularly bad job of actually letting people know that build-reports even exists so I wouldn't expect you or anyone else (except maybe Bill Paul) to have known about it. It's just an alias on hub.freebsd.org right now and not a real majordomo-managed mailing list, so I wasn't inclined to take on the workload of managing the alias. It does at least log its results to the build-reports mail archive so anyone looking in /home/mail/build-reports on hub can also spy on the current status of both active branches. If there's a real interest in this, then this should obviously be created as a real mailing list and probably split into build-reports-stable and build-reports-current for people who only want one or the other. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message