42ac34f7401f70c3f19ef176df7e1bc2f47396a0 |
|
26-May-2015 |
Mark Salyzyn <salyzyn@google.com> |
logd: test modernization (cherry pick from commit 62d6a2a921d5ee5cc455e6ae5e62d4ad2474fd25) Bug: 19603976 Change-Id: Ie920c128e7e6a436fea7a96c7d68bc39e13a2ad4
/system/core/logd/tests/logd_test.cpp
|
4ed16b4381e6723670575ff8da3cfe12fe74998a |
|
03-Mar-2015 |
Mark Salyzyn <salyzyn@google.com> |
Revert "logd: Add minimum time bucket statistics" This forward port reverts commit e457b74ce6ee6d799812dc2ec5e4b8b18bcd3e91 No longer as necessary once we add liblog: Instrument logging of logd write drops Although this provided an indication of how close statistically we were to overloading logd it is simpler to understand fails thus to hunt and peck a corrected value for /proc/sys/net/unix/max_dgram_qlen Change-Id: I2b30e0fc30625a48fd11a12c2d2cc6a41f26226f
/system/core/logd/tests/logd_test.cpp
|
634118e261d2a3c6f67212f43a4ec3f075d705b6 |
|
13-Sep-2014 |
Chih-Hung Hsieh <chh@google.com> |
logd: fix format-extra-args warning. Bug: 17409250 Change-Id: Id50ebb57754b12d69ed605d0e2901b8e05c607c6
/system/core/logd/tests/logd_test.cpp
|
89472df4cd799182062656352958edb12341b411 |
|
10-Jul-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: test: disable kernel LOGGER Bug: 15384806 Change-Id: I3072d6dd0618fa9ebe151c78a85eb121327f9df3
/system/core/logd/tests/logd_test.cpp
|
6e9aaae9eda474beea26802c360b45e96402399a |
|
13-Jun-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: test: deal with spam filter turned off Change-Id: I759c65e869d0c7cd81063fa7993ba3d67ef9cd06
/system/core/logd/tests/logd_test.cpp
|
0c57bd864d2353e8f03c8b128bdacb58fc5dce95 |
|
06-Jun-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: test: modernize - Correct default tense for kernel or user logger - harden code that parses the benchmark data - give more meaning to the spam filter test Change-Id: I97699037ca9d56718f53f08d22be79092fb431de
/system/core/logd/tests/logd_test.cpp
|
c61895ac3a9717dac6b24ce210aab0ccae6747f4 |
|
30-Apr-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: turn on -Werror - Deal with some -Wunused / -Wunused-variable issues Change-Id: Ic86cd7b0680868ad0536198b71a34cb19134fc21
/system/core/logd/tests/logd_test.cpp
|
e821dace4161c5fdf19d8af036381b850d0fb988 |
|
09-Apr-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: enable UID spam filter and test Change-Id: Ie9c7a744e341e6e64afa14973d4d095717c97933
/system/core/logd/tests/logd_test.cpp
|
696817d3524e2fb8bbbcc2ec3526f4383f789163 |
|
18-Apr-2014 |
Mark Salyzyn <salyzyn@google.com> |
liblog: Statistics truncated to 16384 bytes - if network read/write broken up, reassemble the pieces. - Use a 20ms poll to check if a new fragment has been sent by the other side. - fixup logd-unit-tests to take a (simplified) fragment from the liblog changes. Bug: 14164765 Change-Id: I98ff87888c119e1e8349717646d0f733e8971bc8
/system/core/logd/tests/logd_test.cpp
|
99f47a9e7c4374f2bbfc18e4a97aa7848245ea33 |
|
07-Apr-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: liblog: logcat: debuggerd: Add LOG_ID_CRASH Change-Id: Iea453764a1a4fc1661f461f10c641c30150e4d20
/system/core/logd/tests/logd_test.cpp
|
d3ba665020b3fd1923c1b9ab1d63cb3dc21430ac |
|
28-Feb-2014 |
Mark Salyzyn <salyzyn@google.com> |
logd: Add logd_test * Test statistics output, all four main log id types are checked to be present, and output is properly formatted with header (ascii new-line terminated byte count) and trailer (newline formfeed) frames. * On dev build test dgram_qlen, circumvent if liblog benchmarks executed first though. * Test if kernel and user space loggers are present, and if any content has leaked to both. * test benchmark and use it to verify worst UID pruning Change-Id: I890c89f64825956f40108de806ed750b0170ac6c
/system/core/logd/tests/logd_test.cpp
|