Issue metadata
Sign in to add a comment
|
"InMemoryApp/NetworkContextConfigurationHttpsStrippingPacBrowserTest.PacHttpsUrlStripping/0" is flaky |
||||||||||||||||||||||||
Issue description"InMemoryApp/NetworkContextConfigurationHttpsStrippingPacBrowserTest.PacHttpsUrlStripping/0" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZQsSBUZsYWtlIlpJbk1lbW9yeUFwcC9OZXR3b3JrQ29udGV4dENvbmZpZ3VyYXRpb25IdHRwc1N0cmlwcGluZ1BhY0Jyb3dzZXJUZXN0LlBhY0h0dHBzVXJsU3RyaXBwaW5nLzAM. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Aug 21
mmenke@, could you take look? Since you introduce this test. Thanks!
,
Aug 21
[+hjd, +primiano]: Any ideas what could cause this to happen? Looks like you're the owners of the DCHECK in question. The failure doesn't look like it has much to do with the test itself, but rather with services/resource_coordinator/memory_instrumentation not being set up in the network process (No idea why this would happen, or why it would only happen in one set of tests).
,
Aug 21
Note that this test actually looks to be failing with the network process disabled...so the network code is just running in a generic browser process, and this has nothing to do with the network service, like I first assumed. The DCHECK actually looks to be happening on the browser process's IO thread.
,
Aug 22
+ssid / erikchen. Does any of you know what could be going on here?
,
Aug 22
Actually I think this might be a dupe of Issue 840127 (see Comment 7)
,
Aug 22
I don't see why we would be restarting a service in InMemoryApp/NetworkContextConfigurationHttpsStrippingPacBrowserTest.PacHttpsUrlStripping/0 (We would in the /2 one, though), so it may not quite be the same issue. I'll leave this open, but won't dig into it until the other one is resolved.
,
Aug 23
Looks like it may be a while before the other issue is resolver, so just going to merge this after all. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by yosin@chromium.org
, Aug 21