On Wed, Feb 26, 2020 at 2:07 AM Michel Dänzer <mic...@daenzer.net> wrote: > > On 2020-02-26 4:56 a.m., Rob Clark wrote: > > It looks like we have 4 scons build jobs in CI.. I'm not sure how much > > that costs us, but I guess those cycles could be put to better use? > > So even ignoring the developer-cycles issue (ie. someone making > > changes that effects scons build, and has to setup a scons build env > > to fix breakage of their MR) I guess there is at least an argument to > > remove scons from CI. Whether it is worth keeping a dead build system > > after it is removed from CI is an issue that I'm ambivalent about. > > As long as it's supported, it needs to be tested in CI. >
Well, I mean, removed from CI (but files left in place) would put it at the same level of "support" as android build. Ie. not tested in CI and doesn't block merging changes, but people who use it are on the hook for pushing fixes when it does break. BR, -R _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev