tree 58855fa9dcdc73e0a17c9b240c43111e4f7a3aa4
parent 7fa74425ce5cc2d1e2636a1c103199e3201f8ce0
author Yigit Boyar <yboyar@google.com> 1635973936 -0700
committer Yigit Boyar <yboyar@google.com> 1636065048 -0700

Add test infra to create profile scenerios

Currently, we only have a way to run profile tests on compilation, which
prevents us from creating more specific test scenerious.

This CL introduces a new rule that works with profile.sh to capture
profiling data from tests.

It is composed of two parts:
profile.sh: Previoulsy, profile.sh always attached to the gradle
compilation, which does not cover tests since they are run on a forked
process. Instead, now it has a new `target` parameter where the caller
can specifiy the target jvm process to attach (limited to gradle or
test).
ProfileRule: This is a test rule for tests to report trace sections.
When running compilation tests, most time is spent in actually compiling
the code and we don't care about that. ProfileRule adds a `trace` method
that can be used to mark trace sections. These trace call stacks are
automatically filtered by profile.sh to generate the report only
including them.

I've also added a simple profile test that obtains a raw type to
validate the performance improvements in the previous change.
(I792f643a80294a65bf55572cc4872b4a8af4e1b7).

Bug: 204923211
Test: RawTypeCreationScenarioTest
Change-Id: Id78d1266dc9815eb7eba2dbff4fd27b001e7b022