Specify buffers in some calls of dlog_tests

Those tests would start failing on some targets after the libdlogutil
patches. This would be due to them trying to clear/get size of the apps
buffer, which does not exist. This was accepted before the libdlogutil
patches, because dlogutil would consider all of the enabled buffers at
the same time. However, said patches change it to clear/get size of each
buffer separately and return on the first failure. We can work around
this issue by making it so that dlogutil will not try to manipulate the
apps buffer in the failing spots.

Change-Id: I5b3135256b99b0bc8f53a14fc68f99a9effbf6c3

diff --git a/tests/dlog_test.in b/tests/dlog_test.in
index a26100f..bf02b9e 100644 (file)
--- a/tests/dlog_test.in
+++ b/tests/dlog_test.in
@@ -285,7 +285,7 @@ LOG_DETAILS="testing if reading from \"system\" buffer returns zero entries (log
 [ $(dlogutil -d -b system | wc -l) -eq 0 ] && ok || fail
 
 LOG_DETAILS="testing if dlogutil -c empties all buffers"
-dlogutil -c && ok || fail
+dlogutil -cb main && ok || fail
 
 LOG_DETAILS="testing if writing entries to empty buffer and reading them returns proper amount of entries"
 test_libdlog 10
@@ -298,7 +298,7 @@ LOG_DETAILS="testing if adding \"silent\" filter works"
 [ $(dlogutil -b main -s -d | wc -l) -eq 0 ] && ok || fail
 
 LOG_DETAILS="testing if reading buffer size returns proper exit code"
-dlogutil -g &> /dev/null && ok || fail
+dlogutil -gb main &> /dev/null && ok || fail
 
 LOG_DETAILS="testing if writing all entries to single file works (-f)"
 dlogutil -f $TESTDIR/dlog_test_file -d &> /dev/null && ok || fail