Track send failures in timing reports
Previously, there was no external indication of the number of
failed sends. Start tracking failures by cause, so that
we have at least some visibility.
Change-Id: Ia66c9a8fa7bb580b786d435ce3dbdca242e2c80f
Signed-off-by: James Kuszmaul <james.kuszmaul@bluerivertech.com>
diff --git a/aos/events/logging/logger_test.cc b/aos/events/logging/logger_test.cc
index c346854..42ba12f 100644
--- a/aos/events/logging/logger_test.cc
+++ b/aos/events/logging/logger_test.cc
@@ -3393,9 +3393,9 @@
}
constexpr std::string_view kCombinedConfigSha1(
- "b33e522a2d0d746f5e514c3a9799987d9c79b2cc45c66f0a91c7a879d5248f0e");
+ "ad71114d104afea6cc400f3a968bb69e394681183fd42655d4efcdc8f4cd8911");
constexpr std::string_view kSplitConfigSha1(
- "0f36fe738e357c65082ced1b5d8179e70cb9e2ac6638e748279619db523aec1c");
+ "cdd60ecc4423ef2450bf67bed059f2f28f0e8ff6819b94a2194d825a6b15fe91");
INSTANTIATE_TEST_SUITE_P(
All, MultinodeLoggerTest,