Last Comment Bug 767456 - [tracking bug] Get tegras into service
: [tracking bug] Get tegras into service
Status: RESOLVED INCOMPLETE
:
Product: Release Engineering
Classification: Other
Component: Buildduty (show other bugs)
: other
: x86 Mac OS X
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Armen Zambrano [:armenzg] (EDT/UTC-4)
Mentors:
Depends on: 767447 767457 767459 767469 782301 784278 784767 785172
Blocks: 772458
  Show dependency treegraph
 
Reported: 2012-06-22 10:35 PDT by Mike Taylor [:bear]
Modified: 2013-08-12 21:55 PDT (History)
2 users (show)
See Also:
Crash Signature:
(edit)
Machine State: ---
QA Whiteboard:
Iteration: ---
Points: ---


Attachments
[tools] put the rest of the tegras on foopies (5.92 KB, patch)
2012-09-04 23:11 PDT, Justin Wood (:Callek)
coop: review+
Details | Diff | Splinter Review

Description Mike Taylor [:bear] 2012-06-22 10:35:15 PDT
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
Comment 1 Justin Wood (:Callek) 2012-09-04 23:11:45 PDT
Created attachment 658383 [details] [diff] [review]
[tools] put the rest of the tegras on foopies

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)
Comment 2 Chris Cooper [:coop] 2012-09-05 07:25:02 PDT
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.
Comment 3 Mike Taylor [:bear] 2012-10-16 10:23:32 PDT
resolving as INCOMPLETE because these bugs are most likely not even being worked on or known about anymore

Note You need to log in before you can comment on or make changes to this bug.