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

Issue 816360 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: [DevTools] Unable to run audit on any "https/http" page

Reported by shruti.j...@etouch.net, Feb 26 2018

Issue description

Chrome Version:66.0.3355.0 (Official Build)   Revision	31d0bb0369f909177f2ce90b439f296bcf9c90cb-refs/heads/master@{#539001} (64-bit) 

OS: Windows (7,8,8.1,10) MAC(10.12.6)
 
Steps to reproduce:

(1) Launch chrome and navigate to NTP
(2) Press F12 and run audit and observe.

Actual Result:Unable to run audit on NTP.
Expected Result:Audit should work on NTP.

Thank You!








 
Actual_video.mov
1.7 MB View Download
Components: Platform>Apps>DevTools
Labels: hasbisect-per-revision RegressedIn-66 FoundIn-66 Target-66 OS-Linux
Status: Untriaged (was: Unconfirmed)
Summary: Regression: [DevTools] Unable to run audit on any "https/http" page (was: Regression: Unable to run audit on NTP.)
Updates:
This issue is also reproducible on Mac(10.13.1,10.13.4)and Linux(14.04 LTS) machines.

Below is manual regression range:

Good build: 66.0.3353.0(Revision:538678)
Bad Build:  66.0.3354.0(Revision:538971)

Using per-revision bisect providing the bisect results:

You are probably looking for a change made after 538940 (known good), but no later than 538944 (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/d4e8300ba0adc54a81d19fecdc381dc8ff0cbfd5..25072f82f7cf45bdeaa8e667d8eb4b9445b80f95

Note:
1.Bisected four times on different machines, but was Unable to find correct suspect. Requesting Dev team to look into this issue and kindly help me to  assign it to appropriate owner.
2.Issue is not reproducible on Chromium builds.

Thank You!

Actual.mp4
1.8 MB View Download
Expected.mp4
1.5 MB View Download
Updated Steps to reproduce:

(1) Launch chrome and navigate to any any "https/http" page
(2) Press F12 and run audit and observe.

Actual Result:Unable to run audit on  any "https/http" page
Expected Result:Audit should work on any "https/http" page

Thank You!
Cc: pbomm...@chromium.org
Labels: ReleaseBlock-Stable
marking as RBS, please change if required
Labels: OS-Chrome
Able to reproduce the issue on 66.0.3356.0/CrOS 10443.0.0 - Kip
Cc: phulce@chromium.org
CC'ed respective dev(Platform>devtools) to take a look.
phulce@,
Could you please take a look & reassign to the right owner if it is not related to your change.

Thanks in advance..!

Comment 6 by phulce@chromium.org, Mar 19 2018

Mergedinto: 747349
Status: Duplicate (was: Untriaged)
There are two issues going on here, that explain different manifestations of this but all are related to the fact that audits is a remote module.

1) The bisect is struggling to identify because the issue was infra-related. Remote module building was broken for ~5 days in February which means that all Chrome builds built during that time period are missing audits functionality. This was fixed and all Mac/Windows builds should've been fine going forward. I'm unable to reproduce on newer versions. 
2) Remote modules do not work at all on CrOS. https://bugs.chromium.org/p/chromium/issues/detail?id=747349

I'll merge this into the tracking issue for #2 since #1 should be a non-factor at this point, but if anyone else is able to repro for 66.0.3359.x or later on Mac/Windows, please notify ASAP as we'll need to re-investigate!

Sign in to add a comment