The current instructions on the README to generate the report call for the user to generate the png's using report.R. Unfortunately, the repo's version of this report is out-of-sync with chrome-tracing. And as a result the results.json is incompatible with our own report.R.
The quick-fix solution is to clone chrome tracing and then generate the report (which is much nicer in chrome-tracing) using its report.R and plot.R. You can point it to the results.json file in your repo and it will put a PDF at that location with your aggregate results (the plot.R).
I've created a PR in chrome-tracing to ship those plot.R and report.R with chrome-tracing's distribution, so that we can have EMB use those via an npm script.
The current instructions on the README to generate the report call for the user to generate the png's using
report.R. Unfortunately, the repo's version of this report is out-of-sync with chrome-tracing. And as a result theresults.jsonis incompatible with our ownreport.R.The quick-fix solution is to clone chrome tracing and then generate the report (which is much nicer in chrome-tracing) using its
report.Randplot.R. You can point it to theresults.jsonfile in your repo and it will put a PDF at that location with your aggregate results (theplot.R).I've created a PR in chrome-tracing to ship those
plot.Randreport.Rwith chrome-tracing's distribution, so that we can have EMB use those via an npm script.https://github.com/krisselden/chrome-tracing/pull/8