5 Commits

Author	SHA1	Message	Date
Peter Bacon Darwin	6531806996	build(aio): do not ignore `is-on-https` in lighthouse check ... Lighthouse v1.6.5 treats localhost/1.2.7.0.0.1 as secure domains (i.e. as if they where HTTPS), so we need to stop handling the is-on-https audit specially.	2017-05-18 15:48:49 +01:00
Georgios Kalpakas	3a604ba0bf	fix(aio): fix PWA testing on Windows (and reduce flaky-ness) ... Adding a delay after Lighthouse has run and before killing the Chrome process avoids `ECONNREFUSED` errors on Windows and will hopefully prevent such errors occasionally appearing on CI. Based on info in: https://github.com/paulirish/pwmetrics/issues/63#issuecomment-282721068	2017-05-18 15:48:49 +01:00
Georgios Kalpakas	35d1922006	ci(aio): log the full PWA testing results ... This will help diagnose errors or regressions in PWA scores.	2017-05-18 15:48:49 +01:00
Georgios Kalpakas	b40aae54b7	fix(aio): fix PWA testing in cases where `atob`/`btoa` is necessary ... In some cases (unclear when), traceviewer-js, used by Lighthouse under the hood, assumes `atob`/`btoa` are defined in the global scope. This is true for browser environments, but not on node. As a result, some aggregations that required access to model-tracing failed to produce results, dropping the overall PWA score. This affected #16665 (e.g. commit 0de6eec7a).	2017-05-18 15:48:49 +01:00
Georgios Kalpakas	49d97e1216	ci(aio): verify that the Lighthouse PWA score remains above a threshold	2017-04-15 10:23:45 +01:00