8000
Jan 20, 2022
·
2 comments
Comment options
You must be logged in to vote
Comment options
You must be logged in to vote
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji
reacted with thumbs down emoji
reacted with laugh emoji
reacted with hooray emoji
reacted with confused emoji
reacted with heart emoji
reacted with rocket emoji
reacted with eyes emoji
Error Message: Runner is not Alive #2188
logyourtesting
started this conversation in
General
Replies: 2 comments
-
|
looks like the runner crashed unexpectedly, is there any information in the logs? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
In my case the problem with this error was the bad import for step that AI gave me. After switching it as in the original documentation it worked: You can find solid info in the logs. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
when running scenario from visual studio code getting this error :
Logs
Error Message: error reading from server: read tcp 444.0.0.1:49719->127.0.0.1:444718: wsarecv: An existing connection was forcibly closed by the remote host.
Stacktrace:
Error Message: Runner is not Alive
Stacktrace:
plugins and gauge versions
Gauge version: 1.4.2
Commit Hash: f080fbc
Plugins
html-report (4.1.4)
js (2.4.0)
screenshot (0.1.0)
Beta Was this translation helpful? Give feedback.
All reactions