New issue
Advanced search Search tips

Issue 664494 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug


Sign in to add a comment

Bisect failures unclear after refactor

Project Member Reported by sullivan@chromium.org, Nov 11 2016

Issue description

I'm having a lot of trouble understanding bisect results from the refactor. This is a meta-bug for weird results; I'm blocking it on the sub-bugs. To keep the feature launched we need to be able to triage these bisects to the point where we can:
1) File clear bugs on problems in bisect itself
2) File clear bugs on external failures (infra issues, test issues) to the point that test authors, troopers, infra labs, etc can understand the problems and address them easily.
 
Blockedon: 664496
Blockedon: 664497
Blockedon: 664501
Blockedon: 664503
Blockedon: 664516
Blocking: 616932
Blockedon: 664710
Blockedon: 664743
Blockedon: 664765
Blockedon: 665439
Status: Started (was: Untriaged)
Blockedon: 667813
Blockedon: 666447
Components: Speed>Bisection
Owner: ----
Status: Available (was: Started)
This issue has been marked as started, but has no owner. Making available.

Sign in to add a comment