Closed
Bug 747641
(tegra-224)
Opened 12 years ago
Closed 12 years ago
tegra-224 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Unassigned)
References
()
Details
(Whiteboard: [buildduty][capacity])
The solid stream of red in https://build.mozilla.org/buildapi/recent/tegra-224?numbuilds=100 says it needs a stop_cp and a chance to think about what it has done.
Comment 1•12 years ago
|
||
taken offline
Comment 2•12 years ago
|
||
Was/Is attached to foopy19, We have no idea if it was ever repaired. Might be worth taking over to staging (foopy05), so assigning to me to figure out these details.
Assignee: nobody → bugspam.Callek
Comment 3•12 years ago
|
||
I assigned tegra-146 to foopy19 instead, and pulled 224 to throw it into staging instead (foopy05) http://hg.mozilla.org/build/tools/rev/fdf190203a10
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•10 years ago
|
Assignee: bugspam.Callek → nobody
QA Contact: armenzg → bugspam.Callek
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
•