New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 620221 link

Starred by 1 user
Status: WontFix
Owner:
jdufault@chromium.org
Closed: Jun 2016
Cc:
█ keta...@chromium.org
steve...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

site_crashcollect: minidump_stackwalk: command not found

Project Member Reported by ihf@chromium.org, Jun 15 2016 
From https://bugs.chromium.org/p/chromium/issues/detail?id=615662#c15

/bin/bash: minidump_stackwalk: command not found, 'Command returned non-zero exit status')
06/14 05:23:53.868 INFO | site_crashcollect:0093| Generating stack trace using devserver for /usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050004.19934.dmp
06/14 05:23:53.869 INFO | site_crashcollect:0106| Failed to generate stack trace on devserver for dump /usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050004.19934.dmp:
DevServerException('Cannot determine build being tested.',)
06/14 05:23:53.869 WARNI| site_crashcollect:0110| Failed to generate stack trace for /usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050004.19934.dmp (see info logs)
06/14 05:23:53.869 INFO | site_crashcollect:0082| Trying to generate stack trace locally for /usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp
06/14 05:23:53.869 INFO | site_crashcollect:0035| symbol_dir: /usr/local/autotest/server/../../../lib/debug
06/14 05:23:53.869 DEBUG|        base_utils:0185| Running 'minidump_stackwalk "/usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp" "/usr/local/autotest/server/../../../lib/debug" > "/usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp.txt"'
06/14 05:23:53.889 INFO | site_crashcollect:0089| Failed to generate stack trace locally for dump /usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp (rc=127):
CmdError('minidump_stackwalk "/usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp" "/usr/local/autotest/server/../../../lib/debug" > "/usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp.txt"', * Command: 
    minidump_stackwalk "/usr/local/autotest/results/hosts/chromeos4-row3-rack
    4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1
    /shill.20160614.050107.20180.dmp"
    "/usr/local/autotest/server/../../../lib/debug" > "/usr/local/autotest/res
    ults/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashi
    nfo.chromeos4-row3-rack4-host1/shill.20160614.050107.20180.dmp.txt"
Exit status: 127
Duration: 0.00266098976135

Comment 1 by jdufault@chromium.org, Jun 15 2016 

Local stack collection is expected to fail when not run by a developer.

But the dev server is also failing to generate a stack trace, which is more concerning:

06/14 05:23:54.735 INFO | site_crashcollect:0106| Failed to generate stack trace on devserver for dump /usr/local/autotest/results/hosts/chromeos4-row3-rack4-host1/4022-provision/20161406045228/crashinfo.chromeos4-row3-rack4-host1/shill.20160614.050004.19915.dmp:
DevServerException('Cannot determine build being tested.',)

Comment 2 by ihf@chromium.org, Jun 15 2016

Cc: steve...@chromium.org
There is a bug on failure to upload symbols. (But mostly Chrome symbols.) Could this be the reason?

Comment 3 by jdufault@chromium.org, Jun 15 2016

Cc: keta...@chromium.org

Comment 4 by jdufault@chromium.org, Jun 15 2016

Status: WontFix (was: Untriaged)
I don't think there are any issues with symbolization itself; rather, the keyval file was not available when symbolization ran. The keyval file contains the build information (JOB_BUILD_KEY) which is used to get the correct set of symbols.

So I think this is a more general infra issue. The keyval file is now available in the test results folder [1].

1: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/64963592-chromeos-test/chromeos2-row10-rack10-host5/
►

Sign in to add a comment