Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server terminated early with status 0 #5701

Closed
amedvedjev opened this issue Mar 28, 2018 · 6 comments
Closed

Server terminated early with status 0 #5701

amedvedjev opened this issue Mar 28, 2018 · 6 comments

Comments

@amedvedjev
Copy link

Meta -

OS:
Windows 10
Selenium Version:
selenium standalone versions available: 3.11.0 [last]
chromedriver versions available: 2.35, 2.37 [last]
Browser:
Chrome
Browser Version:
Version 65.0.3325.181

Expected Behavior -

[15:57:54][Step 5/6] [chrome #1-16] [15:57:18] I/local - Starting selenium standalone server...
[15:57:54][Step 5/6] [chrome #1-16] [15:57:21] I/local - Selenium standalone server started at http://169.254.182.34:10936/wd/hub

Actual Behavior -

[15:58:01][Step 5/6] [chrome #1-26] [15:57:59] I/local - Starting selenium standalone server...
[15:58:01][Step 5/6] [chrome #1-26] [15:58:01] I/runnerCli - Server terminated early with status 0
[15:58:01][Step 5/6] [15:58:01] E/launcher - Runner process exited unexpectedly with error code: 1

Steps to reproduce -

When i execute jasmine tests in parallel - sometimes is see that server failed to start.

Thanks for any help/workaround. Is any way exists try to restart failed server?

@barancev
Copy link
Member

barancev commented Apr 3, 2018

Please enable debug log in selenium server (-debug option) and attach debug log of a failure.

@amedvedjev
Copy link
Author

@barancev need little help. how i can do this with protractor?

@amedvedjev
Copy link
Author

I got error in manual mode (not sure if the same)

[13:09:08] E/launcher - Error: Error: Server terminated early with status 0
    at earlyTermination.catch.e (C:\Users\alme01\Documents\Sources\xxxxxx\node_modules\selenium-webdriver\remote\index.js:252:52)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

@barancev
Copy link
Member

barancev commented Apr 4, 2018

Can you start selenium server independently of protractor?

@amedvedjev
Copy link
Author

amedvedjev commented Apr 4, 2018

When i start selenium server as hub on some machine issue (and point tests to it) then - issue does not reproduce. Reproducing only when protractor starting selenium server with each test start. Reproducing 1 to 100. But it is annoying to see that one-two tests skipped due to this error.

@barancev
Copy link
Member

barancev commented Apr 4, 2018

I think you have to report this issue to protractor. They can at least add more logging -- what options were used to run selenium server and where to look for detailed selenium server log. We can accept a report if you are able to reproduce the issue with "vanilla" server.

@barancev barancev closed this as completed Apr 4, 2018
@lock lock bot locked and limited conversation to collaborators Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants