| Issue 202924: | desktop_UrlFetch: random loss | |
| Back to list |
Sign in to add a comment
|
See: http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex-binary/builds/1122/steps/VMTest/logs/stdio But specifically, from the status file: ERROR desktopui_UrlFetch.not-live desktopui_UrlFetch.not-live timestamp=1314709743 localtime=Aug 30 06:09:03 Unexpected web site title. Expected: Hello World. Returned: about:blank Perhaps we are starting the HTTP server after we fire off the Chrome request or somesuch.
Aug 30, 2011
Again on x86-generic PFQ http://build.chromium.org/p/chromiumos/builders/x86%20generic%20PFQ/builds/649
Sep 1, 2011
This seems to have done fine all day yesterday. If I didn't know any better I'd suspect a bad chrome build.
Sep 2, 2011
This test has been fine. Closing.
Status:
WontFix
Mar 6, 2013
(No comment was entered for this change.)
Labels:
OS-Chrome
Mar 9, 2013
(No comment was entered for this change.)
Labels:
-Area-Test Cr-Test
|
||||||||||||
| ► Sign in to add a comment | |||||||||||||
This http server is being used in a whole lot of tests, so I'm surprised it'd be failing for this reason only in desktopui_UrlFetch. And in any case, if the http server did not load, the active tab title would not be about:blank -- it would be some error title. cmasone would know more but he's on vacation I see the following in the chrome logs: [3446:3446:64393457:WARNING:gaia_auth_fetcher.cc(424)] ClientLogin failed with BadAuthentication [3446:3446:64393544:WARNING:token_service.cc(257)] Auth token issuing failed for service:chromiumsync [3446:3446:64398342:WARNING:gaia_auth_fetcher.cc(424)] ClientLogin failed with BadAuthentication [3446:3446:64398411:WARNING:token_service.cc(257)] Auth token issuing failed for service:talk [3446:3446:64398615:WARNING:gaia_auth_fetcher.cc(424)] ClientLogin failed with BadAuthentication [3446:3446:64398677:WARNING:token_service.cc(257)] Auth token issuing failed for service:mobilesync At the end of the test, I also see that restarting flimflam did not reset the DNS settings soon enough. 08/30 06:08:58 DEBUG|base_utils:0074| Running 'restart flimflam' 08/30 06:08:58 DEBUG|base_utils:0106| [stdout] flimflam start/running, process 3872 08/30 06:08:58 DEBUG|cros_ui_te:0088| Attempting to resolve www.google.com. to 127.0.0.1 08/30 06:08:58 DEBUG|base_utils:0074| Running 'ping -c 1 -w 1 -q www.google.com.' 08/30 06:08:58 DEBUG|miniFakeDn:0086| Response: www.google.com. -> 127.0.0.1 08/30 06:08:58 DEBUG|cros_ui_te:0091| Resolve attempt for www.google.com. got 127.0.0.1 08/30 06:08:59 DEBUG|cros_ui_te:0088| Attempting to resolve www.google.com. to 127.0.0.1 08/30 06:08:59 DEBUG|base_utils:0074| Running 'ping -c 1 -w 1 -q www.google.com.' 08/30 06:09:01 WARNI|base_utils:0812| run process timeout (2) fired on: ping -c 1 -w 1 -q www.google.com. 08/30 06:09:01 WARNI|cros_ui_te:0082| Command <ping -c 1 -w 1 -q www.google.com.> failed, rc=-15, Command(s) did not complete within 2 seconds * Command: ping -c 1 -w 1 -q www.google.com. Exit status: -15 Duration: 2.00310897827 08/30 06:09:01 DEBUG|cros_ui_te:0091| Resolve attempt for www.google.com. got None 08/30 06:09:01 DEBUG|cros_ui_te:0088| Attempting to resolve www.google.com. to 127.0.0.1 08/30 06:09:01 DEBUG|base_utils:0074| Running 'ping -c 1 -w 1 -q www.google.com.' 08/30 06:09:02 DEBUG|cros_ui_te:0091| Resolve attempt for www.google.com. got 74.125.224.145