Co-authored-by: Zev Eisenberg <zev@zeveisenberg.com>

This partially fixes #399 by not display non-finite scores which are caused by 0-measured suite results.

- For non-positive or non-finite scores, the following summary page is displayed. Note that the detailed page is still accessible since you might find some useful information there.
- Additionally, a console.error is generated for each zero-sum suite
- Merge of original PR  #406

The metric's "geomean" aggregate value can be easily confused with the top-level Geomean metric (issue #407).

- Don't serialize "geomean" in the JSON data
- Add descriptions to Score, Geomean, and Iteration metrics that are serialized in the JSON data
- Make the detail view titles more descriptive
- Merge of original PR #408

…nto) (#494)

…OM (#488) (#496)

modifications happen asynchronously in the onhashchange() callback.

This results in nothing interesting being measured during the sync phase, and
the resulting rendering update (during the async phase) not including the
change.

Change the test to manually and synchronously trigger the onhashchange()
callback, and change the page content to detect and omit duplicate events.

Co-authored-by: Matt Woodrow <m_woodrow@apple.com>

* Add WakeLock wrapper class around the web-api to keep the screen unlocked during benchmark runs
* Use WakeLock.aquire() and WakeLock.release() in the benchmark runner

* Use 8080 as default address for local test server

* fix space