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

Issue 835394 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

wifi: autotest: report driver spew as "Timeout waiting for hardware access" in tests

Project Member Reported by kirtika@chromium.org, Apr 20 2018

Issue description

Two issues:
(1) We often pass a wifi autotest if the pass "criteria" are met without checking if the wifi driver or firmware crashed or had unwanted warnings
during the test. (IIRC, network_WiFi_CSADisconnect was an example)

(2) We are looking for in-house repros of the kernel warnings in iwl_trans_pci_grab_nic_access & iwl_trans_pcie_reclaim
"Timeout waiting for hardware access (CSR_GP_CNTRL 0xFFFFFFFF)

Add a hook that applies to all wifi_matfunc autotests. It checks for such spew and if found, fails the test.



 
Owner: harpreet@chromium.org
We do this for few other tests where we look for crashes and upload the count to perf dashboard. We can do something similar but expand it to include looking for specific warnings / crashes as needed and uploading crash/warning counts to perf dashboard.


Do we really want to fail the test if there is a warning or a crash? I think its better to let the test pass and add monitoring to chromeperf to generate alerts for the collected data instead. Here is an example of crash count data:
https://chromeperf.appspot.com/report?sid=b0de0da38abbf1d31534213043aae42ee359612f5095bfc966bf14ccc3ea4c10&start_rev=31630600976503700&end_rev=34050001061400000



I'll assign this to myself, unless someone else wants to take it. Won't get to it till after I am back in office (OOO next week).
Status: Assigned (was: Untriaged)

Sign in to add a comment