Closed
Bug 1416696
Opened 7 years ago
Closed 4 years ago
Enable AWFY for performance sheriffing
Categories
(Testing Graveyard :: AWFY, enhancement)
Testing Graveyard
AWFY
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: igoldan, Unassigned)
References
Details
We must address following steps to properly sheriff AWFY alerts: 1. Enable job retriggering 2. Triage alerts from last 2-3 months 3. Identify unstable tests (on specific platforms) 5. Gather docs for all our stable tests & publish them 6. Disable unstable tests
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → igoldan
Comment 1•7 years ago
|
||
#1 will be difficult. you can do it with AWFY, but right now it isn't from treeherder. Also there is a lack of backfilling on AWFY and I don't think that exists currently. Related to this topic is load on the machines- Most of these machines have much fewer available CPU cycles- so getting many extra runs in will be hard. I would solve 3/5/6 in your list (there is a 4 missing) and then we can delete old alerts and start triaging from a given point in time.
Updated•7 years ago
|
Whiteboard: [PI:November]
Updated•7 years ago
|
Status: NEW → ASSIGNED
Comment 2•7 years ago
|
||
(In reply to Joel Maher ( :jmaher) (UTC-5) from comment #1) > #1 will be difficult. you can do it with AWFY, but right now it isn't from > treeherder. Also there is a lack of backfilling on AWFY and I don't think > that exists currently. Related to this topic is load on the machines- Most > of these machines have much fewer available CPU cycles- so getting many > extra runs in will be hard. This kind of thing (feature parity with Taskcluster jobs) is only going to get harder for third parties I think. I've posted to the Taskcluster newsgroup on this topic: https://groups.google.com/forum/#!topic/mozilla.tools.taskcluster/Stpw9bKq-h4
Comment 3•7 years ago
|
||
:igoldan, can you update here with where we are at and what are the next steps?
Flags: needinfo?(igoldan)
Reporter | ||
Comment 4•7 years ago
|
||
I didn't manage to look over this issue yet.
Flags: needinfo?(igoldan)
Reporter | ||
Comment 5•7 years ago
|
||
I'm working on finalizing bug 1400380.
Updated•7 years ago
|
Whiteboard: [PI:November] → [PI:January]
Comment 6•6 years ago
|
||
I think we need to revisit this in Q2- we might reduce the number of benchmarks (and also add some different ones)- likewise we need the ability to push to try and run locally- we either need to fix AWFY to make it modern, or create a tier-2 sheriffing model.
Assignee: igoldan → nobody
Status: ASSIGNED → NEW
Whiteboard: [PI:January]
Updated•6 years ago
|
Component: Perfherder → AWFY
Product: Tree Management → Testing
Version: --- → unspecified
Comment 7•4 years ago
|
||
AWFY is dead. Long live AWFY.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 8•4 years ago
|
||
Dave, could we remove AWFY entirely from Perfherder?
Flags: needinfo?(dave.hunt)
Updated•4 years ago
|
Product: Testing → Testing Graveyard
Comment 9•4 years ago
|
||
(In reply to Ionuț Goldan [:igoldan] from comment #8)
Dave, could we remove AWFY entirely from Perfherder?
Yes, please do.
Flags: needinfo?(dave.hunt)
You need to log in
before you can comment on or make changes to this bug.
Description
•