cros: Do not schedule attempt when behind captive portal with response 200 is detected
Changes: (1) Do not schedule attempt if we are already behind captive portal with response 200, which can be either the result of NetworkPortalDetector or shill's detection. In test, this can reduce the call times of CaptivePortalDetector::DetectCaptivePortal from 6+ to 2~3 within 10s. (2) modify tests to adapt this change BUG=702273 TEST=If we log in CaptivePortalDetector::DetectCaptivePortal, we can see the attempts reduced to 2~3 for connecting to captive portal wifi. Review-Url: https://codereview.chromium.org/2756643002 Cr-Commit-Position: refs/heads/master@{#457829}
Showing
Please register or sign in to comment