On Thu, Jul 6, 2017 at 4:53 PM, Theodore Ts'o <tytso@xxxxxxx> wrote: > On Thu, Jul 06, 2017 at 11:41:39AM +0200, Daniel Vetter wrote: >> +1. That pretty much means large-scale CI. The i915 test suite has >> suffered quite a bit over the past years because the CI infrastructure >> didn't keep up. Result is that running full CI kills pretty much every >> platform there is eventually, and it's really hard to get back to a >> state where the testsuite can be used to catch regressions again. > > I assume the i915 test suite requires real hardware and can't be run > on VM's; is that correct? Yes, that's another problem. If all bigger teams/subsystems would do what we'd do, but extended to all mailing lists, your patch series would get replies from a few hundred CI farms. Not sure that would scale ... And there's no way ever that one single entity will have hardware for everything. And if you only CI the mailing list for your own subsystem then every time a merge window happens your CI will be out of service (4.13 seems extremely bad, atm nothing survives an extended run on linux-next for us). -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
