Problem to test Jitsi with Jitsi Toture

I’d try to test my installation with Jitsi torture but the test fail with error:

ChromeDriver was started successfully.

java.util.concurrent.ExecutionException: org.openqa.selenium.WebDriverException: unknown error: cannot find Chrome binary

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’

System info: host: ‘ip-172-31-11-195.eu-south-1.compute.internal’, ip: ‘172.31.11.195’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘4.14.243-185.433.amzn2.x86_64’, java.version: ‘1.8.0_302’

Driver info: driver.version: ChromeDriver

remote stacktrace: #0 0x5587c3a9c8f3

#1 0x5587c3581ba8

#2 0x5587c35a2d96

#3 0x5587c35a09ef

#4 0x5587c35da995

#5 0x5587c35d4d63

#6 0x5587c35ab144

#7 0x5587c35ac135

#8 0x5587c3acbc3e

#9 0x5587c3ae16b7

#10 0x5587c3accb95

#11 0x5587c3ae2b05

#12 0x5587c3ac12ab

#13 0x5587c3afd248

#14 0x5587c3afd3c8

#15 0x5587c3b1833d

#16 0x7f2d619df40b start_thread

at java.util.concurrent.FutureTask.report(FutureTask.java:122)

at java.util.concurrent.FutureTask.get(FutureTask.java:206)

at org.jitsi.meet.test.web.WebParticipantFactory.startWebDriver(WebParticipantFactory.java:337)

at org.jitsi.meet.test.web.WebParticipantFactory.doCreateParticipant(WebParticipantFactory.java:100)

at org.jitsi.meet.test.web.WebParticipantFactory.doCreateParticipant(WebParticipantFactory.java:38)

at org.jitsi.meet.test.base.ParticipantFactory.createParticipant(ParticipantFactory.java:35)

at org.jitsi.meet.test.base.ParticipantHelper.createParticipant(ParticipantHelper.java:162)

at org.jitsi.meet.test.web.WebTestBase.joinParticipant(WebTestBase.java:289)

at org.jitsi.meet.test.web.WebTestBase.joinParticipantAndWait(WebTestBase.java:409)

at org.jitsi.meet.test.web.WebTestBase.ensureOneParticipant(WebTestBase.java:82)

at org.jitsi.meet.test.web.WebTestBase.ensureTwoParticipantsInternal(WebTestBase.java:151)

at org.jitsi.meet.test.web.WebTestBase.ensureThreeParticipants(WebTestBase.java:180)

at org.jitsi.meet.test.web.WebTestBase.ensureThreeParticipants(WebTestBase.java:199)

at org.jitsi.meet.test.ActiveSpeakerTest.setupClass(ActiveSpeakerTest.java:45)

at org.jitsi.meet.test.base.AbstractBaseTest.setupClassPrivate(AbstractBaseTest.java:188)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)

at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:59)

at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:451)

at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:222)

at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:142)

at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:163)

at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)

at org.testng.TestRunner.privateRun(TestRunner.java:648)

at org.testng.TestRunner.run(TestRunner.java:505)

at org.testng.SuiteRunner.runTest(SuiteRunner.java:455)

at org.testng.SuiteRunner.access$000(SuiteRunner.java:40)

at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:489)

at org.testng.internal.thread.ThreadUtil$1.call(ThreadUtil.java:52)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Caused by: org.openqa.selenium.WebDriverException: unknown error: cannot find Chrome binary

We see this from time to time since we updated to latest chrome

This is the first time that I use torture.

Do you have Chrome installed on the machine?
You are running the test locally, you are not using a selenium grid?

No, the installation is on EC2 server.

Torture tests use selenium, which uses a browser headless or not. You either create a selenium grid with nodes that will run the browsers and make the tests connect to your grid or you run it locally to use your local browser.