Meta —
OS: Linux 4.4.0-116-generic x86_64
Selenium Version: 3.11.0
Browser: chrome
Browser Version: 65.0.3325.146 (64-bit)
Expected Behavior —
Element is found
Actual Behavior —
org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status from unknown error: unknown sessionId (Session info: chrome=65.0.3325.146) (Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.4.0-116-generic x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 0 milliseconds Build info: version: ‘3.11.0’, revision: ‘e59cfb3’, time: ‘2018-03-11T20:26:55.152Z’ System info: host: ‘ITM-41’, ip: ‘10.3.199.68’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_121′ Driver info: ru.wb.site.uitest.common.selenium.CustomRemoteWebDriver Capabilities {acceptInsecureCerts: false, acceptSslCerts: false, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.36.540471 (9c759b81a907e7…, userDataDir: /tmp/.org.chromium.Chromium…}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.146, webStorageEnabled: true, webdriver.remote.sessionid: 0b7ec67533c747fd1e0a8e65333…} Session ID: 0b7ec67533c747fd1e0a8e65333dddd9 *** Element info: {Using=xpath, value=//ul[@Class=’user_menu’]/li[@data-jsv]/a}
Steps to reproduce —
- find element by xpath=//h1[text()=’К сожалению, запрошенная вами страница не существует’] | //h1[text()=’404 Not Found’] | //h1[starts-with(text(),’Ошибка сервера’)] | //p[starts-with(normalize-space(text()), ‘В данный момент запрашиваемая вами страница недоступна.’)] — NotFoundException is thrown — it is ok as expected
- find element by xpath=//ul[@Class=’user_menu’]/li[@data-jsv]/a
But I can get the page screenshot and htmlsource
WebDriverException: unknown error: cannot determine loading status from unknown error: unknown sessionId #5609
Comments
jselect commented Mar 14, 2018
OS: Linux 4.4.0-116-generic x86_64
Selenium Version: 3.11.0
Browser: chrome
Browser Version: 65.0.3325.146 (64-bit)
Expected Behavior —
Element is found
Actual Behavior —
org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status from unknown error: unknown sessionId (Session info: chrome=65.0.3325.146) (Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.4.0-116-generic x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 0 milliseconds Build info: version: ‘3.11.0’, revision: ‘e59cfb3’, time: ‘2018-03-11T20:26:55.152Z’ System info: host: ‘ITM-41’, ip: ‘10.3.199.68’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_121’ Driver info: ru.wb.site.uitest.common.selenium.CustomRemoteWebDriver Capabilities , cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.146, webStorageEnabled: true, webdriver.remote.sessionid: 0b7ec67533c747fd1e0a8e65333. > Session ID: 0b7ec67533c747fd1e0a8e65333dddd9 *** Element info:
Steps to reproduce —
- find element by xpath=//h1[text()=’К сожалению, запрошенная вами страница не существует’] | //h1[text()=’404 Not Found’] | //h1[starts-with(text(),’Ошибка сервера’)] | //p[starts-with(normalize-space(text()), ‘В данный момент запрашиваемая вами страница недоступна.’)] — NotFoundException is thrown — it is ok as expected
- find element by xpath=//ul[@Class=’user_menu’]/li[@data-jsv]/a
But I can get the page screenshot and htmlsource
The text was updated successfully, but these errors were encountered:
Источник
Unknown error: session deleted because of page crash #431
Comments
lasotaartur commented Apr 1, 2017
I have error while I’m running many behat scenarios. I’m using selenium/standalone-chrome:3.0.
docker-compose.yml
Error
The text was updated successfully, but these errors were encountered:
tparikka commented Apr 1, 2017
@lasotaartur Not sure if this will help, but try setting shm_size down to 256mb? I hadn’t tried setting it to something as large as 1g, but at 256mb Chrome in my containers has been extremely stable.
lasotaartur commented Apr 1, 2017
I’m using docker in docker with docker-compose. Mayby this is reason. 256mb not help me:/
tparikka commented Apr 1, 2017 •
My one other thought is to try selenium/standalone-chrome:3.2.0 or 3.3.0 and see if using a newer release helps. If it does not, it will help someone who is more technically savvy with the underpinnings of Docker and docker-selenium for you to provide the version of Docker you’re using, for diagnostic purposes.
lasotaartur commented Apr 2, 2017
I checked version 3.2.0 and 3.3.0 but did not work. :/
lasotaartur commented Apr 2, 2017
Is there somewhere logs from chromium to check reason of this situation?
tparikka commented Apr 2, 2017
You can get logs from the container with the command docker logs . I’m out of other ideas — you’ve already mapped /dev/shm:/dev/shm and set shm_size as recommended by all the articles I had read and all of the info I was able to dig up. Maybe others here will know more?
ddavison commented Apr 2, 2017
it’s also possible the app you are automating has some sort of javascript that is killing the page. Also, @lasotaartur next time you open an issue here, please keep the template that you were given when you clicked «New Issue», that’helps with the diagnostics 🙂 thanks!
bvkatwijk commented Apr 3, 2017 •
We are experiencing the same issue using selenium/node-chrome:
org.openqa.selenium.WebDriverException: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed (Session info: chrome=57.0.2987.110) (Driver info: chromedriver=2.28.455506 (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 3.16.0-4-amd64 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 142 milliseconds Build info: version: ‘3.3.0’, revision: ‘b526bd5’, time: ‘2017-03-07 11:21:31 -0800’ System info: host: ‘3a5d88e101a9’, ip: ‘172.17.0.16’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘3.16.0-4-amd64’, java.version: ‘1.8.0_121’ Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities [, takesHeapSnapshot=true, pageLoadStrategy=normal, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=57.0.2987.110, platform=LINUX, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true, unexpectedAlertBehaviour=>] Session ID: 8fb3ca40bb35fb73f6ca45ad2cb7fdfa
A bit further in the logs:
Caused by: org.openqa.selenium.WebDriverException: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed (Session info: chrome=57.0.2987.110) (Driver info: chromedriver=2.28.455506 (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 3.16.0-4-amd64 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 142 milliseconds Build info: version: ‘3.3.0’, revision: ‘b526bd5’, time: ‘2017-03-07 11:21:31 -0800’ System info: host: ‘3a5d88e101a9’, ip: ‘172.17.0.16’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘3.16.0-4-amd64’, java.version: ‘1.8.0_121’ Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities [, takesHeapSnapshot=true, pageLoadStrategy=normal, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=57.0.2987.110, platform=LINUX, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true, unexpectedAlertBehaviour=>] Session ID: 8fb3ca40bb35fb73f6ca45ad2cb7fdfa Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’ System info: host: ‘PC1935’, ip: ‘10.0.110.25’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘1.8.0_91’ Driver info: driver.version: RemoteWebDriver
lasotaartur commented Apr 3, 2017
Now I’m using selenium/standalone-chrome-debug:3.3.0, chrome standalone version with debug and this problem appears less often.
elgalu commented Apr 3, 2017
@lasotaartur you mention you are using docker in docker, did you try to -v /dev/shm:/dev/shm in the parent image? so the shm is shared properly downstream.
lasotaartur commented Apr 3, 2017
What is parent image? You think about container in which is execute docker-compose up ? I tought that I must do this volume mapping on selenium container.
elgalu commented Apr 3, 2017 •
Yes, given you run docker inside docker I think this also need to be done in the container that runs docker-compose up, so you need to do it in both sides else you will just be shared an already small shm
diemol commented Apr 16, 2017
@lasotaartur, perhaps check this issue that resolved what you reported:
elgalu/docker-selenium#20
Try to set in the environment something like —shm-size=1g , as @elgalu says
diemol commented May 4, 2017
@lasotaartur do you have any feedback about our comments and using the additional options?
Perhaps with the recent fixes it is working now for you.
lasotaartur commented May 4, 2017
Now I’m using selenium/standalone-chrome-debug:3.3.0 and it work’s better than selenium/standalone-chrome:3.3.0.
diemol commented May 28, 2017
Sounds good, so you are now sharing the shm memory with the first container you start? (Asking about the docker in docker thing, #431 (comment)).
If things seem to work now, perhaps you could close the issue.
Источник
WebDriverError: unknown error: cannot determine loading status from unknown error: unhandled inspector error: <«code»:-32000,»message»:»Inspected target navigated or closed»>#5347
Comments
allbigbopper commented Nov 4, 2019 •
Hi!
We started experiencing this problem on latest chrome browser versions
- Node Version: 10.13.0
- Protractor Version: 6.0.0
- Angular Version: «
- Browser(s): chrome=78.0.3904.87
- Operating System and Version macOS Mojave 10.14.6
It almost always fails on first page load or login step
The text was updated successfully, but these errors were encountered:
Dan0803 commented Nov 14, 2019
Have you had any update regarding this, as we are experiencing the same problem intermittently, having updated to the latest Chrome Browser version (78.0.3904.97).
jweaver66 commented Nov 14, 2019
I am having the IDENTICAL issue and am unable to resolve.
preethiraoatprospa commented Nov 26, 2019
Was anyone able to resolve the issue, I have been facing it since 4 days
Octopus134 commented Nov 26, 2019 •
I had this issue sometimes 3 weeks ago, but now not any more.
I remember that an Iframe seems to have been the reason, which I had to look in and did not succeed, because it was in a way not there yet, the loading has slowed down.
Because waiting for the iframe to get visible, caused also an error (this or a different; i do not remember) I let my browser sleep for a second, and then wait in a loop for visibility of the iframe and then go on.
kosh01 commented Nov 28, 2019
I am getting this error only when I execute my test cases using Jenkins. One more strange things is, error is not consistent. It fails test cases randomly.
Let me know if you found a solution already.
NikitaV1 commented Dec 2, 2019 •
MummanaSubramanya commented Dec 21, 2019
Facing this same issue on v79. Any update?
junaid18404 commented Mar 9, 2020
I’m also facing same issue. Any help ?
Treborium commented Mar 17, 2020
I’m also facing this issue with v79, however sometimes it works. Not sure what the cause for this is
heathkit commented Apr 6, 2020 •
Having this issue in v80 — it happens about 25% of the time when I navigate to a page that does a redirect. Anyone have a workaround? Catching the error and retrying doesn’t work.
vsravuri commented Apr 6, 2020
This is fixed in v81.
Issue 3252: Getting org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status
Chrome v81 will be stable on April 7th. To overcome this issue, i built a custom chrome driver.
cytora-tarren commented Apr 8, 2020 •
I am still having this issue using chrome version 81.
This is the error i get when running my automated tests:
— Failed: unknown error: cannot determine loading status from target frame detached (Session info: chrome=81.0.4044.92)
However, there have been some occasions where this does not occur and I am able to interact with the iframe (i.e. sendKeys to element) but most of the time it throws the above error. I can’t seem to find anything out there to resolve this issue. HELP NEEDED please! Even if someone could just explain the issue to me from what they know about it. Thanks
vsravuri commented Apr 8, 2020 •
This is how i am able to workaround this issue while switching frame.
this.fn_SwitchToMainFrame = async () => <
let success = false;
let count = 0, max_tries = 40;
while (!success && count++
cytora-tarren commented Apr 9, 2020
When I am on a page I run the below to switch focus to the iframe:
After clicking a button on the first iframe, it opens another iframe attached to the DOM, so now to interact with this new iframe I run:
(note — that the first iframe is still open behind this new iframe)
At this point everything works perfectly fine, so on the second iframe, I log into an account, one successful log in, the iframe is automatically closed and I can see the first iframe again. At this point I run the below code to interact with the first iframe again:
This is when i receive the error message below:
— Failed: unknown error: cannot determine loading status from target frame detached (Session info: chrome=81.0.4044.92)
dextrous2010 commented Apr 27, 2020
Hi all,
I’m expecting the same issue after upgrading the Chrome browser and webdriver to the latest version.
Now a lot of automation tests are failing.
For me, it occurs when I’m working with frames and performing any actions there: trying to fill some textbox or click a button.
Please assist!
yopasa94 commented May 4, 2020
Do we have any update about the issue, I’m getting the same error with the chrome 81.0.4044.122
guicsou-lw commented Aug 17, 2020
any update on this? I am facing the same issue
Bgirish0 commented Sep 3, 2020
n2nco commented Sep 4, 2020
Did that add_argument resolve the issue for you @Bgirish0 ?
Footer
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
#java #selenium #selenium-webdriver #webdriver
#java #selenium #selenium-webdriver #webdriver
Вопрос:
У меня есть сценарий, чтобы щелкнуть гиперссылку и открыть новую вкладку (активное окно переместится на новую вкладку после нажатия гиперссылки)
Когда я пытаюсь перейти с webdriver на новую вкладку с помощью switchTo()
метода, затем WebDriverWait.until
браузер автоматически закрывается с ошибкой
org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status
from no such execution context
(Session info: chrome=73.0.3683.103)
Я использую System.out.println(driver.getWindowHandle())
и вижу, как драйвер переходит на новую вкладку.
Как я могу исправить вышеуказанную ошибку? Я попытался использовать итератор для цикла в WindowHandle
Похоже, не удается использовать WebDriverWait.until(ожидаемые условия) для ожидания новой вкладки. Всегда выдает ошибку cannot determine loading status from no such execution context
Странная вещь, я могу использовать Thread.sleep(1000)
.
Как я могу избежать использования Thread.sleep в этом случае? Поскольку неявное ожидание тоже не может работать
Рабочий код с Thread.sleep()
public class MyCode {
private WebDriver driver;
private WebDriverWait wait;
@Test
public void openPrestaShopFromDemoWebsite() {
System.setProperty("webdriver.chrome.driver", "chromedriver");
ChromeOptions chromeOptions = new ChromeOptions()
.addArguments("--start-maximized", "--incognito");
driver = new ChromeDriver(chromeOptions);
driver.navigate().to("http://demo.prestashop.com");
wait = new WebDriverWait(driver, 10);
wait.until(ExpectedConditions.invisibilityOfElementLocated(By.id("loadingMessage")));
driver.switchTo().frame("framelive");
String parentTab = driver.getWindowHandle();
driver.findElement(By.partialLinkText("Ecommerce software by PrestaShop")).click();
Set<String> windowHandles = driver.getWindowHandles();
Iterator<String> it = windowHandles.iterator();
while (it.hasNext()) {
String newTab = it.next();
if (!parentTab.equals(newTab)) {
driver.switchTo().window(newTab);
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
e.printStackTrace();
}
wait.until(ExpectedConditions.titleIs("Create and develop your business with PrestaShop"));
driver.close();
}
}
driver.switchTo().window(parentTab);
driver.switchTo().frame("framelive");
assertThat(driver.findElement(By.linkText("Personal info")).isDisplayed());
driver.quit();
}
}
Не рабочий код (не удается определить статус загрузки из такого контекста выполнения)
public class MyCode {
private WebDriver driver;
private WebDriverWait wait;
private WebElement element;
@Test
public void openPrestaShopFromDemoWebsite() {
System.setProperty("webdriver.chrome.driver", "chromedriver");
ChromeOptions chromeOptions = new ChromeOptions()
.addArguments("--start-maximized", "--incognito");
driver = new ChromeDriver(chromeOptions);
driver.navigate().to("http://demo.prestashop.com");
wait = new WebDriverWait(driver, 10);
wait.until(ExpectedConditions.invisibilityOfElementLocated(By.id("loadingMessage")));
driver.switchTo().frame("framelive");
String parentTab = driver.getWindowHandle();
driver.findElement(By.partialLinkText("Ecommerce software by PrestaShop")).click();
Set<String> windowHandles = driver.getWindowHandles();
Iterator<String> it = windowHandles.iterator();
while (it.hasNext()) {
String newTab = it.next();
if (!parentTab.equals(newTab)) {
driver.switchTo().window(newTab);
wait.until(ExpectedConditions.titleIs("Create and develop your business with PrestaShop"));
driver.close();
}
}
driver.switchTo().window(parentTab);
driver.switchTo().frame("framelive");
assertThat(driver.findElement(By.linkText("Personal info")).isDisplayed());
driver.quit();
}
}
Комментарии:
1. Обновите вопрос с помощью блока кода для … нажмите гиперссылку … шаг
Ответ №1:
Я сталкивался с этой же проблемой в течение нескольких дней, и кажется, что на самом деле это проблема с chromedriver. Решение, которое сработало для меня, заключалось в добавлении следующего флага / аргумента в параметры вашего chromedriver:
--disable-site-isolation-trials
Вот проблема с chromedriver (и ее решение) Я имею в виду.
Если флаг не работает, вы также можете попробовать обновить chromedriver до версии 75
Комментарии:
1. Спасибо .. это сделано для меня.
2. Да!!! Вот и все!!!
Ответ №2:
Поскольку ссылка открывается на новой вкладке, вам необходимо переключить драйвер на новую вкладку, и для этого вы можете использовать следующий код:
ArrayList<String> tabs = new ArrayList<String> (driver.getWindowHandles());
driver.switchTo().window(tabs.get(1));
И если вы хотите переключиться на исходную вкладку, вам необходимо использовать:
driver.switchTo().window(tabs.get(0));
Комментарии:
1. не работает, после switchTo() и последующего WebDriverWait.until webdriver возвращает
cannot determine loading status from no such execution context
2. @J.Doem Можете ли вы добавить код, который вы использовали после переключения вкладки?
Вопрос:
У меня есть сценарий, который использует селен для тестирования. Теперь даже открываем страницу Google, используя
driver.get(url) # url = Google homepage url
дает мне ниже ошибку
driver.get("https://my.gumtree.com/login")
File "C:Python34libsite-packagesseleniumwebdriverremotewebdriver.py", line 245, in get
self.execute(Command.GET, {'url': url})
File "C:Python34libsite-packagesseleniumwebdriverremotewebdriver.py", line 233, in execute
self.error_handler.check_response(response)
File "C:Python34libsite-packagesseleniumwebdriverremoteerrorhandler.py", line 194, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: cannot determine loading status
from unknown error: missing or invalid 'entry.level'
(Session info: chrome=65.0.3315.3)
(Driver info: chromedriver=2.29.461591 (62ebf098771772160f391d75e589dc567915b233),platform=Windows NT 10.0.16299 x86_64)
У меня есть Google chrome версии 65, Chromedriver 2.35 и селен 2.53.1
Я пробовал разные комбинации версий (упомянутые в таблице ниже) в соответствии с решениями, упомянутыми в других подобных вопросах, но ничего не получилось.
Selenium Chrome Chromedriver
2.53.0 63 2.33
2.53.1 65(latest) 2.34
3.6.0 2.35(latest)
3.7.0
3.8.0
3.8.1(latest)
EDIT 1: версия JDK
java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)
Лучший ответ:
Ошибка говорит все:
selenium.common.exceptions.WebDriverException: Message: unknown error: cannot determine loading status
from unknown error: missing or invalid 'entry.level'
Ваша основная проблема – совместимость версий между используемыми вами двоичными файлами следующим образом:
- Вы используете
chromedriver=2.29.461591
(что соответствует журналам, хотя вы упомянулиChromedriver 2.35
в своем вопросе) - Примечания к
chromedriver=2.29.461591
ясно упоминают следующее:
Supports Chrome v56-58
- Вы используете
chrome=65.0.3315.3
- Примечания к
chromedriver=2.35
ясно упоминают следующее:
Supports Chrome v62-64
- Вы используете
Selenium Version 2.53.1
. -
JDK version
неизвестна нам.
Решение
- Обновление
JDK
до последних уровнейJDK Version 8 Update 151
. - Обновите
ChromeDriver
до уровняChromeDriver v2.35
. - Храните
Chrome
до уровняChrome v64.x
(as per ChromeDriver v2.35 release notes
) - Обновление
Selenium
до текущих уровней.Version 3.8.1
. - Очистите рабочую область проекта от своей среды IDE и перестройте все.
- Запустите средство CCleaner, чтобы стереть все операции с ОС.
- Если ваша базовая версия Chrome слишком старая, удалите Chrome через Revo Uninstaller и установите новую версию Chrome для Chrome.
- Возьмите системную перезагрузку.
- Выполните свой
Test
.
Ответ №1
Перейдите на страницу http://chromedriver.chromium.org/downloads
скопируйте ссылку для загрузки в соответствии с вашей ОС.
wget -N paste_the_link_you_copied
разархивируйте его, используя команду ниже
unzip chromedriver_linux64.zip
Дайте разрешение с помощью команды внизу
chmod +x chromedriver
Затем следуйте приведенным ниже командам, если он говорит, что уже существует (вероятно, старая версия), затем перейдите к этому пути (/usr/local/bin/chromedriver и /usr/bin/chromedriver) и удалите хромированный рекордер и снова запустите команды
sudo mv -f chromedriver /usr/local/share/chromedriver
sudo ln -s /usr/local/share/chromedriver /usr/local/bin/chromedriver
sudo ln -s /usr/local/share/chromedriver /usr/bin/chromedriver
Надеюсь это поможет. Спасибо
Ответ №2
Эта ошибка означает, что ваш браузер Chrome не совместим с веб-драйвером. Если вы используете Linux, просто выполните следующую команду. Обновление sudo apt-get