From owner-freebsd-stable@freebsd.org Sun Jul 10 10:30:43 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6299B84525 for ; Sun, 10 Jul 2016 10:30:43 +0000 (UTC) (envelope-from jshevland@calm-horizons.net) Received: from relay.ox.registrar-servers.com (relay.ox.registrar-servers.com [199.188.203.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.registrar-servers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 852821DDF for ; Sun, 10 Jul 2016 10:30:43 +0000 (UTC) (envelope-from jshevland@calm-horizons.net) Received: from MTA-06-3.privateemail.com (mta-06-3.privateemail.com [198.54.127.59]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay.ox.registrar-servers.com (Postfix) with ESMTPS id BEFCAB00AB for ; Sun, 10 Jul 2016 06:30:35 -0400 (EDT) Received: from [10.10.10.2] (unknown [10.20.151.233]) by MTA-06.privateemail.com (Postfix) with ESMTPA id 5F26E60030 for ; Sun, 10 Jul 2016 10:30:27 +0000 (UTC) Subject: Re: Jenkins build is still unstable: FreeBSD_stable_10 #302 To: freebsd-stable@FreeBSD.org References: <62698937.11.1468018652840.JavaMail.jenkins@jenkins-9.freebsd.org> <1604686759.16.1468137562842.JavaMail.jenkins@jenkins-9.freebsd.org> From: Joe Shevland Message-ID: <49883f29-9ee1-d8c4-85c1-4d18a1ea8416@calm-horizons.net> Date: Sun, 10 Jul 2016 20:30:09 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <1604686759.16.1468137562842.JavaMail.jenkins@jenkins-9.freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 10:30:43 -0000 I'm wondering if it's my build process where I'm seeing issues. I have been tracking -stable on a spare machine lately, and I've had about 60% success rate on a full build world/kernel etc. (following UPDATING instructions) on the times I do it. Been a few foot-shooting moments, but those aside, still what look to be a few just broken builds. Typically to resolve this, I'd just 'svnlite -up' in /usr/src, and rebuild, and it works fine (this little Atom/Shuttle doesn't compile things too quickly, so that's a window of 6 hours at least). Normally, I'm used to a gated commit system i.e. you commit changes, the change/s in question compiles successfully (with any other changes that have been committed by others), and only then those changes are promoted to another branch or tag (where they should compile w/o problems). Is that what happens, or am I doing things wrong? I follow that little chunk down the bottom of UPDATING normally to do a full world/kernel build. Cheers, Joe On 10/07/2016 5:59 PM, jenkins-admin@FreeBSD.org wrote: > See > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"