Date: Sat, 4 Nov 2017 10:23:10 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: 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: <201711041723.vA4HNANJ001399@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <ec4f16fc-eeb3-d778-94f6-6b564b0e6987@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 11/2/2017 8:58 PM, Warner Losh wrote: > > FreeBSD has grown too big to test every possible thing before you commit. I would say that it has always been too big to test every possible thing before a commit. Breakage is just going to happen, we make great efforts to minimize it, but like all risks sooner or later your gona have a failure. > > The build itself is massive. I usually forget about release/ and the > new 'make packages', external toolchain, "old style" kernel builds, etc. Good starting list for "make build-regresion" ? > > Steve's concerns have validity. I do think it's time we have an > automated suite to test most build cases for things like bmake upgrades > or other high risk changes like META_MODE. > > > I'll think about this and add to my list of things to implement. I would even go so far as to say this may be what we should be running in (a) Jenkins. Or perhaps a deeper exp-run? -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201711041723.vA4HNANJ001399>