inputflinger: add WM SurfaceControlViewHostTests to TEST_MAPPING
These were broken by an input change a while back, but then change If2d86b044ae48f5acee0b9b37f34c8c71ab629eb added the wrong SurfaceControlViewHostTests to the mapping (as there are two test classes with the same name in different suites). Bug: 353528074 Test: $ atest WmTests_SurfaceControlViewHostTests Flag: TEST_ONLY Change-Id: I3b6ec09583715cb59838650f42cf263748b0ee51
Loading
Please register or sign in to comment