"start_crash_service" is flaky |
||
Issue description"start_crash_service" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHgsSBUZsYWtlIhNzdGFydF9jcmFzaF9zZXJ2aWNlDA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Mar 21 2016
Not sure what to do with this, let's hope it goes away. |
||
►
Sign in to add a comment |
||
Comment 1 by phoglund@chromium.org
, Mar 18 2016Crash stack: Traceback (most recent call last): File "E:\b\build\scripts\slave\chromium\run_crash_handler.py", line 71, in <module> sys.exit(main()) File "E:\b\build\scripts\slave\chromium\run_crash_handler.py", line 50, in main raise chromium_utils.PathNotFound('Unable to find %s' % exe_path) common.chromium_utils.PathNotFound: Unable to find E:\b\build\slave\win\build\src\out\Release\crash_service.exe step returned non-zero exit code: 1 @@@STEP_EXCEPTION@@@ @@@SET_BUILD_PROPERTY@failure_hash@"f001b7c56292bb28d606f9f3a3516ad27d1ea012"@@@