[PATCH] Provide Solaris 11 buildbots

[Rainer Orth]

Hi Sergio,

>>> There are two "special" tags: "MAIL" and "TEST".  When a builder is
>>> marked as "MAIL", the BuildBot master will send e-mail notifications
>>> about it to gdb-testers/gdb-patches.  If it's marked as "TEST", then all
>>> e-mail notifications are supressed.  I just mark a builder as "TEST" if
>>> it proves to unstable (i.e., when GDB fails to compile on it because of
>>> some problem with the builder itself).  I think it makes sense to mark
>>> your builders as "MAIL", since they're relatively stable, from what you
>>> said.
>>
>> That's the intent: the hosts (global zones in Solaris lingo) are among
>> my main (or only in case of the sparc box) development machines, so I'll
>> keep them up and running for that reason alone ;-)
>>
>> The global zones are running current Solaris 11.5 Beta builds, and thus
>> will be upgraded/rebooted biweekly.  The kernel zones which host the
>> build slaves are on Solaris 11.4, with the intent of upgrading to the
>> latest SRU (support repository upgrade; collection of patches tested
>> together) once a month.  Apart from those planned downtimes (reboots in
>> the order of minutes), the systems have been rock solid.
>
> Cool.  Reboots are fine, as long as (as you said below) the buildslaves
> reconnect automatically.

just FYI: I've now turned both buildslaves into Solaris SMF services,
and they survived reboots.  So I believe we're set on that front.

One question, though: the reboots (both host and kernel zones, which are
VMs effectively) took longer than the current missing_timeout of 5
minutes.  Would it be possible to double that or make it per-buildslave?

Thanks.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University