All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=650073

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZymAELEhNTdG9wcGFnZUFsZXJ0UGFyZW50ImpDaHJvbWl1bVBlcmYvY2hyb21pdW0tcmVsLXdpbjctZHVhbC90cmFjaW5nLnRyYWNpbmdfd2l0aF9kZWJ1Z19vdmVyaGVhZC9NYXggZXZlbnQgc2l6ZSBpbiBieXRlcyBwZXIgc2Vjb25kDAsSDVN0b3BwYWdlQWxlcnQY0qsZDA,agxzfmNocm9tZXBlcmZylQELEhNTdG9wcGFnZUFsZXJ0UGFyZW50ImdDaHJvbWl1bVBlcmYvY2hyb21pdW0tcmVsLXdpbjctZHVhbC90cmFjaW5nLnRyYWNpbmdfd2l0aF9kZWJ1Z19vdmVyaGVhZC9NYXggbnVtYmVyIG9mIGV2ZW50cyBwZXIgc2Vjb25kDAsSDVN0b3BwYWdlQWxlcnQY0qsZDA,agxzfmNocm9tZXBlcmZyjwELEhNTdG9wcGFnZUFsZXJ0UGFyZW50ImFDaHJvbWl1bVBlcmYvY2hyb21pdW0tcmVsLXdpbjctZHVhbC90cmFjaW5nLnRyYWNpbmdfd2l0aF9kZWJ1Z19vdmVyaGVhZC9Ub3RhbCB0cmFjZSBzaXplIGluIGJ5dGVzDAsSDVN0b3BwYWdlQWxlcnQY0qsZDA


Bot(s) for this bug's original alert(s):

chromium-rel-win7-dual

+zhenw: any idea why tracing.tracing_with_debug_overhead stopped producing data on August 30?

crrev.com/415186 looks irrelevant, but idk.

Issue 650068 has been merged into this issue.

Hmm, I have no idea. The test is not disabled. And there seems to be no failure. Ned, do you have any clue?

Hmhh, this seems like a bug with uploading the chartjson to the dashboard? I see the chart json with values populated from latest run (build 10788) here:

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Perf%20%283%29/builds/10788/steps/tracing.tracing_with_debug_overhead/logs/json.output


Assign to Annie for triaging.

Looks like a renaming issue: The current chartjson gives names like "Max event size in bytes per second_avg" an the charts in comment 1 have names without "_avg", "_count", etc.