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.

Sign up for GitHub

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

Jump to bottom

Problems running with recent Chromium #30

Open
mitar opened this issue Nov 10, 2020 · 3 comments
Open

Problems running with recent Chromium #30

mitar opened this issue Nov 10, 2020 · 3 comments
Labels
bug

Comments

@mitar
Copy link
Member

mitar commented Nov 10, 2020

It seems recent Chromium (0.75 and up) do not use chromeOptions anymore for custom parameters, but goog:chromeOptions. So passing things with TEST_CHROME_ARGS does not seem to work anymore? BTW, options I am trying to pass are --no-sandbox --disable-dev-shm-usage which seems to be useful in CI context. Not sure if they should not simply be set by default?
@mitar
Copy link
Member Author

mitar commented Nov 10, 2020

It seems we could also pass both?

@mitar
Copy link
Member Author

mitar commented Nov 10, 2020

Maybe we could change code to simply directly set capabilities, instead of using options.toCapabilities()?

@StorytellerCZ
Copy link
Member

Bug confirmed with latest Chromium.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mitar @StorytellerCZ