logging_UserCrash failed with "Executable name incorrect" |
|||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/stumpy-paladin/builds/28086 logging_UserCrash: FAIL: Executable name incorrect http://cautotest/tko/retrieve_logs.cgi?job=/results/113276994-chromeos-test/ File "/usr/local/autotest/common_lib/test.py", line 609, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 817, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 470, in execute dargs) File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 380, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/logging_UserCrash/logging_UserCrash.py", line 322, in run_once initialize_crash_reporter=True) File "/usr/local/autotest/cros/crash/crash_test.py", line 697, in run_crash_tests getattr(self, '_test_' + test_name)() File "/usr/local/autotest/tests/logging_UserCrash/logging_UserCrash.py", line 196, in _test_core2md_failure _CORE2MD_PATH) File "/usr/local/autotest/tests/logging_UserCrash/logging_UserCrash.py", line 187, in _check_collection_failure _COLLECTION_ERROR_SIGNATURE) File "/usr/local/autotest/cros/crash/user_crash_test.py", line 278, in _check_generated_report_sending raise error.TestFail('Executable name incorrect') TestFail: Executable name incorrect Also happened on https://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex-paladin/builds/27525 https://uberchromegw.corp.google.com/i/chromeos/builders/nyan_kitty-paladin/builds/1388 https://uberchromegw.corp.google.com/i/chromeos/builders/peppy-paladin/builds/14908 https://uberchromegw.corp.google.com/i/chromeos/builders/link-paladin/builds/28081 etc.
,
Apr 19 2017
Looks like cause by one of following CLs https://chromium-review.googlesource.com/c/418344/ https://chromium-review.googlesource.com/c/416358/
,
Apr 21 2017
The common CL in those CQ runs is [1]. The failure doesn't make sense to me though, because that CL only affects ARC and logging_UserCrash passes on my local device. Also, the test fails here [2], but the earlier log output implies that both strings are "crasher_nobreakpad"... [1] https://chromium-review.googlesource.com/#/c/480522/ [2] https://chromium.git.corp.google.com/chromiumos/third_party/autotest/+/master/client/cros/crash/user_crash_test.py#277
,
Sep 18 2017
One-off flake. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nxia@chromium.org
, Apr 19 2017