Open Bug 1180292 Opened 4 years ago Updated 4 years ago

User gets notified of regression for push that should not be a regression

Categories

(Testing :: General, defect)

defect
Not set

Tracking

(Not tracked)

People

(Reporter: armenzg, Unassigned)

Details

It sounds like a bug to me.

As a reference:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora&revision=68399cfe3799

From dev.tools
###################################
This morning I received two regression notifications for Mozilla-Aurora: https://groups.google.com/d/msg/mozilla.dev.tree-alerts/BkWClavO43I/bhqT8odn5NMJ and https://groups.google.com/d/msg/mozilla.dev.tree-alerts/BkWClavO43I/sxHEhDp9m2YJ .

They're both pointing at a changeset I made: http://hg.mozilla.org/releases/mozilla-aurora/rev/68399cfe3799

However, that changeset is quite clearly test-only, so I'm sure it's not the cause of these regressions.

Is there someone I should specifically notify about these regressions?

##################################
The regressions are most likely due to the uplift- we mix things up way too often due to:
1) coalescing and build scheduling
2) noisy tests
3) other random things (like less noise on weekends, missing data, pgo quirks)

We keep track of all the regressions- apologies for the confusion!

As to fix this- there is not an easy way unless we don't send emails automatically when finding a regressions unless a longer list of criteria is met (ensuring all data is present, retriggered successfully to generate additional data for the test/platform).
You need to log in before you can comment on or make changes to this bug.