diff options
| author | Christopher Tate <ctate@google.com> | 2017-03-15 11:07:46 -0700 |
|---|---|---|
| committer | Chris Tate <ctate@android.com> | 2017-03-30 22:07:02 +0000 |
| commit | 69bbcb6a75216858c5cbbb59c41e01ec4bda02ad (patch) | |
| tree | 489bd33d9d785f18e9df107a3c1ca89529ee4b2a /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 877cd5191bbb03de52b151023d82b98fe4ee47f2 (diff) | |
Don't run jobs when connectivity is not validated
Previously, the job scheduler would run jobs with connectivity
constraints as soon as "raw" connectivity was achieved. This could
cause problems, though, because the device might be behind a
captive portal or similar, so apps expecting to contact the internet
would still see connect() failures or other unexpected results.
We now run such jobs only when connectivity has been validated,
so jobs have a stronger expectation that their needed internet
access will be possible.
Bug 28346529
Bug 36137931
Test: manual; use tethered phone hotspot, both with and without SIM,
and verify that the 'validation' trigger is correct.
Change-Id: I79194467610ef9611d38f871d01f92044d0ee9de
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions