freebsd stable - Jul 2016 - Jenkins build is still unstable: FreeBSD_stable_10 #302

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 at FreeBSD.org
wrote:
> See <https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/302/>
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"

(My foot-shooting moments have involved LibreSSL and tomcat-native. I've 
removed them since).

On 10/07/2016 8:30 PM, Joe Shevland wrote:
> 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 at FreeBSD.org wrote:
>> See <https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/302/>
>>
>> _______________________________________________
>> freebsd-stable at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to 
>> "freebsd-stable-unsubscribe at freebsd.org"
>