On loan to an unknown person whose only trace was leaving the note "Reserved for testing ( do not enable or reboot!)" in slavealloc while disabling it on January 28th.

After some archaeology, I linked bug 916765 in the slavealloc notes, which also links to bug 1122975.

Ah, that explains the wrongness before the loan - a single instance of that known intermittent, during the time when we knew something was broken but didn't yet realize the problem was a set of slaves with only 4gb, so someone rage-disabled it with a useless slavealloc note and failed to reopen the tracking bug. 99.9% chance the slave is fine.

From Q via email on Feb 23: "0019 was deemed "unusable" as being "too-slow" and was loaned to relops for AWS image testing. The orginal note had a bug number not "( do not enable or reboot!)" . Don't know what happend there. I will copy the VHD capture information off that machine and hand it back over to see if it isn't "too slow" anymore" Are we ready to put this slave back into production yet?

Done and reimaging now. Q

Re-enabled and returned to production.

on loan for "Bug 989531 - Deploy NSIS 3.0b1 to buildslaves" work

Re-imaged and returned to production (try).

disabled to facilitate bug 1198317

allocated to bug 1198317

deallocated from bug 1198317