Jonathan Loske

We didn't bump it but we had `image: backstopjs/backstopjs` (without a version number) in our `docker-compose.yml`.

I wouldn't know how to run the smoke test in a local installation with a custom `docker-compose.yml`. I tried pointing the script to the correct config file (`node_modules/backstopjs/test/configs/backstop`) but then...

Also of note: We're using a custom `docker-compose.yml` with the following content: ```yml version: "2.1" services: testrunner: image: backstopjs/backstopjs:4.5.0 volumes_from: - container:${HOSTNAME}:rw working_dir: ${WORKSPACE} shm_size: 2048m command: "test --config ./src/test/regression/.generated.backstop.json"...

I had this error happen to me recently locally with an older BackstopJS docker image as well, so it might not be related to the image update. I was able...

I left the project this was happening in last week and don't have access to the code anymore, so I won't be able to test, unfortunately :(

I also wanted to disable logging and used the code @verbruggenalex posted, with one slight variation in my onReady.js, where I used `process.stdout.write` instead of `console.log` (with a `\n` at...

That would be a nice idea! Are you talking about [the files underneath the `chromy` folder](https://github.com/garris/BackstopJS/blob/master/capture/engine_scripts/chromy/)? I could prepare a pull request for this :)

Hm, I just realized that I don't see anything after and including `COMMAND | Executing core for \`report\``. Could we change the output of that to `process.stdout.write`? For my personal...

...upon further investigation, couldn't we just silence `console.log` by changing [the `page.on('console')` listener in `runPuppet.js`](https://github.com/garris/BackstopJS/blob/master/core/util/runPuppet.js#L82)?

Thanks, that helps! I feel like it would be useful to include this in the README somewhere, WDYT? I could volunteer to write a section on it 😊