Closed
Bug 767456
Opened 12 years ago
Closed 12 years ago
[tracking bug] Get tegras into service
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bear, Unassigned)
References
Details
Attachments
(1 file)
5.92 KB,
patch
|
coop
:
review+
|
Details | Diff | Splinter Review |
28 new tegras from bug 767447 need to be added to: slavealloc buildbot configs tegras.json assigned to a foopy get two foopies stood up
Updated•12 years ago
|
Summary: [tracking bug] get 28 new tegras into service → [tracking bug] Get tegras into service
Comment 1•12 years ago
|
||
This reflects what I just stood up, I did just push this live, so we can get the reporting power of the dashboard which needs the tegras.json updates. With this we have 1 tegra left unassigned (since its acting up, 226) but other than that all are assigned somewhere (or dead or loaned-- but in our infra)
Attachment #658383 -
Flags: review?(coop)
Comment 2•12 years ago
|
||
Comment on attachment 658383 [details] [diff] [review] [tools] put the rest of the tegras on foopies Review of attachment 658383 [details] [diff] [review]: ----------------------------------------------------------------- A few trailing spaces, but not the end of the world if those don't get fixed before landing.
Attachment #658383 -
Flags: review?(coop) → review+
Reporter | ||
Comment 3•12 years ago
|
||
resolving as INCOMPLETE because these bugs are most likely not even being worked on or known about anymore
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [tracking][buildslaves][tegra]
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 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
•