| Index: chrome/browser/chromeos/policy/blocking_login_browsertest.cc
|
| diff --git a/chrome/browser/chromeos/policy/blocking_login_browsertest.cc b/chrome/browser/chromeos/policy/blocking_login_browsertest.cc
|
| index 651a9264acc7c0cea5feaf70f30fc7d67a20f02f..a57f3ac2312e522368628165ad5fef6d5a46fd26 100644
|
| --- a/chrome/browser/chromeos/policy/blocking_login_browsertest.cc
|
| +++ b/chrome/browser/chromeos/policy/blocking_login_browsertest.cc
|
| @@ -81,11 +81,6 @@
|
| const bool enroll_device;
|
| };
|
|
|
| -// TODO(atwilson): This test is completely broken - it originally was built
|
| -// when we made an entirely different set of network calls on startup. As a
|
| -// result it generates random failures in startup network requests, then waits
|
| -// to see if the profile finishes loading which is not at all what it is
|
| -// intended to test. We need to fix this test or remove it (crbug.com/580537).
|
| class BlockingLoginTest
|
| : public OobeBaseTest,
|
| public content::NotificationObserver,
|
| @@ -100,9 +95,6 @@
|
| command_line->AppendSwitchASCII(
|
| policy::switches::kDeviceManagementUrl,
|
| embedded_test_server()->GetURL("/device_management").spec());
|
| -
|
| - command_line->AppendSwitch(
|
| - chromeos::switches::kAllowFailedPolicyFetchForTest);
|
| }
|
|
|
| void SetUpOnMainThread() override {
|
|
|