New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 821317 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Mar 2018
Cc:
█ jialiul@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

browser_tests PolicyTest fails in branded/official windows builds

Project Member Reported by h...@chromium.org, Mar 13 2018 
First failing build on the official waterfal:
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/win%20trunk/builds/80968

See also this public bot:
https://ci.chromium.org/buildbot/chromium.clang/ToTWin/1125

These tests fail:
PolicyTest.PasswordProtectionWarningTrigger
PolicyTest.PasswordProtectionRiskTrigger
PolicyTest.SafeBrowsingWhitelistDomains

Comment 1 by h...@chromium.org, Mar 13 2018

Cc: jialiul@chromium.org
Guessing it's https://chromium-review.googlesource.com/942308

I'll try to confirm locally.

Comment 2 by jialiul@chromium.org, Mar 13 2018 

hmm... Do official bots take input from testing/variations/fieldtrial_testing_config.json?

I cannot think of any other reason that can make my CL pass trybots but not the official build bots....

Comment 3 by jialiul@chromium.org, Mar 13 2018 

Ah, that's the reason... Let me revert my CL and try again.....

Comment 4 by h...@chromium.org, Mar 13 2018

Status: Fixed (was: Available)
The revert landed in https://chromium.googlesource.com/chromium/src/+/c0c17db910641d3708255e55d0446a2f12270f80
Verified locally that this fixes browser_tests.
►

Sign in to add a comment