Any verbose/debug options?

[avishnyakov]

Hi team,

I might be overlooking but can't find debug/verbose options or execution logs. Having silent failures under various docker container based runs as following.

Best bet so far - corporate proxy or ssl cert validation failure. Would be nice to confirm this with actual logs.

If you could point to the right troubleshooting direction, that would be wonderful.

Launching Chrome
  ✘ Error: Unable to complete run 1 of 3 due to No metrics data.
Launching Chrome
  ✘ Error: Unable to complete run 2 of 3 due to No metrics data.
Launching Chrome
  ✘ Error: Unable to complete run 3 of 3 due to No metrics data.

Config / CLI options

module.exports = {
    flags: {
        runs: '3',
        expectations: false,
        chromeFlags: '--headless',
        json: true
    },
    expectations: {
        ttfcp: {
            warn: '>=10000',
            error: '>=15000'
        },
        ttfmp: {
            warn: '>=16000',
            error: '>=20000'
        },
        psi: {
            warn: '>=16500',
            error: '>=20000'
        },
        ttfi: {
            warn: '>=20000',
            error: '>=25000'
        },
        ttci: {
            warn: '>=25000',
            error: '>=30000'
        }
    }
}

Steps to reproduce.

Execute pwmertics under Docker container.

# https://github.com/ImmoweltGroup/docker-pwmetrics/blob/master/Dockerfile

FROM markadams/chromium-xvfb-js:8

ARG NODE_ENV=production
ARG BABEL_ENV=production

ARG PWMETRICS_VERSION="4.2.1"

RUN npm config set registry http://registry.npmjs.org/
RUN npm i -g pwmetrics@"$PWMETRICS_VERSION"

ENTRYPOINT [ "pwmetrics" ]

Stack trace

Launching Chrome
  ✘ Error: Unable to complete run 1 of 3 due to No metrics data.
Launching Chrome
  ✘ Error: Unable to complete run 2 of 3 due to No metrics data.
Launching Chrome
  ✘ Error: Unable to complete run 3 of 3 due to No metrics data.
        ☆  Median run  ☆
{
  "runs": []
}

Screenshot

N/A

Environment

1. pwmetrics version: 4.2.1
2. Chrome version: Chromium 64.0.3282.119 built on Debian 9.3, running on Debian 9.4
3. OS version: Linux 593a0e94ac2d 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux

[avishnyakov]

All good, internal proxies / settings. Closing this.

Generally, chromeFlags helps a bit but it might be still a good idea to craft a page on troubleshooting experience.

chromeFlags: '', // custom flags to pass to Chrome. For a full list of flags, see http://peter.sh/experiments/chromium-command-line-switches/.