[graph server] Enable Talos regression analysis for UX and Holly trees

RESOLVED FIXED

Status

Release Engineering
General
--
blocker
RESOLVED FIXED
5 years ago
a year ago

People

(Reporter: MattN, Assigned: bhearsum)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [regression-detection])

Please add the UX and Holly trees to graph server's analysis.cfg. UX is currently an integration branch for Australis and Holly will soon become the integration branch for the backout of Australis.[1]

[1] https://msujaws.wordpress.com/2013/11/08/australis-landing-plans/
Depends on: 937926
We need this as soon as possible so there aren't any surprises on Holly.
Severity: normal → critical
(Assignee)

Comment 2

5 years ago
Chris, how do we do this? I can't find any references to it on wiki.m.o or any of our repos.
Flags: needinfo?(catlee)
(Assignee)

Comment 3

5 years ago
12:34 <@catlee> bhearsum: so, graph server analysis is running out of...um...
12:34 <@catlee> ~catlee on cruncher
12:37 <@catlee> bhearsum: basically edit /home/catlee/graphs/server/analysis/analysis.cfg and put the new branch(es) at the bottom
12:37 <@catlee> PGO branches need to be added separately
Flags: needinfo?(catlee)
We should consider stopping merges to Holly until this is fixed as nobody wants to be hunting down regressions that happened weeks prior. It is very, very likely that Holly will be merged to Aurora at the end of the cycle and so the tree needs to be in good shape.

Thanks
Severity: critical → blocker
(Assignee)

Comment 5

5 years ago
Whoops, I meant to look at this already. I'll dive into it today.
Assignee: nobody → bhearsum
(Assignee)

Comment 6

5 years ago
I'm very sorry for the delay here, but I'm pretty sure this is working now. It found a bunch of improvements on the first run: https://groups.google.com/forum/#!topic/mozilla.dev.tree-management/SybceAhwqUU
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.