Skip to content

Find free xvfb display instead of hardcoded 99 using the -a option #778

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

Merged
merged 1 commit into from
Aug 30, 2018
Merged

Find free xvfb display instead of hardcoded 99 using the -a option #778

merged 1 commit into from
Aug 30, 2018

Conversation

anto-ac
Copy link

@anto-ac anto-ac commented Aug 29, 2018

Up until now the xvfb display has been hardcoded to 99 for all nodes.
This sometimes causes errors if the display is not actually free.
xvfb-run has a -a --auto-servernum option, which tries to get a free
server number, starting at 99, or the argument to --server-num.

Fixes #772

@anto-ac anto-ac closed this Aug 29, 2018
@anto-ac anto-ac reopened this Aug 29, 2018
@diemol
Copy link
Member

diemol commented Aug 30, 2018

Thanks @anto-ac! I added some comments to it.

Up until now the xvfb display has been hardcoded to 99 for all nodes.
This sometimes causes errors if the display is not actually free.
xvfb-run has a -a --auto-servernum option, which tries to get a free
server number, starting at 99, or the argument to --server-num.

Fixes #772
@diemol diemol merged commit 96ffe69 into SeleniumHQ:master Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants