Issue metadata
Sign in to add a comment
|
cheets_StartAndroid.stress - DevToolsClientConnectionError
Reported by
jrbarnette@chromium.org,
Jan 8 2018
|
||||||||||||||||||||||
Issue description
This CQ run failed:
https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17432
The run failed because of caroline-paladin:
https://luci-milo.appspot.com/buildbot/chromeos/caroline-paladin/2342
This is the test failure message:
cheets_StartAndroid.stress: FAIL: Unhandled DevToolsClientConnectionError: ''
The test logs are here:
http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/168509746-chromeos-test/
The blamelist for the failed caroline-paladin run contains only two CLs;
one couldn't have caused the failure, and the other looks unlikely. So,
this is a bug in the test, or in ToT. Passing to the ARC++ constable
for triage.
,
Jan 9 2018
I don't know the general policy, but in general I think we actually care about investigating flake bugs. We have so many builders that if we let flake bugs go unfixed then the build is always failing for one flake or another...
,
Jan 9 2018
Basically, dianders@ is right. I don't want to be absolutist - there is a level of flake that may be cheaper to tolerate than to fix. However, absent a clearer explanation of the root cause, a day or two of no failures isn't good enough.
,
Jan 13 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/9a225c02d1f78511f44bc9abdeea07fb9bfe011b commit 9a225c02d1f78511f44bc9abdeea07fb9bfe011b Author: Ben Lin <linben@google.com> Date: Sat Jan 13 06:37:50 2018 Add check for Chrome PID if exception occurs for startAndroid.stress. startAndroid.stress test has been hitting exceptions regarding timeout when trying to enable play store. We don't know whether Chrome is still alive or not at this point, so logging this. BUG= chromium:783832 BUG= chromium:799958 TEST=ran cheets_StartAndroid test locally. Change-Id: Ifbe1bc73fa75a29df01410a9ef4cd77d5b4c7f80 Reviewed-on: https://chromium-review.googlesource.com/865100 Commit-Ready: Ben Lin <linben@chromium.org> Tested-by: Ben Lin <linben@chromium.org> Reviewed-by: Yusuke Sato <yusukes@chromium.org> [modify] https://crrev.com/9a225c02d1f78511f44bc9abdeea07fb9bfe011b/client/common_lib/cros/chrome.py [modify] https://crrev.com/9a225c02d1f78511f44bc9abdeea07fb9bfe011b/client/site_tests/cheets_StartAndroid/cheets_StartAndroid.py
,
Jan 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/fed7f8aba8cfcc2b75b1ab86cad46b5476bb551d commit fed7f8aba8cfcc2b75b1ab86cad46b5476bb551d Author: Ben Lin <linben@chromium.org> Date: Tue Jan 23 09:48:47 2018 Revert "Add check for Chrome PID if exception occurs for startAndroid.stress." This reverts commit 9a225c02d1f78511f44bc9abdeea07fb9bfe011b. Reason for revert: See original CL's comments - test is no longer failing properly. Original change's description: > Add check for Chrome PID if exception occurs for startAndroid.stress. > > startAndroid.stress test has been hitting exceptions regarding timeout > when trying to enable play store. We don't know whether Chrome is still > alive or not at this point, so logging this. > > BUG= chromium:783832 > BUG= chromium:799958 > TEST=ran cheets_StartAndroid test locally. > > Change-Id: Ifbe1bc73fa75a29df01410a9ef4cd77d5b4c7f80 > Reviewed-on: https://chromium-review.googlesource.com/865100 > Commit-Ready: Ben Lin <linben@chromium.org> > Tested-by: Ben Lin <linben@chromium.org> > Reviewed-by: Yusuke Sato <yusukes@chromium.org> Bug: chromium:783832 , chromium:799958 Change-Id: I788e204682bb62093ad7284e78817c60f3ddb39f Reviewed-on: https://chromium-review.googlesource.com/879241 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Ben Lin <linben@chromium.org> Reviewed-by: Yusuke Sato <yusukes@chromium.org> Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org> [modify] https://crrev.com/fed7f8aba8cfcc2b75b1ab86cad46b5476bb551d/client/common_lib/cros/chrome.py [modify] https://crrev.com/fed7f8aba8cfcc2b75b1ab86cad46b5476bb551d/client/site_tests/cheets_StartAndroid/cheets_StartAndroid.py
,
Jan 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/ef56d33d40afb1da263697944305a1288122c8cd commit ef56d33d40afb1da263697944305a1288122c8cd Author: Ben Lin <linben@chromium.org> Date: Fri Jan 26 04:18:51 2018 Revert "Add check for Chrome PID if exception occurs for startAndroid.stress." This reverts commit 9a225c02d1f78511f44bc9abdeea07fb9bfe011b. Reason for revert: See original CL's comments - test is no longer failing properly. Original change's description: > Add check for Chrome PID if exception occurs for startAndroid.stress. > > startAndroid.stress test has been hitting exceptions regarding timeout > when trying to enable play store. We don't know whether Chrome is still > alive or not at this point, so logging this. > > BUG= chromium:783832 > BUG= chromium:799958 > TEST=ran cheets_StartAndroid test locally. > > Change-Id: Ifbe1bc73fa75a29df01410a9ef4cd77d5b4c7f80 > Reviewed-on: https://chromium-review.googlesource.com/865100 > Commit-Ready: Ben Lin <linben@chromium.org> > Tested-by: Ben Lin <linben@chromium.org> > Reviewed-by: Yusuke Sato <yusukes@chromium.org> Bug: chromium:783832 , chromium:799958 Change-Id: I788e204682bb62093ad7284e78817c60f3ddb39f Reviewed-on: https://chromium-review.googlesource.com/879241 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Ben Lin <linben@chromium.org> Reviewed-by: Yusuke Sato <yusukes@chromium.org> Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org> (cherry picked from commit fed7f8aba8cfcc2b75b1ab86cad46b5476bb551d) Reviewed-on: https://chromium-review.googlesource.com/888298 Tested-by: Kazuhiro Inaba <kinaba@chromium.org> [modify] https://crrev.com/ef56d33d40afb1da263697944305a1288122c8cd/client/common_lib/cros/chrome.py [modify] https://crrev.com/ef56d33d40afb1da263697944305a1288122c8cd/client/site_tests/cheets_StartAndroid/cheets_StartAndroid.py
,
Jan 26 2018
/var/log/ui/ui.20180108-045901 of the Caroline log shows that this is due to a Chrome crash in the login screen: Inconsistency detected by ld.so: dl-tls.c: 493: _dl_allocate_tls_init: Assertion `listp->slotinfo[cnt].gen <= GL(dl_tls_generation)' failed! which is exactly worked on right now in crbug.com/783832 . I found 3 other instances of the same error message "Unhandled DevToolsClientConnectionError: ''" in these 2 months, and all of them shared the same cause. https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/169435885-chromeos-test https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/169430919-chromeos-test https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/164356900-chromeos-test Merging to crbug.com/783832
,
Jan 26 2018
Some more note: a similar error message Unhandled DevToolsClientConnectionError: [Errno 104] Connection reset by peer were occasionally seen as well. https://stainless.corp.google.com/search?view=list&first_date=2017-12-01&last_date=2018-01-31&test=cheets_StartAndroid&status=FAIL&status=ERROR&reason=DevToolsClientConnectionError&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true Looking at the instances of that failure, the causes are cryptohome/chrome crashes of crbug.com/794403, which should already be fixed in M65/M66/ToT. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by linben@chromium.org
, Jan 9 2018