Switch back from Chromium to PhantomJS?

We switched from PhantomJS to Chromium in #6377 by @PierreBesson

This is of course the future, but at the moment I have at least 2 feedbacks from clients where it doesn’t work:

• At one client, using Windows 7, yarn test did not run at all with Chromium
• At another client, using either Red Hat or Ubuntu, we have missing libraries that make Chromium fail

As we had none of those issues with PhantomJS (it works for both clients), I think it’s too early to have Chromium, and we should switch back to PhantomJS.

Thoughts, ideas, comments?

[pascalgrimaud]

I spent a couple of hours tonight on this. In fact, we currently have the same issue in our jhipster/jhipster image.

To resolve, I needed to follow these instructions: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-puppeteer-in-docker

Then, here my karma.conf.js configuration:

    browsers: ['ChromiumHeadless'],
        customLaunchers: {
            'ChromiumHeadless': {
                base: 'Chrome',
                flags: [
                    '--no-sandbox',
                    '--headless',
                    '--disable-gpu',
                    // Without a remote debugging port, Google Chrome exits immediately.
                    '--remote-debugging-port=9222'
                ],
                debug: true
            }
        },

[thomastardy]

Just for information if anybody tries to run the current version with ChromiumHeadless on CentOS 7, you have to install the packages chromium-libs and gtk3. This solved the problem for us.