| 0ca30c27547634d0cab031526ab759da772bd355 |
|
26-Jan-2016 |
Dane Pollock <danepollock@google.com> |
autotest: Read iw event log directly from host.
Currently, the IwEventLogger is only able to read the event log file after
it has been copied to the autotest server after the event logger has been
stopped. With this change, we will read the file directly from the host,
to allow multiple checks within a single context, then copy it to the
autotest server after we exit the context.
BUG=None
TEST=Run jetstream sanity autotests which use the iw event logger.
Change-Id: If2a814c90a941e6f46ab031909ce607d01a2c729
Reviewed-on: https://chromium-review.googlesource.com/323771
Commit-Ready: Dane Pollock <danepollock@google.com>
Tested-by: Dane Pollock <danepollock@google.com>
Reviewed-by: Filipe Brandenburger <filbranden@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 570c7ddc289b63d71543387924b91012eb915189 |
|
15-Oct-2015 |
Filipe Brandenburger <filbranden@chromium.org> |
autotest (wifi): Do not try to write to /tmp on an ADBHost
Because the root filesystem is read-only and writing to /data/local/tmp
is a more appropriate location on that platform.
The file will now be placed into a subdirectory named autoserv-<random>
under the base temporary directory (be it /tmp or /data/local/tmp) for
each test run. The temporary directories all get cleaned up after the
end of the test run.
BUG=chrome-os-partner:42310
TEST=Ran network_WiFi_SimpleConnect through adb successfully.
Also ran it on samus and confirmed it did not cause any regressions.
Change-Id: I1f7e94c3aad91c05cd958698a44c491b4ed673ee
Signed-off-by: Filipe Brandenburger <filbranden@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/306115
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Bindu Mahadev <bmahadev@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 029457bea998679d3c5c8e6ad22305e925af2c2e |
|
14-Jul-2015 |
Filipe Brandenburger <filbranden@chromium.org> |
autotest: Use `nohup` to put the iw log tail command in background
Otherwise running it through `adb shell` ends up killing it with a
SIGHUP as soon as the shell is terminated.
Also redirect its stdin (to /dev/null) and stderr (dup of stdout) to
prevent the channel from staying open, which would block the script.
BUG=chrome-os-partner:42310
TEST=Ran network_WiFi_SimpleConnect through adb successfully.
Ran suite:wifi_matfunc against a Samus in a wifi cage.
Change-Id: Ia74f923b0487d6cae99d921876ebdf3d0446120c
Reviewed-on: https://chromium-review.googlesource.com/285643
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Filipe Brandenburger <filbranden@chromium.org>
Tested-by: Filipe Brandenburger <filbranden@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 7668974aa7b9968ebadf3cfbdf94280c56a2f7e2 |
|
22-Jul-2015 |
Rebecca Silberstein <silberst@chromium.org> |
autotest (wifi): Move disconnect checks to function and add a third
During tests, connection failures are checked by looking for log messages
starting with specific phrases. Consolidate these checks into a helper
function and add a third log message type.
Log messages covered now include those starting with 'disconnected' and
'Deauthenticated' and matching 'Previous authentication no longer valid'.
BUG=chromium:512928
TEST=confirmed network_WiFi_LinkMonitorFailure still passes
Change-Id: Ic1e4fc41c482af11d1b3c1aa249bab1c7bdec466
Reviewed-on: https://chromium-review.googlesource.com/287613
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Queue: Rebecca Silberstein <silberst@chromium.org>
Trybot-Ready: Rebecca Silberstein <silberst@chromium.org>
Tested-by: Rebecca Silberstein <silberst@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 4ee74511349b196a936bb56dbe0e18ee1c16b531 |
|
16-Jul-2015 |
Rebecca Silberstein <silberst@chromium.org> |
autotest (wifi): add Deauthenticated message to disconnect checks
During tests, connection failures are only counted if the message starts
with 'disconnected'. When the AP is suddenly taken down, the connection
failure may be logged as 'Deauthenticated'. The event message now
covers both cases.
BUG=chromium:510636
TEST=confirmed network_WiFi_LinkMonitorFailure still passes
Change-Id: Ia5bea977d3182da758dca2bb1f2aada95346ea02
Reviewed-on: https://chromium-review.googlesource.com/285923
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Queue: Rebecca Silberstein <silberst@chromium.org>
Trybot-Ready: Rebecca Silberstein <silberst@chromium.org>
Tested-by: Rebecca Silberstein <silberst@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| cc4bd9e0e1e62cc8cb6bd4f45b46cc24343e1941 |
|
07-Apr-2015 |
Peter Qiu <zqiu@chromium.org> |
autotest: add network_WiFi_LinkMonitorFailure test
This test checks how fast the DUT detects the link failure when the
network link goes down (restarting the local server with a different
gateway IP), and how fast it reconnects back after the failure.
BUG=chromium:469761
TEST=Run this test
CQ-DEPEND=CL:264459
Change-Id: Ibf8c74f0361798b6f099ba9c9282d96d4b0d741c
Reviewed-on: https://chromium-review.googlesource.com/264457
Reviewed-by: Zeping Qiu <zqiu@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
Tested-by: Zeping Qiu <zqiu@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| a04aa7dc31f5eb3961145c7816bcee83ad8cff65 |
|
20-Feb-2015 |
Peter Qiu <zqiu@chromium.org> |
Update disconnect event signature for start of reassociation
On some devices (broadcom and marvell), the disconnect is triggered by
the driver instead of wpa_supplicant, which means there is only
a "disconnected" iw event during the disconnect attempt. Update
the disconnect event signature to this event for the start of
reassociation.
BUG=chromium:448155
TEST=Run network_WiFi_Reassociate on all types of wifi devices.
Change-Id: I8d0e86e85d8f956459210df393f800311d22419f
Reviewed-on: https://chromium-review.googlesource.com/251410
Trybot-Ready: Zeping Qiu <zqiu@chromium.org>
Tested-by: Zeping Qiu <zqiu@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 01c974da4081c422551c369af8ebc2b76a6fb884 |
|
18-Feb-2015 |
Peter Qiu <zqiu@chromium.org> |
Update reassociate time calculation
Previously, the reassociation time is determined based on the time when
scan is started to the time when client is connected. However, in the newer
version (2.3) of wpa_supplicant, the device will first try to reconnect
(disconnect then connect) without scanning.
Update the reassociate time calculation to consider both scan attempt
and disconnect attempt as the start of reassociation, whichever appears
first in the iw event log is considered the start of reassociation.
BUG=chromium:448155
TEST=Run network_WiFi_Reassociate test for both version of wpa_supplicant
Change-Id: I9c2c71999e16b5f1eab7d902450deb1221bf8f93
Reviewed-on: https://chromium-review.googlesource.com/250840
Trybot-Ready: Zeping Qiu <zqiu@chromium.org>
Tested-by: Zeping Qiu <zqiu@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 3b39c821f3d5695c905242475c07c6a505c701fc |
|
08-Jan-2015 |
Paul Stewart <pstew@chromium.org> |
Add assertion that SimpleConnect runs with no client disconnects
In addition to detecting client deauths from the AP side, also
use a new client context object to ensure that the client never
detects a disconnect using an iw logger. To do this, refactor
the IwEventLogger to separate parsing from processing so the
same parser can be used in get_association_time() and a new
get_disconnect_count() function.
BUG=chromium:447028
TEST=network_WiFi_SimpleConnect.wifi_check11b
Change-Id: I5415d7b8edd806cdc8f58f458752097bb3c20c22
Reviewed-on: https://chromium-review.googlesource.com/239265
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|
| 1e31090a7b43c30f2d18cd3da1aba9894470af6e |
|
04-Mar-2014 |
Peter Qiu <zqiu@chromium.org> |
wpa_supplicant reassociate timing test
Test to benchmark the performance of wpa_supplicant reassociate operation.
Specifically the time taken from the start of the scan to being connected.
BUG=chromium:348673
TEST=Run this test
Change-Id: I079d75cc8ac96a9fbcd6dc2112e2b0b787d975ce
Reviewed-on: https://chromium-review.googlesource.com/188780
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Tested-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Peter Qiu <zqiu@chromium.org>
/external/autotest/client/common_lib/cros/network/iw_event_logger.py
|