Tests timing out

[jywarren]

Seeing this come up a lot; and @sashadev-sky tried working on it in #609 (comment)

I attempted a fix in #675

https://docs.travis-ci.com/user/gui-and-headless-browsers/#karma-and-firefox-inactivity-timeouts

    browserNoActivityTimeout: 40000,

But we're still seeing it in #680 (you can try it out in fact in GitPod there!)

The error is typically:

30 06 2020 19:24:15.577:WARN [PhantomJS 2.1.1 (Linux x86_64)]: Disconnected (1 times), because no message in 30000 ms.
PhantomJS 2.1.1 (Linux x86_64) ERROR
  Disconnected, because no message in 30000 ms.

And after #675 it is now:

  Disconnected, because no message in 40000 ms.

Any help appreciated!

[MLefebvreICO]

Hi there,

Just found your issue while searching for why our tests suite on our end was not working anymore.

First of all, let me suggest you use Chrome headless instead of PhantomJS which was abandonned years ago.

But for now even Chrome headless is broken, because of their latest stable release ..

You can follow on this here : https://bugs.chromium.org/p/chromium/issues/detail?id=1090988

[jywarren]

Ah, thank you for the tip! Looking in our test setup, i'm thinking we could make the switch here perhaps:

Leaflet.DistortableImage/test/karma.conf.js

Lines 98 to 111 in 33f0bf5

	// start these browsers
	// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
	browsers: ['PhantomJS'],
	// If browser does not capture in given timeout [ms], kill it
	captureTimeout: 5000,
	// to address Travis build errors; https://github.com/publiclab/Leaflet.DistortableImage/pull/675
	// https://docs.travis-ci.com/user/gui-and-headless-browsers/#karma-and-firefox-inactivity-timeouts
	browserNoActivityTimeout: 40000,
	// Workaround for PhantomJS random DISCONNECTED error
	browserDisconnectTimeout: 10000, // default 2000
	browserDisconnectTolerance: 1, // default 0

[jywarren]

Looks like there are karma-chrome-launcher and karma-firefox-launcher among others!

[jywarren]

So i would guess the steps might be:

1. include karma-chrome-launcher in package.json
2. add "Chrome" to browsers: array
3. change this include:

Leaflet.DistortableImage/test/karma.conf.js

Line 15 in 33f0bf5

require('karma-phantomjs-launcher'),

[jywarren]

Let's see how this does, and if Chrome bug resolves we can update it: #685

[sashadev-sky]

closed via #716