[Sync:USS] Add MAYBE prefix to explicit passphrase prefs test
Original CL missed MAYBE prefix and this could lead to test flakiness
on tsan tryjobs.
Bug: 922900
Change-Id: I1faf72c55b7942ad53b4f0e0bd9efdee979f427b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729633
Auto-Submit: Maksim Moskvitin <mmoskvitin@google.com>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683099}
diff --git a/chrome/browser/sync/test/integration/single_client_custom_passphrase_sync_test.cc b/chrome/browser/sync/test/integration/single_client_custom_passphrase_sync_test.cc
index 61b81f9c..2fd3a08 100644
--- a/chrome/browser/sync/test/integration/single_client_custom_passphrase_sync_test.cc
+++ b/chrome/browser/sync/test/integration/single_client_custom_passphrase_sync_test.cc
@@ -412,7 +412,7 @@
#endif
IN_PROC_BROWSER_TEST_F(SingleClientCustomPassphraseSyncTest,
- PRE_ShouldLoadUSSCustomPassphraseInDirectoryMode) {
+ MAYBE_PRE_ShouldLoadUSSCustomPassphraseInDirectoryMode) {
base::test::ScopedFeatureList override_features;
// TODO(crbug.com/922900): Don't disable scrypt derivation and use it as key
// derivation method in ShouldLoadUSSCustomPassphraseInDirectoryMode, once
@@ -439,7 +439,7 @@
#endif
IN_PROC_BROWSER_TEST_F(SingleClientCustomPassphraseSyncTest,
- ShouldLoadUSSCustomPassphraseInDirectoryMode) {
+ MAYBE_ShouldLoadUSSCustomPassphraseInDirectoryMode) {
// We should be able to decrypt bookmarks with passphrase, which was set when
// kSyncUSSNigori was enabled, without providing it again once kSyncUSSNigori
// is disabled.