History log of /system/core/logcat/tests/logcat_test.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
558282bfe4650f7b249f5ba0a24d3a400d67b78b 03-Apr-2017 Mark Salyzyn <salyzyn@google.com> logcatd: introduce logcatd executable

logcatd is the same as logcat, except that the -L flag, if supplied,
runs once, then the command re-runs itself without the -L flag with
the same argument set. By introducing a logcatd daemon executable
we can solve the problem of the longish reads from pstore that
sometimes occur when the system is excessively busy, starving this
background cgroup daemon as we absorb the delay in a backgrounded
init "service", rather than in a forgrounded init "exec". This would
not have been efficiently possible without the introduction of
liblogcat.

There are no doubt many flags that make no sense to run twice with,
and without, the -L flag. In the general sense we expect the caller
to perform the correct set of operations and not pick these nonsense
operations. logcatd is only supplied on engineering and debug builds
for logpersist, and is only an automated aid to triage.

Test: gTest logcat-unit-tests
Test: manual confirm logpersist functions as expected, required reboot
Bug: 28788401
Bug: 30041146
Bug: 30612424
Bug: 35326290
Change-Id: I53ba31970749daf37eef42636f039f485932416f
/system/core/logcat/tests/logcat_test.cpp
d7fb0a069d0076e08d34d54767114631de5d21a1 03-Apr-2017 Mark Salyzyn <salyzyn@google.com> logcat: Add -h and --help flags

If -h or --help argument was supplied, logcat would report the help
message but also return an error. Officially add -h and --help as
recognized flags, report all help with a (zero) success error code.
Adding this, and the associated test, was split off as a stepping
stone to resolving an issue with logcat -L or --last flag operations.

Test: gTest logcat-unit-tests --gtest_filter=*.help
Bug: 28788401
Bug: 30041146
Bug: 30612424
Bug: 35326290
Change-Id: I948e7fa4e92bd23f52717758ffd96bbd068c53d4
/system/core/logcat/tests/logcat_test.cpp
fbc0fe429b4b97011fcd0a1f1ed449371c03ea4a 24-Mar-2017 Mark Salyzyn <salyzyn@google.com> logcat: test: run 256 simultaneous logcats

For logd daemon, heavy reader stress. For system popen fork and
execute of logcat measure baseline against liblogcat. For liblogcat
local concurrent thread, locking, argument parsing and context scaling
for popen-style pair of android_logcat_run_command_thread* functions.

NB: 1000 logcat executables ran, but did not scale well on time
blocked for more than a minute. With 343 contexts of
android_logcat_run_command_thread ran out of local resources
to even return a file descriptor, and the per-context event tag
mappings coincidentally ran out at 340 when threads ran, although
that path was consistently 15% faster than the popen test.

Test: gtest logcat-unit-tests --gtest_filter=*.End_to_End_multitude
Bug: 35326290
Change-Id: I0e1a5d4f8ffbd77fa8db13d53f4d328973731895
/system/core/logcat/tests/logcat_test.cpp
d70f246f8a402024db325f15bdf398c9608d54cc 14-Mar-2017 Mark Salyzyn <salyzyn@google.com> logcat: test: tail_# occasional failures

When PID becomes 5 digits, fgetLongTime fails

Test: gTest logcat-unit-tests --gtest_filter=*.tail_*
Bug: 27319267
Change-Id: I9cc636ed9955a317eb3b0ff0a820a50b800b7e0d
/system/core/logcat/tests/logcat_test.cpp
210095136d9952e84174439389f9c3022ffd7178 14-Mar-2017 Mark Salyzyn <salyzyn@google.com> logcat: test -v epoch tail time

Test: gTest logcat-unit-tests
Bug: 35373582
Change-Id: I57d84af2eb5d1fce8753539edf3133bfe0bb7213
/system/core/logcat/tests/logcat_test.cpp
6dabc81a0b7eac772209e8eef70ff3b156e5cc6b 10-Feb-2017 Mark Salyzyn <salyzyn@google.com> liblogcat: add android_logcat_popen and android_logcat_system

Supply a wrapper to the logcat API that provides some analogous
functionality to popen and system libc calls with some bits of
KISS shell-like parsing for environment, quotes and error
redirection handling.

Test: gTest logcat-unit-tests
Bug: 35326290
Change-Id: I9494ce71267ad2b2bec7fcccfc7d4beddae9aea6
/system/core/logcat/tests/logcat_test.cpp
c0cf90d1fb6aca1e6ae6c06d4d6231dd4d47d3cb 10-Feb-2017 Mark Salyzyn <salyzyn@google.com> logcat: Create liblogcat

Try to leverage as much of logcat as-is and produce a viable
library API that others can use for their own logcat execution.

Added a test to check ANDROID_PRINTF_LOG environment variable.

Test: gTest logcat-unit-tests
Bug: 35326290
Change-Id: I30de692ea9d83e6fd6e5d9e7cf93d31401a88a40
/system/core/logcat/tests/logcat_test.cpp
5f606605ed8b1f6a0966a7d145553e228561ddf1 10-Feb-2017 Mark Salyzyn <salyzyn@google.com> logcat: Add coding style

- Android coding standard compliance with an eye to reducing merge
impact.
- resolve a few misbehaviors in logcat_test.

SideEffects: none
Test: gTest logcat-unit-tests
Bug: 35326290
Change-Id: I63d0667ad34c0df11086a6ffe94b7030430b865b
/system/core/logcat/tests/logcat_test.cpp
9b4d7e1c381289b6b6fba1794b5846e0d34da1cc 30-Jan-2017 Mark Salyzyn <salyzyn@google.com> logcat: test: inject() tuning

Add a hidden -v nsec flag to logcat (actually logprint in liblog.so)
so that we can do more exacting tests of logcat.tail_time. Halve the
spam pressure of logcat.tail_* in inject() routine, and give us a few
more retries at the higher counts. Add instrumentation to
logcat.logrotate failures. Add inject for logcat.year test.

Test: gTest logcat-unit-tests
Bug: 34454772
Change-Id: If6f3bd21892c8a2b9ccee8c8bbf592a1ae0b2a57
/system/core/logcat/tests/logcat_test.cpp
e7e21ea67faeadaebe7c5300229bffd9e6dd76f6 26-Jan-2017 Mark Salyzyn <salyzyn@google.com> logcat: test: increase retry on fgetLongTimestamp to 4, and sleep to settle to 3

Test: gTest logcat-unit-tests
Bug: 34454772
Change-Id: I8557b0f7f25c4aa160a23a2428c9b53c8e3b26e1
/system/core/logcat/tests/logcat_test.cpp
15e585853fdc97db32f46da0f0886b19f8f022d5 23-Jan-2017 Mark Salyzyn <salyzyn@google.com> logcat: test: inject messages if necessary for tail test requirements

For the gTests logcat.tz, logcat.tail_3, logcat.tail_10,
logcat.tail_100, logcat.tail_1000 and logcat.tail_time tests inject
messages if we come up short should the background logging not be
sufficient to feed the test requirements. Test frames run the
tests right after reboot requiring injection. Will have radio
silence, so we also add kernel logs if available to help add to the
background logging activity level.

We also will inject a radio message for logcat.buckets so that test
can survive no radio content.

Test: set device to airplane mode (to stress this problem) then:
adb logcat -b all -c && adb shell su root \
/data/nativetest/logcat-unit-tests/logcat-unit-tests \
--gtest_filter=logcat.tail_1000 (or others in this set)
Bug: 34454772
Change-Id: I5ec246552f3ab1fc9c5864ed69d63b851fdf538d
/system/core/logcat/tests/logcat_test.cpp
26a1facfbf5264736c1bfad357f2c417d754b43a 20-Jan-2017 Mark Salyzyn <salyzyn@google.com> logcat: do not report security buffer errors

Do not report security buffer errors if not specifically
named in the buffer list.

Test: gTest logcat-unit-test --gtest_filter=logcat.security
Bug: 34511645
Change-Id: I028d51abad0329fcf42e467b135d035b06c1d2e3
/system/core/logcat/tests/logcat_test.cpp
a46326a51c966fcd65463635c1fd4360e3d1d231 27-Dec-2016 Mark Salyzyn <salyzyn@google.com> logcat: unit test produces log stutter

logd now counts multiple identical messages, causing messages to be
held back. Stop doing that in the tests. When that filter appeared,
the logcat-unit-tests went from 23 seconds to a couple of minutes of
runtime breakign the automated testing.

Test: gTest logcat-unit-tests total time less than 1 minute.
Bug: 33845198
Bug: 33535908
Change-Id: I6145bae89b6d5e5024ef4f8fe66440c9ae53f7c6
/system/core/logcat/tests/logcat_test.cpp
472245d9625b8f0c52737aa8753524facfa211db 18-Nov-2016 Mark Salyzyn <salyzyn@google.com> liblog: move android_log_event_context class to log/log_event_list.h

rename class from android_log_event_context to android_log_event_list

Test: gTest logcat-unit-tests
Bug: 31992412
Bug: 31456426
Change-Id: Ib61cbca7d453837d64959c56b0e11f8c5edbfbdd
/system/core/logcat/tests/logcat_test.cpp
1a57ae3a7d2e33531ce26fa2d2fefaae679b6eeb 11-Nov-2016 Mark Salyzyn <salyzyn@google.com> liblog: logprint: report truncated event log contents if error

We need to accept that a log tag can contain no payload. For those
that are corrupted, and to aid debugging, report what we did manage
to interpret. Report last character as a ! for corruption, and ^
for truncation. Fix a few Android Coding standard issues.

Test: gTest logcat-unit-tests
Bug: 32903864
Change-Id: Id11bef3a7b6569305c51701dd66c45d2038d6628
/system/core/logcat/tests/logcat_test.cpp
4fd0507b20d5afcc7b67ec355dcd89df62e62fc6 18-Oct-2016 Mark Salyzyn <salyzyn@google.com> liblog: logcat: logprint support -v descriptive

Expand logprint feature to pull out the log tag description
fields, parse them and merge into the logging content. Add
-v descriptive, -v colour(british, hidden) and -v help. Also
added a unit test for the descriptive format borrowing from
event tags that have been unchanged since 2009.

Had to add -v help because we have too many undocumented
formats and format adverbs.

Test: gTest logcat-unit-tests --gtest_filter=logcat.descriptive
Bug: 31456426
Change-Id: I93a1c003b7a3f4c332544946fdedb7277919cec3
/system/core/logcat/tests/logcat_test.cpp
9fa133cc286f7d2f1c565668d7675b7d7d4bdc0e 25-Oct-2016 Treehugger Robot <treehugger-gerrit@google.com> Merge "fix regression from android_lookupEventTag_len()"
9f53cac1b4e397c42bf640eec0eed4a2ffae6f60 24-Oct-2016 Mark Salyzyn <salyzyn@google.com> fix regression from android_lookupEventTag_len()

Commit 807e40ecc9786755e2f74a7a6a9b20c812588119 'liblog: logd: Add
android_lookupEventTag_len()' which addressed a Dirty Shared memory
leak resulted in a regression. Most notably logcat <tag> stopped
working for the events log buffer.

AndroidLogEntry::tag also requires callers to check out
AndroidLogEntry::tagLen as tag is no longer guaranteed to be
nul terminated.

Test: logcat-unit-tests --gtest_filter=logcat.event_tag_filter
Bug: 31456426
Change-Id: Ibe5236131b640eb5b7e3df0ab4b5f3e25b85ad45
/system/core/logcat/tests/logcat_test.cpp
aeaaf81c2cc8366ac4f66eb3d2fc85f9b8194982 30-Sep-2016 Mark Salyzyn <salyzyn@google.com> liblog: logd: logcat: Split out log/logger.h into public and private.

log/logger.h pieces moved into log/log.h. Correct for some
minor Android Coding standards.

Test: gTests liblog-unit-tests, logd-unit-tests and logcat-unit-tests
Bug: 19235719
Bug: 26552300
Bug: 31289077
Bug: 31456426
Change-Id: I0a19fd8788eec20a582e72e4c62c04534bdb1b9a
/system/core/logcat/tests/logcat_test.cpp
56cddcd72eb65ee1b172480d9f5634b60774755b 12-Oct-2016 Mark Salyzyn <salyzyn@google.com> logcat: test: report system(command) details

Provide more details regarding test failures

Test: manual, forced a failure, reports actual command issued
Bug: 30566487
Change-Id: I2431dbd335685b5eaef54ba6bd688b8588018aa9
/system/core/logcat/tests/logcat_test.cpp
0dd4431072cce3c62876b728cb20aa5b77b11a8d 29-Sep-2016 Mark Salyzyn <salyzyn@google.com> logd: logcat: Replace log/log.h with android/log.h

Should use android/log.h instead of log/log.h as a good example
to all others.

Test: Compile
Bug: 26552300
Bug: 31289077
Change-Id: If4c9711eb57267d4707b03d54a932af9de241b13
/system/core/logcat/tests/logcat_test.cpp
004cd3c55def10a92888295a9bad5fd0a18b725e 28-Sep-2016 Mark Salyzyn <salyzyn@google.com> liblog: logd: logcat: deprecate log/log_read.h

Always used in combination with log/logger.h except in log_time.cpp,
and not used externally. As a result liblog has to support stl, a
small price to pay since goal is to convert liblog to C++ internally.

Test: compile
Bug: 31456426
Bug: 26552300
Bug: 31289077
Change-Id: I72828ec807d0a2c8e40bbdebd7a69f147a7ca5a9
/system/core/logcat/tests/logcat_test.cpp
02687e75b0d17ef08ab834553ba2fa3699fba09e 03-Aug-2016 Mark Salyzyn <salyzyn@google.com> logcat: add --id=<id> for -f option

Clear file rotate content if id signature changes. This allows
logcatd to detect change of property ro.build.id to reset the
recorded data. The id is stored in the the -f filespec as
<filespec>.id.

If the id file is missing or unreadable, do not clear. Allow an
API where chmod 0 to the id file blocks this feature. Does not
work for root.

Add logcat.logrotate_id gTest.

Bug: 30591615
Change-Id: I895749ca7c6d4af57ec57f058a29d8e3af2f8b27
/system/core/logcat/tests/logcat_test.cpp
b7d059bb2f4e480d2787cf41e03ef85b75503910 06-Jun-2016 Mark Salyzyn <salyzyn@google.com> logcat: clear when specifying file output

If -c and -f are both specified, clear the files rather
than notifying the logger to clear its data. The -f then
acts like a switch between clearing the in-memory log
data, or the on-disk logrotate data.

Bug: 28936216
Change-Id: Ib1d1fb46ea09f81a2fd9bebb6c8f0f9f2355f6e8
/system/core/logcat/tests/logcat_test.cpp
1325ebfab2e490b7cb22900be2a859b133acb6eb 07-Jun-2016 Mark Salyzyn <salyzyn@google.com> Revert "logcat: expand -n, -r and -b"

This reverts commit 33c262513f67d18a7a95d6cd0ec870f0d50dce86.

Bug: 28120456
Bug: 22654233
Change-Id: I2a13f009d9e08dc2389b9872e45e95e0563af22f
/system/core/logcat/tests/logcat_test.cpp
e7e5f1b6aede24e47e49d3a668f5d386814ab02a 29-Apr-2016 Mark Salyzyn <salyzyn@google.com> logcat: confirm -g result after -c

Bug: 28451229
Change-Id: I43a1721ae991cc1316335ba4b3b868b904926d42
/system/core/logcat/tests/logcat_test.cpp
33c262513f67d18a7a95d6cd0ec870f0d50dce86 12-Apr-2016 Mark Salyzyn <salyzyn@google.com> logcat: expand -n, -r and -b

- Add property expansion to the -n/--rotate-count,
-r/--rotate-kbytes and -b/--buffer parameters.
e.g. -r '${logcat.rotate-count:-6}' will expand the property
logcat.rotate-count, and if not present will default to 6
- Add gtest to confirm mid-stream expansion
- No longer support ",:;<whitespace>" for buffer tokenization,
settling on only supporting ",".

Bug: 28120456
Change-Id: I7ebb6146f72047631536c457952fa50d0abb98ab
/system/core/logcat/tests/logcat_test.cpp
45177732966d82a9ee8d558f9b115e061e0c7208 11-Apr-2016 Mark Salyzyn <salyzyn@google.com> logcat: allow comma-separate list of buffers

- Add parsing to support comma+ separated list of buffers.
- Move get_size test into a standalone get_groups function
- add some additional tests for this feature, leveraging
get_groups to confirm buffer selection.

Bug: 28120456
Change-Id: I0b42736c08cf4b2a435cb74cda540dc163a26bd1
/system/core/logcat/tests/logcat_test.cpp
3842b1a5f6f12bd1ffb885940aa88a7bb959e58d 12-Apr-2016 Mark Salyzyn <salyzyn@google.com> logcat: apct test failures

Bug: 27241615
Change-Id: I100a5071c059fe9fa85bbdc33db552b16d7bdf60
/system/core/logcat/tests/logcat_test.cpp
c18c2130d036b115b222860366a97e26a2a1c038 01-Apr-2016 Mark Salyzyn <salyzyn@google.com> logcat: -f <non-existent-directory>/<filename> segfaults

- Check if the result of opendir is NULL in lastLogTime
- Cleanup: alphabetically sorted long options, reserved
an alias for --regex
- Add a unit test, non existent directory should return
gracefully with an exit(1) and not SIGSEGV.

NB: This failure was with eng/debug feature logpersist
turned on, /data/misc/logd/ directory was missing,
deleted, or temporarily inaccessible.

Bug: 27954627
Change-Id: I60246a53b02fdd7e5490fe458b02ad7b14843584
/system/core/logcat/tests/logcat_test.cpp
6ac498d4bbfe262595a77bacb2df9bda2c128222 17-Mar-2016 Casey Dahlin <sadmac@google.com> logcat: Add --max-count option

This new option causes logcat to quit after it prints N messages.

Test: New unit test passes
Bug: 27706081
Change-Id: Ie52ddf300160a041e68a6bac0ae7ade68bb28a7c
/system/core/logcat/tests/logcat_test.cpp
dc42a8734e5394eef022984de528718e195a0e8e 18-Mar-2016 Casey Dahlin <sadmac@google.com> logcat: Add --regex option

You can now filter log output by a regex on the messages.

Test: New unit test passes
Bug: 27706081
Change-Id: Idfa637f62a25fb1b92e9b49b89572dff0fec6e08
/system/core/logcat/tests/logcat_test.cpp
588a2cad7faee54bfb16050d0c7398709f304fea 18-Feb-2016 James Hawkins <jhawkins@google.com> system/core: Cleanup direct calls to opendir by containing in a
std::unique_ptr.

Bug: 26643633
Change-Id: Ia3491fdbff086558da694ae949cf08e4c89d0307
/system/core/logcat/tests/logcat_test.cpp
8beb0d3ad7b00f47e655f126d619bfaa59334b30 15-Dec-2015 Mark Salyzyn <salyzyn@google.com> logcat: test: rotated logs can exceed size during crash

Some crash messages can be as large as 4K, so allow
the rotated logs to have a larger size.

Change-Id: I20ef8d526ad2d5eca128d1f99f4ea2d2da426403
/system/core/logcat/tests/logcat_test.cpp
ba7a9a016bf011fdf45b6736d4c6d6795faba9d3 02-Dec-2015 Mark Salyzyn <salyzyn@google.com> logd: liblog: logcat: switch to android_log_clockid() (2)

android_log_timestamp returns the property leading letter,
it is better to return a clockid_t with android_log_clockid()

Bug: 23668800
Change-Id: I38dee773bf3844177826b03a26b03215c79a5359
/system/core/logcat/tests/logcat_test.cpp
9e18cdcebd893fbbb2369d893be219a7d832865f 07-Dec-2015 Mark Salyzyn <salyzyn@google.com> Revert "logd: liblog: logcat: switch to android_log_clockid()"

This reverts commit 77b5696b1dea6f7afed89e113e479f4a131c14fc.

Change-Id: I7711bf1a7e3f72ed29a2498d7287b725a0e624bd
/system/core/logcat/tests/logcat_test.cpp
77b5696b1dea6f7afed89e113e479f4a131c14fc 02-Dec-2015 Mark Salyzyn <salyzyn@google.com> logd: liblog: logcat: switch to android_log_clockid()

android_log_timestamp returns the property leading letter,
it is better to return a clockid_t with android_log_clockid()

Bug: 23668800
Change-Id: I3c4e3e6b87f6676950797f1f0e203b44c542ed43
/system/core/logcat/tests/logcat_test.cpp
b6bee33182cedea49199eb2252b3f3b442899c6d 08-Sep-2015 Mark Salyzyn <salyzyn@google.com> liblog: logd: support logd.timestamp = monotonic

if ro.logd.timestamp or persist.logd.timestamp are set to the value
monotonic then liblog writer, liblog printing and logd all switch to
recording/printing monotonic time rather than realtime. If reinit
detects a change for presist.logd.timestamp, correct the older entry
timestamps in place.

ToDo: A corner case condition where new log entries in monotonic time
occur before logd reinit detects persist.logd.timestamp, there
will be a few out-of-order entries, but with accurate
timestamps. This problem does not happen for ro.logd.timestamp
as it is set before logd starts.

NB: This offers a nano second time accuracy on all log entries
that may be more suitable for merging with other system
activities, such as systrace, that also use monotonic time. This
feature is for debugging.

Bug: 23668800
Change-Id: Iee6dab7140061b1a6627254921411f61b01aa5c2
/system/core/logcat/tests/logcat_test.cpp
9812fc4bd0b92baeb8f1cad6abdc440512e3cf40 06-Oct-2015 Mark Salyzyn <salyzyn@google.com> logcat: continue where we left off

Issue introduced as part of new logcatd functionality in
commit f3555d9427425c2cba9600ceffb49305c440aa4a

Faulty logic, add a gTest to confirm.

Bug: 19608716
Change-Id: Ic1b97def25e03e69faae4398a3dff2ff0f88545e
/system/core/logcat/tests/logcat_test.cpp
f28f6a9ba228803b402ebaccb59f1b2f2fd4af92 31-Aug-2015 Mark Salyzyn <salyzyn@google.com> liblog: logcat: Add year and zone to date on each line

- '-v year' modifier adds the four digit year prefix
- '-v <timezone>' modifier sets and prints the timezone suffix
- Only promise in logcat to support UTC as a timezone since
all others are based on the configured environment
- '-v zone' modifier toggles the timezone suffix on or off
- '-T YYYY-MM-DD HH:MM:SS.mmm...' format is added

Bug: 23668700
Change-Id: I7521c1efb7455dc9a25434fce72a69a65dcf72ea
/system/core/logcat/tests/logcat_test.cpp
9c51243d8bbcc5ee65dd6f7adc031e410ba5e86b 09-Mar-2015 Mark Salyzyn <salyzyn@google.com> logcat: test: logcat.logrotate fails

Test did not handle all possible multiples of block sizes.

Bug: 19604106
Change-Id: I693358be9598926389631baf21c5883e0f2fd735
/system/core/logcat/tests/logcat_test.cpp
1eca6a91a10a42662afd3d507867f8fedea0f29c 23-Nov-2014 Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> Remove unused variable

Change-Id: Ifba91dd93a9c8170f8837c413756554e117be894
Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org>
/system/core/logcat/tests/logcat_test.cpp
eba7344fc1aca4ae232b881fdf6c5b16e6f59bc9 17-Oct-2014 Aristidis Papaioannou <aristidis@google.com> Made suffix length of rotated logcat files constant.

The suffix now uses as many digits as needed to cover the maximum number
of rotated files.

eg, for 20 files it would use 2 digits: log_file.{01,02,03,...,20}

Change-Id: I4709b3cf4bf88c209db3c4d9e24a3a4731c98bae
/system/core/logcat/tests/logcat_test.cpp
a5e2429f09295dd94b0ae2125e380cfb3b02ab04 18-Sep-2014 Mark Salyzyn <salyzyn@google.com> logcat: tests: deal with -v threadtime default

- specify -v brief where necessary to preserve tests
- fix an occasional issue for logrotate and device block size

Change-Id: I09b02cc0359dc351a89311abc3ee762a0f23582c
/system/core/logcat/tests/logcat_test.cpp
d03caa23ddd8670ccd83eaf4ef4fc0c78e065c1b 10-Jul-2014 Mark Salyzyn <salyzyn@google.com> logcat: test: logrotate flags

- test -f -n and -r flags
- fix issue with parse error for sizes in bytes (no multiplier)

Bug: 16147190
Change-Id: Iadf2fd903d5e881d02f1d2b491441cc8090ee1c9
/system/core/logcat/tests/logcat_test.cpp
9879ac8e1290d744fc4363e6a976516053d5f64d 03-Jun-2014 Mark Salyzyn <salyzyn@google.com> logcat: test: modernize

- split sequential sort output test out as a benchmark check
- Allow up to two failures of sort results because of occasional reader locks.
- logcat -g output was changed to handle wider set of values incorporating a
multiplier for UX, and would not pass test if 'logcat -G 1M' was run.
- If spam filter is turned off, prune checks would fail, allowed for an
empty default.

Change-Id: I06d6089e18279df7525d1c16a1f76b3125ddbf05
/system/core/logcat/tests/logcat_test.cpp
b149e245c8ccd90b52227f3d07ab572080afac53 30-Apr-2014 Mark Salyzyn <salyzyn@google.com> logcat: turn on -Werror

- Deal with some -Wunused issues

Change-Id: Ic4ab9a49f13e156a73d40266e413dee3e6396178
/system/core/logcat/tests/logcat_test.cpp
1c950479393d42d18829d4009dbdb3a7f03acbb7 02-Apr-2014 Mark Salyzyn <salyzyn@google.com> logd: liblog: logcat: enable prune features for user

- Enable whitelist, blacklist and logsize tuneables for user

Change-Id: Id0c283844c71c5263a8cfbebf2e550f7ac415858
/system/core/logcat/tests/logcat_test.cpp
ef7c411ac384665fba6209f6b26d83932f9de576 11-Mar-2014 Mark Salyzyn <salyzyn@google.com> logcat: test arbitrary time to tail

- Add tail_time
- Use EXPECT instead of ASSERT to provide more coverage
- Use EXPECT_TRUE/ASSERT_TRUE when comparing NULL
- Itemize order complaints in sorted_order test

Change-Id: I55a7543fa3300c0a9524fac70111e680c2877eea
/system/core/logcat/tests/logcat_test.cpp
5fef7b6e31c22657dbd0294f0455d6adc6762ade 19-Mar-2014 Mark Salyzyn <salyzyn@google.com> logcat: timed tests fail under load

Change-Id: Ic1cdf0509617720eef7a3ad0b17a3b6f88c9d87e
/system/core/logcat/tests/logcat_test.cpp
22e287df0dfbc6e10c02f570d2fc0c42a2a6b7aa 21-Mar-2014 Mark Salyzyn <salyzyn@google.com> logcat: white and blacklist failure

- logcat improperly squashes out count
- logcat test enhanced to catch failure
- logd places entries in ascending sorted order

Change-Id: If39d8e2c40852b520c98e7840034ab63c2538e5d
/system/core/logcat/tests/logcat_test.cpp
95cfc7b8e2e6e5c6cdc97989563e49208915a583 11-Mar-2014 Mark Salyzyn <salyzyn@google.com> logcat: test White Black list

Change-Id: Ia9509ad09dd86e4d9169ed7d0b33911f1ca9eec6
/system/core/logcat/tests/logcat_test.cpp
9b986497e7f19a7fde9e35eb73d765f4a09dee07 22-Jan-2014 Mark Salyzyn <salyzyn@google.com> logcat: test: add clear and blocking check

(cherry picked from commit 1beb2ab6f6f7cec157b25a2e728c6de8c6be58c4)

Change-Id: I243b1338c4a5935a297a0519c03697fd828e47e6
/system/core/logcat/tests/logcat_test.cpp
5d3d1f17dbcb01aedd510b5435ebdaf1d6afc138 09-Dec-2013 Mark Salyzyn <salyzyn@google.com> logcat: Add -T flag (-t w/o assumption of -d)

(cherry picked from commit de02546e3d7c9c307e3d87e0a7fe8bb39b363a72)

Change-Id: I49763e2db83755e0b7b12dfa3f83a3957c54d389
/system/core/logcat/tests/logcat_test.cpp
65772ca7d7b61b111e75fb0f66f43966f0794bbd 13-Dec-2013 Mark Salyzyn <salyzyn@google.com> logcat: Add logcat test suite

(cherry picked from commit 2807db9a269baaa7b3f67c337d3312877ba90aa0)

Change-Id: Ic4c84b88b8d899965c9765bdc3ee223ef73ba7d1
/system/core/logcat/tests/logcat_test.cpp