init_kill_services_test: also reboot after
See details in comment inside. This is to increase stability of the device. There are some thing we might not detect (yet) but which cause the test to fail. Bug: 156380383 Test: run on walleye Change-Id: Ic0189af7e818916665a2b709d440c517a04c587f
This commit is contained in:
parent
bd68757d44
commit
d642fe4985
1 changed files with 10 additions and 1 deletions
|
@ -18,7 +18,16 @@
|
|||
<option name="test-suite-tag" value="apct-native" />
|
||||
|
||||
<!-- cannot be autogenerated: b/153565474 -->
|
||||
<target_preparer class="com.android.tradefed.targetprep.RebootTargetPreparer" />
|
||||
<target_preparer class="com.android.tradefed.targetprep.RebootTargetPreparer">
|
||||
<!-- flake mitigation, in case device is in bad state-->
|
||||
<option name="pre-reboot" value="true" />
|
||||
<!-- sometimes device gets into bad state, and we don't detect it in this test,
|
||||
so the test succeeds and the next test fails. This is a really bad result, so
|
||||
to avoid that, making sure we reboot the device again before running any more
|
||||
tests.
|
||||
TODO(b/152556737): add metrics for successful device recovery -->
|
||||
<option name="post-reboot" value="true" />
|
||||
</target_preparer>
|
||||
|
||||
<target_preparer class="com.android.tradefed.targetprep.RootTargetPreparer"/>
|
||||
|
||||
|
|
Loading…
Reference in a new issue