Open Bug 1570906 Opened 5 months ago Updated 3 months ago

Performance alert created from a [tier 3] job

Categories

(Tree Management :: Perfherder, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: alexandrui, Unassigned)

Details

This alert was created from a [tier 3] job, and wasn't supposed to. IIRC, we keep unstable jobs on [tier 3] until they settle and then move them to upper tiers.
Eric, could you look into and eventually take the necessary actions, please?
Thaanks!

Flags: needinfo?(erahm)
Component: Perfherder → AWSY
Product: Tree Management → Testing
Version: --- → unspecified
Priority: P2 → --
Summary: Alert created from a [tier 3] job → Performance alert created from a [tier 3] job

Bugbug thinks this bug is a task, but please change it back in case of error.

Type: defect → task

igoldan: This sounds like a treeherder/perfherder issue with alerting a tier 3 job rather than an issue with AWSY. I don't see anything in treeherder's repo under perf, perfalert which mentions tier.

Flags: needinfo?(igoldan)
Type: task → defect

I also don't have a problem with this alerting, it's tier3 because mitmproxy is flaky, not because the data is bad.

Flags: needinfo?(erahm)

(In reply to Bob Clary [:bc:] from comment #2)

igoldan: This sounds like a treeherder/perfherder issue with alerting a tier 3 job rather than an issue with AWSY. I don't see anything in treeherder's repo under perf, perfalert which mentions tier.

Indeed, Perfherder doesn't check for the test's tier, when it should. I believe we need to address this.
Dave, should I file a separate bug to work on this?

Flags: needinfo?(igoldan)
Flags: needinfo?(dave.hunt)

Let's use this bug and just update the product/component. Before we work on this I'd like to publish an update of our performance regression policy, which will stipulate which tiers we monitor for regressions.

Flags: needinfo?(dave.hunt)

Over to perfherder.

Component: AWSY → Perfherder
Priority: -- → P3
Product: Testing → Tree Management
Version: unspecified → ---
You need to log in before you can comment on or make changes to this bug.