From owner-freebsd-current  Wed Sep  4 03:31:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA05397
          for current-outgoing; Wed, 4 Sep 1996 03:31:31 -0700 (PDT)
Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA05392
          for <current@freebsd.org>; Wed, 4 Sep 1996 03:31:25 -0700 (PDT)
Received: (from uucp@localhost) by perki0.connect.com.au id UAA22736
  (8.7.5/IDA-1.6); Wed, 4 Sep 1996 20:31:03 +1000 (EST)
>Received: from localhost (localhost [127.0.0.1]) by nemeton.com.au (8.7.5/8.7.3) with SMTP id UAA28175; Wed, 4 Sep 1996 20:08:14 +1000 (EST)
Message-Id: <199609041008.UAA28175@nemeton.com.au>
To: "Frank E. Terhaar-Yonkers" <fty@mcnc.org>
cc: current@freebsd.org
Subject: Re: suggestion: Re: Latest Current build failure 
In-reply-to: <199609032053.QAA25476@robin.mcnc.org> 
Date: Wed, 04 Sep 1996 20:08:14 +1000
From: Giles Lean <giles@nemeton.com.au>
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 3 Sep 1996 16:53:06 -0400  "Frank E. Terhaar-Yonkers" wrote:

> How about a simple status report?  Like simply the CTM # and a one
> word status: "ng" (won't build), "builds" and "runs" (reasonably
> stable).

I'm working on this.  I presently think the test for OK should be just
that 'make world' ran OK and then a newly built kernel could be
booted.  This much is easy to automate.

Following another posting I guess that if 'make world' fails it should
be retried after 'make bootstrap'.  Thoughts, anyone?

Judging "stable" is rather more difficult for a dumb shell script. :-)

Giles