Automatic bug number selection chose the wrong bug from an inbound range with a backout

NEW
Unassigned

Status

Testing
mozregression
2 years ago
2 years ago

People

(Reporter: mstange, Unassigned)

Tracking

Version 3
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
> 89:50.00 INFO: Narrowed inbound regression window from [c23714f8, 5f285352] (3 revisions) to [7448a727, 5f285352] (2 revisions) (~1 steps left)
> 89:50.00 INFO: Oh noes, no (more) inbound revisions :(
> 89:50.00 INFO: Last good revision: 7448a7275cd7648a609266b0df3385edc5328c2c
> 89:50.00 INFO: First bad revision: 5f2853528bbf4859ca122e944243cf596144283d
> 89:50.00 INFO: Pushlog:
> https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7448a7275cd7648a609266b0df3385edc5328c2c&tochange=5f2853528bbf4859ca122e944243cf596144283d
> 
> 89:51.07 INFO: Looks like the following bug has the changes which introduced the regression:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1127703
> 

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7448a7275cd7648a609266b0df3385edc5328c2c&tochange=5f2853528bbf4859ca122e944243cf596144283d contains two bugs that landed, but one of them got backed out again, and mozregression picked the one that got backed out again instead of the one that stuck.
You need to log in before you can comment on or make changes to this bug.