Trying to get Jitsi-torture to work

I’m trying to get this working:

When I ran the docker-compose up in the jitsi-torture-selenium-grid-platform/hub folder, it created the following containers for me:

990d78312a5c        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5000->5555/tcp    node_chrome_1
e512e28038bb        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_9
c9ae80088a08        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_2
1bca64a30bba        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_6
8fda44d812b6        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_10
29ca700630bb        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_4
720b1c3e44e4        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_3
22f8fd799a46        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_8
b9836a70a430        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_1
5be24e9e198f        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_7
b526a1e8bf09        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours                                    hub_chrome_5
fbf4a18922b9        selenium/hub:3.141.59-xenon           "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:4444->4444/tcp    selenium-hub
c2bdc1835ffb        google/cadvisor:latest                "/usr/bin/cadvisor -…"   7 hours ago         Up 7 hours          0.0.0.0:28080->8080/tcp   cadvisor
jitsi-torture-selenium-grid-platform

And then … I went into the jitsi-torture-selenium-grid-platform/node folder, and ran the docker-compose there and it created the following containers for me:

myserver:/var/git/jitsi-meet-torture# docker ps
    CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS              PORTS                     NAMES
    413b51c60416        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5009->5555/tcp    kind_matsumoto
    cc5ca21cad7d        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5008->5555/tcp    elastic_turing
    ae0e33690d62        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5007->5555/tcp    charming_morse
    22b3d47e5fd2        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5006->5555/tcp    angry_mclean
    9a22fc303a8c        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5005->5555/tcp    suspicious_einstein
    afa77419023e        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5004->5555/tcp    frosty_hugle
    98fe8432015d        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5002->5555/tcp    romantic_napier
    3dea4fab48b9        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5001->5555/tcp    thirsty_engelbart
    edd3c691618d        selenium/node-chrome:3.141.59-xenon   "/opt/bin/entry_poin…"   7 hours ago         Up 7 hours          0.0.0.0:5003->5555/tcp    zealous_hofstadter

The video file and the sound file is present on the node containers.

This is the command I’m using to try to trigger the test:

myserver:/var/git/jitsi-meet-torture# mvn
-Dthreadcount=1
-Dorg.jitsi.malleus.conferences=3
-Dorg.jitsi.malleus.participants=5
-Dorg.jitsi.malleus.senders=5
-Dorg.jitsi.malleus.duration=600
-Dorg.jitsi.malleus.room_name_prefix=openpaastest
-Dremote.address=“http://172.18.0.3:4444/wd/hub
-Djitsi-meet.tests.toRun=MalleusJitsificus
-Dwdm.gitHubTokenName=jitsi-jenkins
-Dremote.resource.path=/usr/share/jitsi/resources
-Djitsi-meet.instance.url=“https://myjitsimeetserver
-Djitsi-meet.isRemote=true
test

when I try to run tests, I keep getting the following error:

Exception in thread “Thread-14” org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.

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

System info: host: ‘myserver’, ip: ‘127.0.0.1’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘5.4.72-0-lts’, java.version: ‘1.8.0_252’

Driver info: driver.version: RemoteWebDriver

I’ve made sure the server works when you hit it manually. no authentication is on in prosody.
any tips would be appreciated.