I'm curious why the i386 Linux distros are considered Tier 1, yet you don't say anything about x86_64. Coming from the world of financial computing, where we run just about everything on x86_64 hardware, I'm surprised you only mention i386.
Seems to me that what is most important is really the OS distro in this case (Debian, RHEL) and both i386 and x86_64 versions should be tested as Tier 1 platforms. On Tue, Nov 2, 2010 at 8:57 AM, Simon Wilkinson <[email protected]> wrote: > > On 2 Nov 2010, at 01:29, Jason Edgecombe wrote: > > > hi everyone, > > > > I'm working with someone who is offering a qemu arm buildslave. The > build on the qemu arm hosts takes ~3 hours. I'm hesitant to have all of the > gerrit submissions take three hours to build. A daily build of the git > branches might be better in this case. > > Yes. > > I'm already finding the cycle time of the IRIX build slave hugely > frustrating, and would be opposed to adding anything that lengthens that > time further. > > I think build cycles of longer than about 20 minutes are going to be > unsustainable in the long term - we should aim to put anything that takes > longer than that into their own build queues that just build the various > branch tips daily. This is similar to what other folks do with Tier 1 and > Tier 2 platforms. > > So, I guess that I'm proposing that we have i386 Debian, i386 RHEL, Darwin, > Windows and Solaris as Tier 1 systems - we aim to have buildbot coverage for > all of these, and to only push changes that buildbot verifies across all of > those platforms. > > We then have Tier 2 systems - Irix, your new Arm build slave. We accept > that master will break on these systems, but will endeavour to pick up the > pieces after buildbot has notified them. > > And finally, we have Tier 3 systems - ones for which we have no buildbot > coverage, and where we only pick up breakage when we're notified of it, > either by users, or during the pre-release smoke testing. > > Comments? > > Simon. > > > > _______________________________________________ > OpenAFS-devel mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-devel >
