Don't assume Chrome needs to be synced just because use flags are set.
Now that we build Chrome with multiple sets of use flags, it's no longer
true that setting the chrome_internal and chrome_pdf use flags will
invalidate the Chrome prebuilts. Remove this check, as it's no longer
needed.
This blocks turning on official Chrome on all builders, as we don't want
Paladin builders to start syncing Chrome (that'd be really slow.)
BUG=chromium:222377
TEST=Unit tests.
Change-Id: Ib05d6bc1792ae64f64e8d2131c2f52a84fdeaf27
Reviewed-on: https://gerrit.chromium.org/gerrit/50923
Tested-by: David James <davidjames@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: David James <davidjames@chromium.org>
diff --git a/scripts/cbuildbot.py b/scripts/cbuildbot.py
index 752eafa..89dce68 100644
--- a/scripts/cbuildbot.py
+++ b/scripts/cbuildbot.py
@@ -667,8 +667,7 @@
if build_config['sync_chrome'] is None:
options.managed_chrome = (chrome_rev != constants.CHROME_REV_LOCAL and
(not build_config['usepkg_build_packages'] or chrome_rev or
- build_config['useflags'] or build_config['profile'] or
- options.rietveld_patches))
+ build_config['profile'] or options.rietveld_patches))
else:
options.managed_chrome = build_config['sync_chrome']