Downgrade Log message level from WTF to WARN for null BSSID case.
Rarely ScanResultInfo might be null when starting provisioning,
for example, switch between different APs frequently. So when L2
roaming happens the current tracked bssid is null, which throws
WTF log message. Downgrade the Log level to WARN in R before WiFi
framework fixes the null BSSID issue temporarily.
Bug: 160217503
Test: atest NetworkStackTests NetworkStackIntegrationTests
Change-Id: Iec342a2c3c52c64b044c5bc56f565fa31997cd53
3 files changed