Not really reliable results using engine Chromy

I have searched the issues and found many problems regarding zombie processes. Even if I stop all zombies, I have a failure rate between 10-30%, having 35 scenarios with three viewports each. I digged into the code and logged out the errors saying

Error: Invalid target undefined in chrome-remote-interface/lib/chrome.js which seems to be related to ports already in use by another instance.

If I change the port assigning code so that the port is chosen short before Chromy is initialized like

 const portfinder = require('portfinder');
  
  let port = await portfinder.getPortPromise();
  let defaultOptions = {
    chromeFlags: undefined,
    port: port,
    waitTimeout: TEST_TIMEOUT,
    visible: config.debugWindow || false
  };

I actually get no port errors or any other errors, but I still only got 97 of 105 screenshots. I also tried decreasing the concurrent processes to 5 or less, but I never got all screenshots.

Is anybody running a similar scenario with more success? I am using the newest version of everything.

[garris]

Just bumped to 3.2.0 and pushed to NPM!

You can…

npm install backstopjs@beta

[krisdigital]

@garris All right, I will try to get the selector screenshots running and to make Puppeteer and Chromy coexist to get it to a ‘near release’ status! Thank’s for the coordination and if you need a AU Plugin let me know 😜