New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 649121 link

Starred by 2 users
Status: Assigned
Owner:
█ anan...@chromium.org
Last visit > 30 days ago
Cc:
█ jparent@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Can't use bisect-builds.py to find console output regression.

Project Member Reported by lgar...@chromium.org, Sep 21 2016 
Version: 55

I regularly file bugs because of errors that crop up when Chrome starts up on Mac (usually because someone didn't take the platform into account). For example, I just filed  Issue 649115 .

I want to bisect  Issue 649115 , but (as far as I can tell) ./tools/bisect-builds.py suppresses console output, so I can't easily use it to find the regression. It would be nice if I could.

Comment 1 by lgar...@chromium.org, Sep 28 2016

Cc: jparent@chromium.org
jparent@, can you help me kickstart triaging this to the right place?

The bisect script is one of our more useful tools, but it doesn't work with this important use case.

Comment 2 by jparent@chromium.org, Sep 29 2016

Components: Test
Labels: Manual-Bisect
I added the Test component and manual-bisect label based on past history with bisect bugs, but this falls into Anantha's area, she can likely triage more appropriately
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 29 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by lgar...@chromium.org, Oct 2 2017

Status: Untriaged (was: Archived)
Still relevant.

Comment 5 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)
►

Sign in to add a comment