Capture event log

This test, and the code it is testing, makes use of the event log -
looking for specific info in it, and writing to it.

Make sure we capture the event log during runs of the test so that we
have some chance of diagnosing falures.

Cherry picked I610c7ddd67381d04c35fd42343e21098c150beb5 to master due to b/286408867.

Code was merged via `-s ours` and is missing even though the sha exists on the target branch. Cherry pick is required to bring in the code.

Manually remove the "Merged in" directive to allow for downstream propagation.

Bug: 239817928
Test: N/A
(cherry picked from https://android-review.googlesource.com/q/commit:2f8ca4afb39395458ed806200db7f1b1ba83cbe0)
Change-Id: I6b8c0bfe3bd6141e82ccee910001475b84565a0f
This commit is contained in:
Alan Stokes
2023-06-07 10:48:45 +01:00
committed by Brian Egizi
parent 62b74f09eb
commit 313aa6f588

View File

@@ -22,6 +22,9 @@
<option name="test-suite-tag" value="apct"/>
<option name="test-tag" value="DynamicCodeLoggerIntegrationTests"/>
<!-- This test make uses of the event log, make sure we capture it. -->
<option name="logcat-options" value="-b all" />
<test class="com.android.tradefed.testtype.AndroidJUnitTest">
<option name="package" value="com.android.frameworks.dynamiccodeloggertest"/>
<option name="runner" value="androidx.test.runner.AndroidJUnitRunner"/>