boot-block: look for a callout in the entry
phosphor-logging callouts always start with a CALLOUT_ in the additional
data entry. Look for this to determine if a callout is present in the
log.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I721e794dc4610a18705e1b0d75e545b14f844402
diff --git a/test/Makefile.am b/test/Makefile.am
index ddd42e6..8484d62 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -11,7 +11,8 @@
remote_logging_test_config \
sdjournal_mock_test \
extensions_test \
- elog_update_ts_test
+ elog_update_ts_test \
+ elog_quiesce_test
test_cppflags = \
-Igtest \
@@ -114,6 +115,14 @@
elog_update_ts_test_LDFLAGS = \
$(test_ldflags)
+elog_quiesce_test_CPPFLAGS = $(test_cppflags)
+elog_quiesce_test_CXXFLAGS = $(test_cxxflags)
+elog_quiesce_test_SOURCES = elog_quiesce_test.cpp
+elog_quiesce_test_LDADD = $(test_ldadd)
+elog_quiesce_test_LDFLAGS = \
+ $(test_ldflags)
+
+
# TODO Remove once the test-case failure is resolved openbmc/phosphor-logging#11
XFAIL_TESTS = elog_errorwrap_test