> 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 rgri...@freebsd.org _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
