Closed
Bug 971859
Opened 11 years ago
Closed 11 years ago
Re-allocate tegras that were on decommissioned foopy118
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
References
Details
We'll want to re-allocate the tegras that were on foopy118, this is because foopy118 seems to have a bad logic board, and is out of warranty. Unsure yet if we want to slot in a "new" [alt existing machine] foopy to replace it, or just spread out the tegra load. I'm leaning toward spread out tegra load. For reference tegras on the foopy: $ find build-tools/ -name "devices.json" -exec grep -B3 "foopy118" {} \; | grep "tegra" "tegra-118": { "tegra-119": { "tegra-120": { "tegra-121": { "tegra-145": { "tegra-148": { "tegra-149": { "tegra-150": { "tegra-151": { "tegra-152": { "tegra-154": { "tegra-155": { "tegra-157": {
Comment 1•11 years ago
|
||
Found this today while trying to resurrect tegras. Callek: are you still planning to return to this, or should buildduty handle it? It seems like buildduty could handle setting up a few tegras a day on new foopys. We could sure use the extra 13 devices back in circulation.
Flags: needinfo?(bugspam.Callek)
Updated•11 years ago
|
Comment 3•11 years ago
|
||
Just adding the deps to clear the buildduty queue a bit. Thanks for jumping on it.
Assignee | ||
Comment 4•11 years ago
|
||
[root@foopy125.tegra.releng.scl3.mozilla.com builds]# mkdir tegra-{118,119,120,121,145,148} [root@foopy125.tegra.releng.scl3.mozilla.com builds]# chown -R cltbld.cltbld tegra-{118,119,120,121,145,148} [root@foopy29.tegra.releng.scl3.mozilla.com builds]# mkdir tegra-{149,150,151,152,154,155,157} [root@foopy29.tegra.releng.scl3.mozilla.com builds]# chown -R cltbld.cltbld tegra-{149,150,151,152,154,155,157} ----- And checked in (and deployed) the tools change: https://hg.mozilla.org/build/tools/rev/bfd44dcd7f79
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•