Siarhei Vishniakou
2b5fbafd37
This will exercise the basic inputflinger pipeline for handling touch events. The purpose is to mainly serve as a template for adding future benchmarks. Also, move existing input-related benchmarks into the InputPerfTests, so that they are all in one place. This allows us to specify custom build rules like treating kotlin warnings as errors, including specific libraries, etc. Example output: com.android.perftests.input (1 Test) [1/1] android.input.TouchPerfTest#testDownMoveUp: PASSED (9.488s) downMoveUp_mean (ns): 81734303 downMoveUp_median (ns): 81343021 downMoveUp_min (ns): 75008516 downMoveUp_standardDeviation: 5514345 Bug: 396219004 Test: atest InputPerfTests Flag: TEST_ONLY Change-Id: I686c0fa6d2d5745ca0d4d69f12308331e37b818f
3 lines
73 B
Plaintext
3 lines
73 B
Plaintext
# Bug component: 136048
|
|
include /core/java/android/hardware/input/OWNERS
|