Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit d85b2e28 authored by Nataniel Borges's avatar Nataniel Borges
Browse files

Log WM trace on frame instead of transaction 

Logging all transactions of WM lead to logging inconsistent states that are not sent to SF nor visible to the end user. This information increases the flakiness of the test.

Logging only on frame means that the log will only contain the information sent to SF.

Test: atest FlickerTests WMShellFlickerTests
Bug: 167521849
Change-Id: I16624181ebd127482724439fff84d4bca7fe9ab3
parent 00964166

libs/WindowManager/Shell/tests/flicker/AndroidTest.xml

+2 −0
Original line number Diff line number Diff line
@@ -11,6 +11,8 @@ 
        <option name="force-skip-system-props" value="true" />

        <!-- set WM tracing verbose level to all -->

        <option name="run-command" value="cmd window tracing level all" />

        <!-- set WM tracing to frame (avoid incomplete states) -->

        <option name="run-command" value="cmd window tracing frame" />

        <!-- restart launcher to activate TAPL -->

        <option name="run-command" value="setprop ro.test_harness 1 ; am force-stop com.google.android.apps.nexuslauncher" />

    </target_preparer>

tests/FlickerTests/AndroidTest.xml

+2 −0
Original line number Diff line number Diff line
@@ -11,6 +11,8 @@ 
        <option name="force-skip-system-props" value="true" />

        <!-- set WM tracing verbose level to all -->

        <option name="run-command" value="cmd window tracing level all" />

        <!-- set WM tracing to frame (avoid incomplete states) -->

        <option name="run-command" value="cmd window tracing frame" />

        <!-- restart launcher to activate TAPL -->

        <option name="run-command" value="setprop ro.test_harness 1 ; am force-stop com.google.android.apps.nexuslauncher" />

    </target_preparer>