Closed Bug 556574 Opened 12 years ago Closed 8 years ago

Regression detection should find which page caused the regression

Categories

(Testing :: Talos, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1020677

People

(Reporter: catlee, Unassigned)

Details

(Whiteboard: [talos][automation][SfN])

For tests like Tp4 or SunSpider, the aggregate test number is composed of the results of several smaller tests.

When a regression is detected in one of these suites, it would be nice to get a report of which of the smaller pieces caused the change.
Priority: -- → P3
Whiteboard: [talos][automation]
Is this something still wanted?

Would the final value still report a regression that happened in one of the smaller tests?
Assignee: nobody → armenzg
Priority: P3 → P4
jmaher, this bug sounds like one of the items we discussed for SfN.
Is there a bug where this idea is being worked on?
This sounds like a DUPE to me.
I don't know of the bug, but this is something which we are working towards.
Whiteboard: [talos][automation] → [talos][automation][SfN]
Makes sense to move to Testing:Talos until there is an actionable item for Releng?
Assignee: armenzg → nobody
Component: Release Engineering → Talos
Product: mozilla.org → Testing
QA Contact: release → talos
Version: other → Trunk
OS: Linux → All
Hardware: x86 → All
we are tracking this work in bug 1020677 - in fact we already generate alerts for this, but the final solution requires a UI.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1020677
You need to log in before you can comment on or make changes to this bug.