Closed Bug 863407 Opened 12 years ago Closed 12 years ago

Fix talos-r3-xp-116 and talos-r3-xp-119 or decommission them

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

From bug 861327. (In reply to Armen Zambrano G. [:armenzg] from comment #30) > (In reply to Amy Rich [:arich] [:arr] from comment #29) > > armen: I suspect 116 should probably be decommed since it's fallen over > > repeatedly. The same may be true of 119. > > That's OK. > Would we want to try to image them as win7 once? I don't think it would work > is time but I have seen weirder things. I can also understand why we would > not want to give it a shot.
What are the next steps here?
I'm fine if we decommission as XP wait times are close to good and we will have more of them once we get stop running jobs on Fedora and Win7.
We have a huge surplus of r3 machines, let's not waste time trying to fix these. I removed them from buildbot-configs in https://hg.mozilla.org/build/buildbot-configs/rev/b8c76aa20611 and marked them as decomm in slavealloc. I've also shut them down to save power.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.