Add input tests to surfaceflinger presubmit
One of the input tests was breaking a test from SurfaceFlinger_test. The breakage only happened when it was executed before the SF test. This only ended up affecting input presubmit, where the tests are executed in this specific order. Meanwhile, input postsubmit and surfaceflinger presubmit / postsubmit were fine. The help catch these issues sooner in the future, add input tests to SF presubmit. Bug: 301657737 Test: (cd frameworks/native/services/surfaceflinger && atest) Test output (as of 2023-09-27): Finding Tests... Found 'libgui_test' as MODULE Found 'FrameworksCoreTests' as MODULE Found 'libnativewindow_bindgen_test' as MODULE Found 'libscheduler_test' as MODULE Found 'libcompositionengine_test' as MODULE Found 'SurfaceFlinger_test' as CACHE Found 'libnativewindow_rs-internal_test' as MODULE Found 'inputflinger_tests' as CACHE Found 'libgui_test' as MODULE Found 'FrameworksServicesTests' as MODULE Found 'CtsViewTestCases' as MODULE Found 'libsurfaceflinger_unittest' as MODULE Found 'CtsGraphicsTestCases' as MODULE Found 'FrameworksCoreTests' as MODULE Found 'CtsHardwareTestCases' as MODULE Found 'libinputservice_test' as CACHE Found 'CtsGraphicsTestCases' as MODULE Found 'CtsInputTestCases' as MODULE Found 'libinput_tests' as CACHE Found 'InputTests' as MODULE Found 'CtsSecurityBulletinHostTestCases' as MODULE Found 'CtsSecurityTestCases' as MODULE Found 'CtsWidgetTestCases' as MODULE Found 'libnativewindow_test' as MODULE Found 'libchrome-gestures_test' as MODULE Found 'CtsWindowManagerDeviceWindow' as MODULE Found 'CtsViewTestCases' as MODULE Found 'libpalmrejection_test' as MODULE Found 'CtsSurfaceControlTests' as MODULE Found 'CtsAppTestCases' as MODULE Change-Id: Ib518d77f495f3a037c0af5d28bff91fe0fde42ff
Loading
Please register or sign in to comment