History log of /external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
b17f08162a554e3c1c48887cf0997e68ff458a00 18-Apr-2018 Lalit Maganti <lalitm@google.com> perfetto: cts: filter out watches from CTS tests

Cherry-picked from aosp/666901

Merged-In: Id61c068f07f811c87074b827b15d41a5b04d0261
Change-Id: Id61c068f07f811c87074b827b15d41a5b04d0261
Bug: 76210250
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
36557d88d4f957669cc9a8768bc6f2d0e7d50652 11-Apr-2018 Lalit Maganti <lalitm@google.com> perfetto: further cleanup and consolidate test code

With the introduction of test helper, integration tests have already been made much cleaner.
Now the next step is to take this further and reduce coupling between producer
service and consumer. We can do this by making the producer emit data without
the test explicitly requesting it (like ftrace) if a flag in config is enabled.

Moreover, we can also consolidate all checkpointing code inside the helper class instead
of every file defining its own.

Bug: 74380167
Change-Id: Idbe24586a4aaadb17f934f6e06c5c6d378be0ec3
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
07e104d1cd893c3bd4f7ff3706edb0cf0b3b87c2 03-Apr-2018 Primiano Tucci <primiano@google.com> Reduce binary size (1.6MB -> 600K) by removing protos/trace:lite dep

This CL removes any dependency from {traced, traced_probes, perfetto}
to //protos/trace:lite. Neither of them really require such dependency
and it causes significant binary bloat due to all the hundreds
.pb.{cc,h} generated by libprotobuf for any possible trace packet.
Specifically:

traced_probes: needs only to depend on the "zero" protos, for writing.

traced: needs the official protobuf only for the following reasons:
- Packet validation (e.g., trusted uid)
- Directly injecting some special packets (TraceConfig, uid, clocks)
Neither of them requires really the hundreds trace packets. They
can just use TrustedPacket, which doesn't pull in the other packets.

perfetto: it requires only TraceConfig, but that is a separate smaller
target.

Bug: 77316877
Test: pefetto_unittests / perfetto_integrationtests
Change-Id: I6e01b47af3313887c685ffb4614009910413bbea
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
c4c3cebfa59102b4f8cda9304c9734a5e73c6e92 29-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: refactor test code to consolidate pattern

With several types of testing now present, a clear pattern has been
established in how test code for end to end tests should be written.
This pattern involves spinning up service and producer, setting up a
test-specific trace config and then defining an intricate set of
checkpoints and RunUntilCheckpoint calls.

All of this code is duplicated and this will only get worse as we add
more benchmarks and tests to the codebase. Moreover, the
complex-appearance of the code hides the true simplicity within.

Refactor all the duplicated code into a helper file and call the
functions in this class from the four other cases where they are used
(integration test, fuzzer, benchmark and CTS).

Bug: 74380167
Change-Id: I261636b3da15b16f063e6a5dc6c293080b8ff4ac
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
200bd2e3d7f0932465e33bd161d9ed883a05c12a 26-Mar-2018 Sami Kyostila <skyostil@google.com> Record incident details into the trace

This patch records incident details from statsd (config id, config uid
and alert id) into the trace (together with the full trace
configuration) so they can be cross-correlated.

Bug: 73627502
Change-Id: Ib552a8b5977bc39f0b9e37dc79011d4d26eab65e
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
8390e5befb0a3d76043c76ca468cf45124d42b70 23-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: add benchmark variable for controlling message size

Bug: 74380167
Change-Id: If6a6467b96a9c0382cea62a36f21a4b116e9a265
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
dd95ef9d6b8a6f665dc29f55665ebaa04aad786c 23-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: use new flushing mechanisms and make variables more consistent

With the addition of benchmark and related mechanisms, we have the ability
to make test code a lot nicer to read and less hacky. Remove some of these
hacks and also start using flushing in fuzzer.

Bug: 74380167
Change-Id: I9942428700aa657b02fcc95e14c9cfb4eeea262a
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
bfc3d3eb18074ac0a39d8e4501603a601caad4d5 22-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: add end to end benchmarking

Bug: 74380167
Change-Id: I448d72492e9a2aaa1123188f38b79492d4be6851
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
9ac6bd988f6e987c1d6e2f7c5bd122e08e87cb4f 22-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: fix cts test failure after clock sync

CTS test wasn't updated in aosp/641399

Bug: 68853078
Change-Id: If696c604d372ebdf78c55370df70634f2b4090cf
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
17992c0db25fbd90a486d6ec946afbf8f3495a24 15-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: try to fix CTS (part 3)

Bug: 70524267
Change-Id: Iefd4cc800514f7a3ebb96afc16ea1dbe53408375
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc
a88807dcbf343089e9cc37440b8c5000893cf01a 05-Mar-2018 Lalit Maganti <lalitm@google.com> perfetto: add code for building/enabling cts tests

Bug: 170524267
Change-Id: I9b910def246f1fa3884f22f40bfc205ad8de2276
/external/perfetto/test/cts/end_to_end_integrationtest_cts.cc