Not sure if we use a real NCN or not in browser_tests, normally.  We are using a real one in NetworkService unittests, now, though.

[+pauljensen]:  Don't suppose you know?  I don't see a MockNCN being created in the browsertest fixture, but I could be missing something.

Sorry, that should be "we are using one in browsertests with the network service enabled."

The only difference between these flaky tests and the other tests is that they are creating a ranged request (ResumeRestoredDownload_xxxx), rather than starting from offset 0.

if a test starts from 0, it seems fine

@qinmin: I'm surprised you're seeing ERR_NETWORK_CHANGED.  Was your network changing?  e.g. were you plugging/unplugging Ethernet or leaving/joining WiFi networks?  Can you run "ip monitor" from the command line to see what changes appear.  If you're using a linux desktop there should be almost no network changes on a regular basis.

@mmenke: There are a few ways to disable the real NCN:
  net::test::ScopedMockNetworkChangeNotifier
  net::test::MockNetworkChangeNotifier
  net::NetworkChangeNotifier::DisableForTest
  net::NetworkChangeNotifier::CreateMock
Various individual tests use one of these to disable the NCN.  I think only net_unittests disables the real NCN for the whole test suite.

Generally our bots shouldn't encounter network changes (the Android bots don't have any active network AFAIK).  I'd like to figure out why qinmin@ experienced a network change before working on disabling the NCN for his tests.

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.