Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Nov 2015 10:31:28 +0000
From:      Glen Barber <gjb@FreeBSD.org>
To:        Baptiste Daroussin <bapt@FreeBSD.org>
Cc:        Li-Wen Hsu <lwhsu@FreeBSD.org>, freebsd-stable@FreeBSD.org, jenkins-admin@FreeBSD.org
Subject:   Re: FreeBSD_STABLE_10-i386 - Build #661 - Still Failing
Message-ID:  <20151125103128.GJ1347@FreeBSD.org>
In-Reply-To: <20151123181540.GB76516@ivaldir.etoilebsd.net>
References:  <196615497.107.1448287849026.JavaMail.jenkins@jenkins-9.freebsd.org> <1065209114.111.1448295034864.JavaMail.jenkins@jenkins-9.freebsd.org> <20151123162036.GA76516@ivaldir.etoilebsd.net> <20151123170650.GA14571@FreeBSD.cs.nctu.edu.tw> <20151123181540.GB76516@ivaldir.etoilebsd.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--jIYo0VRlfdMI9fLa
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Nov 23, 2015 at 07:15:40PM +0100, Baptiste Daroussin wrote:
> > The build happens in a jail built every time the job starts, by fetching
> > the latest snapshot from:
> >=20
> > http://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/11.0-CURRENT/bas=
e.txz
> >=20
> > It looks there is no /usr/bin/colldef.  I haven't looked into what's
> > going on here.
> >=20
>=20
> Ok so it will be fixed by the next snapshot
>=20

The Jenkins builders absolutely *cannot* rely on files within the
snapshots/ directory on the mirrors to exist.  Relying on files that
possibly could not exist (failed builds for extended periods of time,
for example), is an implementation bug.

The Jenkins configurations need to be updated to use the base.txz under
the releases/ directory, and for building -CURRENT, must use the latest
major release base.txz (not *snapshot* build).

In other words:

 9.3-STABLE: built from 9.3-RELEASE
 10.2-STABLE: built from 10.2-RELEASE
 11.0-CURRENT: built from 10.2-RELEASE

This ensures:

1) edge cases where a snapshot (which is *not* a release) is built
   between a problematic commit does not prevent Jenkins spam;
2) source-based upgrades from the last major version to -CURRENT (which
   in turn, ensures 10.2-RELEASE can be source-upgraded to 11.0-RELEASE)
   is tested.

This must be fixed by Jenkins Admins.

Glen


--jIYo0VRlfdMI9fLa
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWVY4AAAoJEAMUWKVHj+KTkxEP/3dndUHNKQZtz624+wu5D0i4
3q4xgIUs678juS+SM/CjrEG3YNE9pft2UNOnpigN6VCQfkOtCb0Xx6sfBuPbYhVX
4lH6v0wR4qad+7e9N67MWSdPLF64NsmSWOAKU3Z9xi/Ukejy3FLW9AWj89g6A7sR
ufK0vhOJYz/03WOhNQSHWA4t3mqVW2a+/Ggh2c8jIg6zT/YNvpYrz7imHwGVD9it
eBS+kASbGAZXbEtGImDYbobCedRDpWzAIBO0remVXi68URmtLrPt6f8mexPeIYaV
Wz08J98NBhoo9SM8HHA3e86/MI75msobwrmeCmUIRjBWxH4r6fxIWS+ME+8vbbmb
hNzyKPQRP+LdaXaERBsiR7DDKuF5QfhMLgHTWsnrdtlygyehPggtMpyWgPU/teYn
MUDK2e2IWbCMagFJvHyJYVwviPMXdiGdILSRYAGe8ksSHYb8SXC9vvwPka36djc9
RFaDfb9hco4l420RcC9Aw4RzitTe6riB/z5ZNPdqG7pVg725o01uEUiVHSC2OWaP
ujpn53s5awX767lp493U57ANoiqT01SD4F3fJofMxrJuuIKE+r06jfgF/nEGDGw1
3sSrzTDDkq1Tr57Sz5DBhEQsjL4rWUMiyq9b+UzJ4+ew8YUggD+9LtsQMT/6BXnt
Yk61XUZbWe56rNBx9Xp4
=ma4D
-----END PGP SIGNATURE-----

--jIYo0VRlfdMI9fLa--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151125103128.GJ1347>