Automatic backfilling should consider more recent pushes that say "Backed out" or "backout" and *not* backfilling

RESOLVED INVALID

Status

Testing
General
RESOLVED INVALID
2 years ago
2 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
We don't want to back fill if "Backed out" or "backout" is on the tip most changeset of a push.

For example:
* push X+2   <-- Back out
* push X+1
* push X     <-- We consider to back fill
* push X-1
* push X-2   <-- Regression introduced

Since push X+2 is a back out we won't back fill.
We need to query push log to determine this.


For example:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2b568650c03a
> Backed out changesets d0eee19c83cd, 0c54ee53678f, 5b202008a431, 81291b4e6dc3, acbc0d7e21cd, a7ceb6162a63 (bug 1194112) for Linux x64 Hazard failure. r=backout
> 
> Backed out changeset d0eee19c83cd (bug 1194112)
> Backed out changeset 0c54ee53678f (bug 1194112)
> Backed out changeset 5b202008a431 (bug 1194112)
> Backed out changeset 81291b4e6dc3 (bug 1194112)
> Backed out changeset acbc0d7e21cd (bug 1194112)
> Backed out changeset a7ceb6162a63 (bug 1194112) 

A push where this won't apply is "backed out" or "backout" is on one of the changesets rather than the tip most:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d55e24c983aa
(Reporter)

Updated

2 years ago
Summary: Automatic backfilling should consider more recent pushes that say "Backed out" or "backout" before backfilling → Automatic backfilling should consider more recent pushes that say "Backed out" or "backout" and *not* backfilling
(Reporter)

Comment 1

2 years ago
I believe the range refered to is this.
See the extra jit tests.

https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=26bcc6952881&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=running&filter-resultStatus=pending

https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=84e4016eb3ad&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=running&filter-resultStatus=pending

https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=0fc1b3aba102&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=running&filter-resultStatus=pending
(Reporter)

Comment 2

2 years ago
I'm going to close a bunch of bugs and start talking with sherrifs what specifically they need.
Instead of coming out with I think is needed.
(Reporter)

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.