Use LOGE for ranging distance results errors
This is only temporary because currently the ranging distance
are unstable for results in both 2G and 5G. Change LOGE back to
sendFatalFailureToHost after the ranging distances are more stable.
Bug: 276368494
Test: pts basicWifiTest
Change-Id: Ia71a882b77ca9840685b3b6760fd5d97b247c04a
diff --git a/apps/test/chqts/src/general_test/basic_wifi_test.cc b/apps/test/chqts/src/general_test/basic_wifi_test.cc
index 4b127e8..a561eca 100644
--- a/apps/test/chqts/src/general_test/basic_wifi_test.cc
+++ b/apps/test/chqts/src/general_test/basic_wifi_test.cc
@@ -639,18 +639,18 @@
} else {
validateRssi(result.rssi);
+ // TODO(b/289432591): Use sendFatalFailureToHost to check ranging distance
+ // results.
constexpr uint32_t kMaxDistanceMillimeters = 100 * 1000;
if (result.distance > kMaxDistanceMillimeters) {
- sendFatalFailureToHost(
- "Ranging result was more than 100 meters away %" PRIu32,
- &result.distance);
+ LOGE("Ranging result was more than 100 meters away %" PRIu32,
+ result.distance);
}
constexpr uint32_t kMaxStdDevMillimeters = 10 * 1000;
if (result.distanceStdDev > kMaxStdDevMillimeters) {
- sendFatalFailureToHost(
- "Ranging result distance stddev was more than 10 meters %" PRIu32,
- &result.distanceStdDev);
+ LOGE("Ranging result distance stddev was more than 10 meters %" PRIu32,
+ result.distanceStdDev);
}
if (result.flags & CHRE_WIFI_RTT_RESULT_HAS_LCI) {
