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

Issue 777733 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
█ susanjuniab@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Blue highlight traces are seen after selecting/deselecting url entries in chrome://history

Reported by vku...@etouch.net, Oct 24 2017 
Chrome Version:63.0.3239.16 (Official Build) 429b133a5af5a24d0d81d4a8b6a8f8d7d3385f13-refs/branch-heads/3239@{#157} (32/64-bit)
OS: Win(7,8,10)

What steps will reproduce the problem?
(1)Launch chrome and open 5-6 webpages(i.e. long history should be present)
(2)Navigate to chrome://history/ , select/deselect url entries and observe


Actual: Blue highlight traces are seen after selecting/deselecting url entries. 

Expected: Blue highlight traces should not be seen after selecting/deselecting url entries.

This is a regression issue broken in 'M63' and will soon update other info.
History.png
116 KB View Download
Actual_History.mp4
228 KB View Download

Comment 1 by vku...@etouch.net, Oct 24 2017

Labels: hasbisect-per-revision OS-Linux OS-Mac
Owner: xiaoyinh@chromium.org
Status: Assigned (was: Unconfirmed)
Good Build: 63.0.3209.0 
Bad Build:  63.0.3210.0 

You are probably looking for a change made after 500472 (known good), but no lat
er than 500473 (first known bad).
CHANGELOG 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/48218d16dc459752e54ba7f6cb6813199285ba03..069eea183d2ddb590c7e5e23ff786ea4ad45dffc

Suspecting: https://chromium.googlesource.com/chromium/src/+/069eea183d2ddb590c7e5e23ff786ea4ad45dffc

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 2 by ranjitkan@chromium.org, Oct 24 2017

Labels: ReleaseBlock-Stable
Tagging with blocker label, please undo if not the case.

Comment 3 by xiaoyinh@chromium.org, Oct 24 2017 

Still seeing this issue after revert the CL in question. I'm bisecting right now.

Comment 4 by xiaoyinh@chromium.org, Oct 24 2017 

I'm seeing this in M61 as well... If this is a regression, do we know which version is a good one to start bisecting?
history.png
30.4 KB View Download
version.png
27.7 KB View Download

Comment 5 by pbomm...@chromium.org, Oct 24 2017

Labels: Needs-Bisect
 vkupte@ or  ranjitkan@ can you please re-run the bisect and update the bisect details.

Comment 6 by vku...@etouch.net, Oct 25 2017

Labels: -Needs-Bisect
Owner: ----
Status: Untriaged (was: Assigned)
With response to comment #4& 5

Rechecked again and this is broken in 'M51' series below is manual bisect info
Good Build: 51.0.2668.0
Bad Build:  51.0.2669.0

CL: https://chromium.googlesource.com/chromium/src/+log/51.0.2668.0..51.0.2669.0?pretty=fuller&n=10000

Note: Unable to narrow down the range using tool bisect as getting all bad builds between this range.

Comment 7 by ranjitkan@chromium.org, Oct 25 2017

Labels: -ReleaseBlock-Stable -M-63 M-64
Removing blocker label, since broken in M51 as per above comment.

Thanks.!

Comment 8 by jochen@chromium.org, Nov 2 2017

Cc: susanjuniab@chromium.org
 Issue 777738  has been merged into this issue.
►

Sign in to add a comment