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

Issue 786860 link

Starred by 1 user
Status: Duplicate
Merged: issue 786778
Owner:
billorr@chromium.org
Closed: Nov 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Chrome official Canary Build 64.0.3273.0 does not launch.

Reported by aiman.an...@etouch.net, Nov 20 2017 
Chrome Version: 64.0.3273.0 Official Build.

OS: Win(7,8,10)

Steps to reproduce:
1. Freshly install and try launching chrome.

Actual Result: Chrome browser does not launch.
Expected Result: Chrome browser should launch.

This is Regression broken in M-64 issue and will soon update other info.

Comment 1 by henkpo...@gmail.com, Nov 20 2017 

I can confirm this bug happens on Windows 10 build 16229.

Comment 3 by aiman.an...@etouch.net, Nov 20 2017

Cc: msrchandra@chromium.org ranjitkan@chromium.org rbasuvula@chromium.org nyerramilli@chromium.org
Components: OS>Installer
Labels: hasbisect-per-revision OS-Windows
Owner: billorr@chromium.org
Status: Assigned (was: Unconfirmed)
This is regression issue broken in ‘M-64’ and and will soon update the bisect info.

Using the per-revision bisect providing the bisect results,
Good build: 64.0.3272.0 (Revision: 517672)
Bad build: 64.0.3273.0 (Revision: 517724)

You are probably looking for a change made after 517683 (known good), but no later than 517684 (first known bad).

CHANGE-LOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/262a9e7bd31156e7611108447254c2e52e92956f..14d631ca392fa139a6f6b89d052d089b99758e33

Suspect: https://chromium.googlesource.com/chromium/src/+/14d631ca392fa139a6f6b89d052d089b99758e33

@billorr: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Comment 4 by msrchandra@chromium.org, Nov 20 2017

Mergedinto: 786778
Status: Duplicate (was: Assigned)
This issue looks similar to Bug Id -- 786778.
Thank You.
►

Sign in to add a comment