diff options
| author | JW Wang <wangchun@google.com> | 2019-10-31 10:08:47 +0800 |
|---|---|---|
| committer | JW Wang <wangchun@google.com> | 2019-11-01 01:31:13 +0000 |
| commit | 282b6f505a1d3caaae758646c305054ba12297e6 (patch) | |
| tree | e1f76505833b1f8edcbbd912c00141c5a7a9a9a9 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | d19566312ecdfc0ed865c33bffaaad77e1751665 (diff) | |
Disable testNetworkPassedDoesNotRollback
This is an effort to fix flaky StagedRollbackTest.
My local tests show that the crash has something to do with repeatedly
turn on/off network connection for each test. Several things are done
below to reduce the flakiness:
1. Disable testNetworkPassedDoesNotRollback
It sometimes takes more than 5 minutes for the device to be back
online after turning on the network connection during the test. This
test contributes a lot to the flakiness. Let's disable it for now so
other tests can keep running.
2. Rewrite testNetworkFailedRollback so we only turn on/off network
connection when necessary in the hope to reduce the WifiHandlerThread
crash. The change works pretty well for my local tests which run over
40 loops without a single failure.
Bug: 143514090
Test: atest StagedRollbackTest
Change-Id: I9aec5eafdd3368ef76517e3b8500970e60d07487
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions