Closed
Bug 1042532
Opened 10 years ago
Closed 10 years ago
2.0 jobs need to fetch build from new location
Categories
(Firefox OS Graveyard :: Performance, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: davehunt)
References
Details
(Keywords: perf, Whiteboard: [c=automation p= s= u=])
So it looks like with the cutover to 2.0, we stopped fetching builds from Aurora (2.0). We need to start fetching builds from mozilla-b2g32_v2_0-* instead of the previous location.
I'll switch Eideticker over, Dave could you switch over the other jobs?
Assignee | ||
Comment 1•10 years ago
|
||
Although I suspect this will work with the master releases of our packages, we will most likely need to resolve bug 1040675 before this can be closed.
Depends on: 1040675
Assignee | ||
Comment 2•10 years ago
|
||
I have set the new build location for the b2gperf and gaia make-test perf jobs.
Updated•10 years ago
|
Severity: normal → critical
Status: NEW → ASSIGNED
Keywords: perf
Priority: -- → P1
Whiteboard: [c=automation p= s= u=]
Assignee | ||
Comment 3•10 years ago
|
||
This is done.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•