Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Nov 2017 20:05:53 -0700
From:      Bryan Drewery <bdrewery@FreeBSD.org>
Cc:        Warner Losh <imp@bsdimp.com>, Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-hackers <freebsd-hackers@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Head build unsafe for /etc today
Message-ID:  <ae73c7c8-1733-d4dc-59a6-ac6283f6c7f0@FreeBSD.org>
In-Reply-To: <CANCZdfod6uNHjNiy9WLnw3Gyg3SLy5bi4=AW3K3W7K0cquMr_g@mail.gmail.com>
References:  <3045EEBF-09E6-4209-B54F-2F95394DBA82@FreeBSD.org> <20171103014907.GA88522@troutmask.apl.washington.edu> <68BECDA4-C182-436E-854C-C3B19ABB4373@FreeBSD.org> <20171103022327.GA88659@troutmask.apl.washington.edu> <998FF503-D4B0-4AD5-AD55-98680E4D66CA@FreeBSD.org> <CANCZdfod6uNHjNiy9WLnw3Gyg3SLy5bi4=AW3K3W7K0cquMr_g@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--EIO8tKeXplnkUnsgPme1tH9JiIfD106Ft
Content-Type: multipart/mixed; boundary="l9s2H3bNWWDRX0hDhTuGWTniSVsePRB8K";
 protected-headers="v1"
From: Bryan Drewery <bdrewery@FreeBSD.org>
Cc: Warner Losh <imp@bsdimp.com>,
 Steve Kargl <sgk@troutmask.apl.washington.edu>,
 freebsd-hackers <freebsd-hackers@freebsd.org>,
 FreeBSD Toolchain <freebsd-toolchain@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>
Message-ID: <ae73c7c8-1733-d4dc-59a6-ac6283f6c7f0@FreeBSD.org>
Subject: Re: Head build unsafe for /etc today
References: <3045EEBF-09E6-4209-B54F-2F95394DBA82@FreeBSD.org>
 <20171103014907.GA88522@troutmask.apl.washington.edu>
 <68BECDA4-C182-436E-854C-C3B19ABB4373@FreeBSD.org>
 <20171103022327.GA88659@troutmask.apl.washington.edu>
 <998FF503-D4B0-4AD5-AD55-98680E4D66CA@FreeBSD.org>
 <CANCZdfod6uNHjNiy9WLnw3Gyg3SLy5bi4=AW3K3W7K0cquMr_g@mail.gmail.com>
In-Reply-To: <CANCZdfod6uNHjNiy9WLnw3Gyg3SLy5bi4=AW3K3W7K0cquMr_g@mail.gmail.com>

--l9s2H3bNWWDRX0hDhTuGWTniSVsePRB8K
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 11/2/2017 7:46 PM, Warner Losh wrote:
>=20
>=20
> On Thu, Nov 2, 2017 at 8:41 PM, Bryan Drewery <bdrewery@freebsd.org
> <mailto:bdrewery@freebsd.org>> wrote:
>=20
>=20
>=20
>     > On Nov 2, 2017, at 19:23, Steve Kargl <sgk@troutmask.apl.washingt=
on.edu
>     <mailto:sgk@troutmask.apl.washington.edu>> wrote:
>     >
>     >> On Thu, Nov 02, 2017 at 07:08:50PM -0700, Bryan Drewery wrote:
>     >>
>     >>
>     >>>> On Nov 2, 2017, at 18:49, Steve Kargl <sgk@troutmask.apl.washi=
ngton.edu
>     <mailto:sgk@troutmask.apl.washington.edu>> wrote:
>     >>>>
>     >>>> On Thu, Nov 02, 2017 at 06:25:24PM -0700, Bryan Drewery wrote:=

>     >>>>
>     >>>> On Nov 2, 2017, at 15:44, Mark Millard <markmi@dsl-only.net <m=
ailto:markmi@dsl-only.net>> wrote:
>     >>>>
>     >>>>>> Author: bdrewery
>     >>>>>> Date: Thu Nov=C2=A0 2 22:23:00 2017
>     >>>>>> New Revision: 325347
>     >>>>>> URL:
>     >>>>>> https://svnweb.freebsd.org/changeset/base/325347
>     <https://svnweb.freebsd.org/changeset/base/325347>;
>     >>>>>>
>     >>>>>>
>     >>>>>> Log:
>     >>>>>> Something is very wrong
>     >>>>
>     >>>>
>     >>>> Unfortunately I only test with META_MODE these days which impl=
ies -DNO_CLEAN.
>     >>>
>     >>> You're making changes to the build infrastructure and you're
>     >>> not properly testing it before committing?=C2=A0 This is beyond=

>     >>> pointyhat material.
>     >>
>     >> I ran 2 universes, dozens of buildworlds and buildkernels, dozen=
s of installworld and installkernel, several xdev and native-xtools, seve=
ral full DIRDEPS_BUILD builds and bootstraps, ran subdir builds, ran subd=
ir cleans, tested several targets together, ran various special case test=
s for submakes, played around with a ton of MAKEOBJDIRPREFIX cases, handl=
ed and tested symlinked objdirs special, ran it through my work repro a f=
ew times, did special testing in rescue/, and had a volunteer test releas=
e.=C2=A0 In the process=C2=A0 I found a bmake bug, GPL_DTC build bug and =
several others I don=E2=80=99t recall from the bus.
>     >>
>     >> What I missed was the =E2=80=9Cclean=E2=80=9D buildworld because=
 I forgot it even exists. I=E2=80=99ve wanted to remove it for a year. I =
also forgot to test buildenv.
>     >>
>     >
>     > If you did all the above under META_MODE, then no you did not
>     > buildworld and buildkernel and all the other stuff you claim.
>=20
>     Are you accusing me of lying?
>=20
>=20
>     > If your first step isn't=C2=A0 'cd /usr/obj ; rm -rf *' or equiva=
lent
>     > in whatever jail you use, then you're not properly testing
>     > your changes to the build
>=20
>     I did that probably 100 times. And that isn=E2=80=99t even =E2=80=9C=
the proper
>     test=E2=80=9D. Both clean and incremental are needed which I did. z=
fs
>     snapshots help a lot there. I just never ran =E2=80=9C_cleanobj=E2=80=
=9D which does
>     a full tree walk of clean. But I ran make clean in some subdirs man=
y
>     times.
>=20
>     > infrastructure.=C2=A0 As you have demonstrated,
>     > Makefile, Makefile.inc1, and the *.mk files are sufficiently
>     > complicated that proper testing
>=20
>     > should be done, and proper
>     > testing means one doesn't takes shortcuts.
>=20
>     I took 0 shortcuts. As I said I *forgot* that case, among hundreds
>     of cases.
>     You=E2=80=99re welcome to do this work if you want. I guarantee you=
 would
>     not have tested even half of what I tested.
>=20
>     Hey can you fix universe to only build clang once please? I=E2=80=99=
ve been
>     working up to that but I think you=E2=80=99re best to do it.
>=20
>=20
> Given the hundreds of commits to the build system and its complexity,
> I'm in awe this doesn't happen more often. Heck, I've done an order of
> magnitude fewer commits to the build system and broken it more often
> than you have, and that's when it was a much simpler beast than it is t=
oday.
>=20
> Steve's just being overly grumpy imho.=C2=A0 Accidents happen despite o=
ne's
> best efforts. This is -current after all...

Sorry I became grumpy too...

I am truly sorry for anyone bit by this. I understand being angry about
it. I too was bitten by it and scrambled to get a fix in on a random
system I had up without much information on what the root cause was. At
first I thought it was the last minute bmake update which came in after
my change since I had no seen anything like this in my testing.  The
commit which caused the problem was reviewed, but the bug was dormant in
unchanged code.

The bug is fixed now, but I am going to keep the AUTO_OBJ feature off
for a few days until I add a few more seatbelts to prevent this again.


--=20
Regards,
Bryan Drewery


--l9s2H3bNWWDRX0hDhTuGWTniSVsePRB8K--

--EIO8tKeXplnkUnsgPme1tH9JiIfD106Ft
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBAgAGBQJZ+90XAAoJEDXXcbtuRpfPvYEH/j14yF/c6c78Y3yOsTCZmFzA
oPcaxHOYpI/L2kaI+sxlVgwob8xJusj1nvoWDfiC9Ol2vJcaIFHmuVQfZqqy7KV8
aI+nDafC1TWlYIGV8lUaHyGGpsYf3qxhi7c/UHz5yyFeYOcJrr7BZdr36NyuVqn7
2Mhasb9YWADjLV6QzONN50RKbbX3y/HpQ008zPbGG6yLfA3lpwsna36LZ5GFN20K
thkgC0zmKw7LktLpPpHl3+dWssnduZEGNLgBWjwEcA6zS5KehhfQJwiXMvUcGFpE
G9ewiagL8AXaoy62qTtMhBm+dnos26X4RFlgOuUO+uxUeEy1rwGrnNTchOa79q0=
=uDrt
-----END PGP SIGNATURE-----

--EIO8tKeXplnkUnsgPme1tH9JiIfD106Ft--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ae73c7c8-1733-d4dc-59a6-ac6283f6c7f0>