Fix chrome_public_test_apk on Oreo |
|
Issue descriptionThe majority of tests instrumentation tests in chrome_public_test_apk run fine on Oreo devices. However, a handful fail: org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testNavigationDeletion org.chromium.chrome.browser.explore_sites.ExploreSitesBridgeTest#testGetIcon org.chromium.chrome.browser.widget.PromoDialogTest#testBasic_HeaderBehavior_NoIllustration org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testImportantSitesDialog org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testClearingSiteDataClearsWebapps org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testFrozenNavigationDeletion org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testClearingEverything org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testDialogAboutOtherFormsOfBrowsingHistory org.chromium.webapk.shell_apk.DexLoaderTest#testLoadFromLocalDataDir org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testClearingHistoryClearsWebappScopesAndLaunchTimes org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferencesTest#testImportantSitesDialogNoFiltering These should be fixed so that the experimental flag can be unset for the tests on O. The majority seem to be under preferences.privacy, so assigning to that component.
,
Dec 7
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0183346307f959af42efec29b8ee773c15a8b00c commit 0183346307f959af42efec29b8ee773c15a8b00c Author: bsheedy <bsheedy@chromium.org> Date: Fri Dec 07 01:05:57 2018 Disable standard instrumentation tests on O chrome_public_test_apk and webview_instrumentation_test_apk have always failed on O and end up burning a lot of device time with no one actively monitoring them or trying to fix them. This combined with the few number of devices that have Oreo means that the other tests that run on Oreo that are monitored can end up not running due to capacity issues. So, disable these tests on Oreo until they're either fixed or more capacity is added. Bug: 884413 Change-Id: Ica3a501ed078075dfb462f9cbcd7b3f26cb8dcad Reviewed-on: https://chromium-review.googlesource.com/c/1366255 Reviewed-by: Ben Pastene <bpastene@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#614521} [modify] https://crrev.com/0183346307f959af42efec29b8ee773c15a8b00c/testing/buildbot/chromium.android.json [modify] https://crrev.com/0183346307f959af42efec29b8ee773c15a8b00c/testing/buildbot/test_suite_exceptions.pyl |
|
►
Sign in to add a comment |
|
Comment 1 by bsheedy@chromium.org
, Sep 14