x86-alex-tot-chrome-pfq-informational failing in login_LogoutProcessCleanup |
||
Issue descriptionThis change broke x86-alex-tot-chrome-pfq-informational: https://chromium-review.googlesource.com/c/527478/ Here is the breaking builder: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/x86-alex-tot-chrome-pfq-informational/builds/24274 Bisect results are builds #43-#52 here: https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/chrome_pfq_informational The failure message is: BrowserConnectionGoneException: Timed out while waiting 240s for HasBrowserFinishedLaunching. It appears that Chrome hung or crashed, but there is no minidump. The chrome logs are here: https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/x86-alex-tot-chrome-pfq-informational/R61-9634.0.0-b24274/vm_test_results_1/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-01-login_LogoutProcessCleanup/login_LogoutProcessCleanup/sysinfo/var/log_diff/chrome/ I do not however see any obvious error messages. We no longer officially support x86 boards for Chrome OS and are in the process of deprecating the builder, however I thought we should at least file a bug for this.
,
Jun 13 2017
It looks like removing the builder from the waterfall removed those links :( The google storage link appears to work at least. With no way to test this further there doesn't seem to be much point in reverting. If you can think of any reason why that CL might have an issue on 32 bit boards it might be worth trying to test that and fix it? Mostly I wanted to file this so that we have a record of the failure and as a heads up to potential issues elsewhere. Feel free to resolve this WontFix.
,
Jun 13 2017
Actually, that waterfall is down completely: issue 732859 , so those links may work once that is fixed.
,
Jun 13 2017
OK. I'll take another look when that's resolved. I'll probably mark this issue as WontFix since I can't think of anything in my CL that causes 32-bit specific bugs.
,
Jun 13 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by staraz@chromium.org
, Jun 13 2017