New issue
Advanced search Search tips

Issue 916986 link

Starred by 2 users
Status: Duplicate
Merged: issue 914387
Owner:
cjamcl@google.com
Closed: Dec 27
Cc:
santhoshkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Audits ignore device and network settings

Reported by brian.mc...@gmail.com, Dec 20 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/71.0.3578.80 Chrome/71.0.3578.80 Safari/537.36

Steps to reproduce the problem:
1. Create an audit for a Desktop device and no network throttling
2. Run the audit

What is the expected behavior?
The audit will be run with no device emulation at full network speed

What went wrong?
The audit is run as a mobile device and the network speed is throttled.

Here are the runtime settings:

Runtime settings
URL: [redacted]
Fetch time: Dec 20, 2018, 2:54 PM GMT+1
Device: Emulated Nexus 5X
Network throttling: 150 ms TCP RTT, 1,638.4 Kbps throughput (Simulated)
CPU throttling: 4x slowdown (Simulated)
User agent (host): Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
User agent (network): Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5 Build/MRA58N) AppleWebKit/537.36(KHTML, like Gecko) Chrome/71.0.3559.0 Mobile Safari/537.36
CPU/Memory Power: 1431

Did this work before? Yes Whatever the most current stable version was on December 4th 2018

Chrome version: 71.0.3578.80  Channel: stable
OS Version: Ubutnu 18.04
Flash Version:

Comment 1 by phanindra.mandapaka@chromium.org, Dec 20

Labels: Needs-Triage-M71 Needs-Bisect

Comment 2 by santhoshkumar@chromium.org, Dec 21

Cc: santhoshkumar@chromium.org
Labels: -Pri-2 hasbisect-per-revision Release-Block-Stable Triaged-ET Target-71 Target-72 Target-73 M-71 FoundIn-71 FoundIn-73 FoundIn-72 OS-Mac OS-Windows Pri-1
Owner: cjamcl@google.com
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on reported chrome version # 71.0.3578.80 and the issue seems to be fixed on latest chrome #73.0.3647.0 and previous stable version # 70.0.3538.110 using mac 10.14.0,windows 10 and Linux 17.10. As the issue got fixed,hence providing reverse bisect info to find where the fix has landed.  

Reverse Bisect information:
==============
Good Build: 73.0.3640.0
Bad Build: 73.0.3639.0

Change log: 
https://chromium.googlesource.com/chromium/src/+log/ecdbbab7908cd7ca9ae565eaae172527721c51d6..23c268dc95840a2fcb266f72acfa2aaf1a42b8ab
Suspecting: https://chromium.googlesource.com/chromium/src/+/23c268dc95840a2fcb266f72acfa2aaf1a42b8ab
Reviewed-on: https://chromium-review.googlesource.com/c/1374196

@cjamcl: Please confirm the issue and help in re-assigning if it is not related to your change
Adding Release-Block-Stable as this is recent regression. Please feel free to remove if not applicable.

Thanks.!

Comment 3 by santhoshkumar@chromium.org, Dec 24

Labels: -Needs-Bisect
++ correction as per comment #2 removing Needs-Bisect label

Comment 4 by cjamcl@google.com, Dec 27

Mergedinto: 914387
Status: Duplicate (was: Assigned)
►

Sign in to add a comment