Windows: Bisects getting passing tests, but not able to read chartjson |
|||||||
Issue descriptionExample bisects: https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/586 https://build.chromium.org/p/tryserver.chromium.perf/builders/win_fyi_perf_bisect/builds/975 https://build.chromium.org/p/tryserver.chromium.perf/builders/win_fyi_perf_bisect/builds/976 The test seems to run: https://build.chromium.org/p/tryserver.chromium.perf/builders/win_fyi_perf_bisect/builds/975/steps/Gathering%20reference%20values.Performance%20Test%201%20of%205/logs/Captured%20Output [ OK ] dummy_page.html (5634 ms) (INFO) 2016-11-09 13:15:15,016 desktop_browser_backend._TryCooperativeShutdown:509 Successfully shut down browser cooperatively [ PASSED ] 1 test. But then there is no chartjson to read: https://build.chromium.org/p/tryserver.chromium.perf/builders/win_fyi_perf_bisect/builds/975/steps/Gathering%20reference%20values.Reading%20chartjson%20results/logs/json.output%20%28invalid%29 Ned, could it be a telemetry issue?
,
Nov 9 2016
,
Nov 9 2016
,
Nov 9 2016
Maybe related to Ben & Ethan on this space.
,
Nov 10 2016
,
Nov 10 2016
Issue 663967 has been merged into this issue.
,
Nov 11 2016
This seems due to stuff from the temp directory getting removed from under bisect. This should be fixed now with the use of a named directory.
,
Feb 3 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sullivan@chromium.org
, Nov 9 2016