Fix chromium.perf win builder |
|||||
Issue descriptionLink to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Builder?numbuilds=200 Link to buildbot run: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Builder/builds/54837 It looks like once every 10-20 runs, process_dumps fails with an error message along the lines of: """ Cannot find debugger. step returned non-zero exit code: 88 """ It seems like this should be fixed. maruel@, do you have any idea who the right person to contact about this would be?
,
Feb 13 2017
,
Feb 13 2017
cc'ing Stephen (perf) but I don't think he can quickly figure out either. Searching for "process_dump" on cs.chromium.org leads to the script: https://cs.chromium.org/chromium/build/scripts/slave/process_dumps.py?q=process_dump+package:%5Echromium$&dr The scripts search for a few paths. Probably worth updating these if you installed a new version of the toolchain.
,
Feb 13 2017
I see this is happening only on build40-m1. This sounds familiar. Also changing title of bug.
,
Feb 14 2017
Bah, sorry for the bad bug title. Any idea what the cause might be Peter?
,
Feb 14 2017
Actually it's happening on all the Windows2012R2 based builders. The debuggers installed on them. It's just that process_dumps.py is not finding it.
,
Feb 28 2017
Issue 697209 has been merged into this issue.
,
Mar 1 2017
Looks like https://chromium-review.googlesource.com/c/447776 did the trick. Marking this as fixed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by charliea@chromium.org
, Feb 13 2017