commit | a5dda0e9b074fa2c5a4279470f1916c66cb14013 | [log] [tgz] |
---|---|---|
author | mukesh agrawal <quiche@chromium.org> | Fri Aug 16 11:53:10 2013 -0700 |
committer | ChromeBot <chrome-bot@google.com> | Fri Aug 16 19:02:58 2013 -0700 |
tree | 48c18400518ef9c5ea32d48907c5e97617657730 | |
parent | 09e0811c0d54facab2874cfac8b3563005220c2b [diff] |
shill: don't update FrequenciesConnectedEver until we complete L2 shill has been reporting Network.Shill.WiFi.FrequenciesConnectedEver when supplicant reports a change in BSS. However, a change in BSS may only indicate the start of a connection attempt, not its success. It's probably more relevant to record the number of frequencies where we successfully connect. So change to reporting the data after the layer-2 is established. We could go further and wait until DHCP is complete, or even further, and wait until we get online. But let's keep this a layer-2 statistic for now. While there: make some EXPECTations in wifi_provider_unittest a little more specific. BUG=chromium:274595 TEST=unit tests Change-Id: I67547db507498c130a2a26822b679306ad3ede4f Reviewed-on: https://gerrit.chromium.org/gerrit/66113 Tested-by: mukesh agrawal <quiche@chromium.org> Reviewed-by: Paul Stewart <pstew@chromium.org> Commit-Queue: mukesh agrawal <quiche@chromium.org>