Issue metadata
Sign in to add a comment
|
No new perf results of system_health.memory_desktop on mac |
||||||||||||||||||||||||
Issue descriptionFor example, https://chromeperf.appspot.com/report?sid=923add8f41e8a668b9bf48442c2665279afac6765abb2a28ce342480ccd7ab1d stopped at r558666 on May 15. The bot status (https://ci.chromium.org/buildbot/chromium.perf/Mac%20Pro%2010.11%20Perf/) shows that the bot has been failing at "system_health.memory_desktop Dashboard Upload" step since May 15. Several other mac perf bots (e.g. https://ci.chromium.org/buildbot/chromium.perf/Mac%2010.12%20Perf/) have the same problem.
,
May 18 2018
Sample log: https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FMac_10.12_Perf%2F2068%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_desktop_Dashboard_Upload%2F0%2Fstdout Traceback (most recent call last): File "/b/c/b/Mac_10_12_Perf/src/third_party/catapult/tracing/bin/add_reserved_diagnostics", line 84, in <module> sys.exit(main()) File "/b/c/b/Mac_10_12_Perf/src/third_party/catapult/tracing/bin/add_reserved_diagnostics", line 72, in main dicts, names_to_values) File "/b/c/b/Mac_10_12_Perf/src/third_party/catapult/tracing/tracing/value/diagnostics/add_reserved_diagnostics.py", line 114, in AddReservedDiagnostics dicts_across_repeats = _MergeHistogramSetByPath(hs) File "/b/c/b/Mac_10_12_Perf/src/third_party/catapult/tracing/tracing/value/diagnostics/add_reserved_diagnostics.py", line 80, in _MergeHistogramSetByPath reserved_infos.TEST_PATH.name,)) File "/b/c/b/Mac_10_12_Perf/src/third_party/catapult/tracing/tracing/value/merge_histograms.py", line 33, in MergeHistograms str(result.returncode)) Exception: vinn merge_histograms_cmdline.html returned -12 Sending result 2 of 2 to dashboard. Error uploading histogram data: HTTP Response 400: Bad Request step returned non-zero exit code: 1 Also cc-ing Ethan and Ben, it does look histogram related.
,
May 18 2018
Yeah Emily just reported this, looking at it with Ben. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, May 18 2018