- Issue created by @alexpott
- First commit to issue fork.
- 🇬🇧United Kingdom catch
Added verbose logging, the logging is more verbose but it's not giving me any more hints about what's going wrong.
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
From the verbose we see:
[0;37m[service:selenium__standalone-chrome-selenium-standalone-chrome-selenium] 2024-07-27T08:33:55.799363620Z 08:33:55.799 DEBUG [DriverService.start] - Starting driver at /usr/bin/chromedriver with [--port=6662, --log-path=/builds/chromedriver.log][0;m [0;37m[service:selenium__standalone-chrome-selenium-standalone-chrome-selenium] 2024-07-27T08:33:55.806694897Z 08:33:55.806 DEBUG [UrlChecker.waitUntilAvailable] - Waiting for [http://localhost:6662/status][0;m [0;37m[service:selenium__standalone-chrome-selenium-standalone-chrome-selenium] 2024-07-27T08:33:55.807341040Z 08:33:55.807 DEBUG [UrlChecker.lambda$waitUntilAvailable$1] - Polling http://localhost:6662/status[0;m [0;37m[service:selenium__standalone-chrome-selenium-standalone-chrome-selenium] 2024-07-27T08:33:55.807568985Z 08:33:55.807 DEBUG [ExternalProcess$Builder.lambda$start$0] - completed to copy the output of process 64[0;m [0;37m[service:selenium__standalone-chrome-selenium-standalone-chrome-selenium] 2024-07-27T08:33:55.810179587Z 08:33:55.809 WARN [DriverServiceSessionFactory.apply] - Error while creating session with the driver service. Stopping driver service: Driver server process died prematurely.[0;mSo the key part seems to be that selenium fails to start up chromedriver - it'd be great to see what is in /builds/chromedriver.log