Date: Sun, 10 Jul 2016 20:30:09 +1000 From: Joe Shevland <jshevland@calm-horizons.net> To: freebsd-stable@FreeBSD.org Subject: Re: Jenkins build is still unstable: FreeBSD_stable_10 #302 Message-ID: <49883f29-9ee1-d8c4-85c1-4d18a1ea8416@calm-horizons.net> In-Reply-To: <1604686759.16.1468137562842.JavaMail.jenkins@jenkins-9.freebsd.org> References: <62698937.11.1468018652840.JavaMail.jenkins@jenkins-9.freebsd.org> <1604686759.16.1468137562842.JavaMail.jenkins@jenkins-9.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/302/>; > > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49883f29-9ee1-d8c4-85c1-4d18a1ea8416>