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

Issue 602716 link

Starred by 3 users
Status: Verified
Owner:
█ ejcaruso@chromium.org
Last visit 15 days ago
Closed: May 2016
Cc:
█ pstew@chromium.org
█ quiche@chromium.org
█ samueltan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Remove progressive scan code from shill

Project Member Reported by ejcaruso@chromium.org, Apr 12 2016 
The progressive scan code, and associated ScanSession code, is dead. We should be able to remove it and simplify the scan logic.

Comment 1 by samueltan@chromium.org, Apr 12 2016

Cc: quiche@chromium.org
+quiche@, who has context on this code.

Comment 2 by quiche@chromium.org, Apr 12 2016 

SGTM.

Comment 3 by quiche@chromium.org, Apr 12 2016 

(The goal of progressive scan was to optimize time-to-connect. With Lucid Sleep in place, this is less of an issue... The device stays connected more of the time.)

Comment 4 by ejcaruso@chromium.org, May 12 2016

Status: Fixed (was: Assigned)
CL:343547 contains these changes. Progressive scan is now gone.

The one bit of cleanup left is removing the ScanType enum. I'll file another bug for this and work on it after the fork happens.

Comment 5 by patricia@chromium.org, May 23 2016

Labels: VerifyIn-52

Comment 6 by aashuto...@chromium.org, May 25 2016

Status: Verified (was: Fixed)
Closing as verified.
►

Sign in to add a comment