run-selenium-in-aws-lambda-for-ui-testing" ChromeDriver is assuming that Chrome has crashed #127
Replies: 4 comments 1 reply
-
|
same problem, were you able to succeed? |
Beta Was this translation helpful? Give feedback.
-
|
Nope I gave up.
…On Wed, 28 Sept 2022, 2:59 am jvillaweg, ***@***.***> wrote:
same problem, were you able to succeed?
—
Reply to this email directly, view it on GitHub
<#127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHKCWXDH7HNJC7Q5M4ECMSTWANGY3ANCNFSM56BT6PYA>
.
You are receiving this because you authored the thread.Message ID:
<CloudBytes-Academy/CloudBytes.dev/repo-discussions/127/comments/3746399@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
@jvillaweg @vinitshetty The error is extremely generic and just means chrome hasn't been configured correctly. The exact reason is almost impossible to find out. More often than not it happens due to incorrect permission on the shell script. |
Beta Was this translation helpful? Give feedback.
-
|
For those running into this issue, the latest version of Selenium is not compatible with the default code in the example. Use a version pre 4.0 and you will be good. You can update your requirements.txt to the following: selenium>=3.0,<4.0 |
Beta Was this translation helpful? Give feedback.
-
|
Would you be willing to update the code? |
Beta Was this translation helpful? Give feedback.
-
All steps succeeded but facing below error please help-
https://cloudbytes.dev/snippets/run-selenium-in-aws-lambda-for-ui-testing
so ChromeDriver is assuming that Chrome has crashed
[ERROR] WebDriverException: Message: unknown error: Chrome failed to start: crashed.
(chrome not reachable)
(The process started from chrome location /opt/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Beta Was this translation helpful? Give feedback.
All reactions