Skip to content

Chromedriver timeout #669

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

Closed
minkimcello opened this issue Nov 6, 2020 · 3 comments
Closed

Chromedriver timeout #669

minkimcello opened this issue Nov 6, 2020 · 3 comments
Assignees
Labels
@bigtest/webdriver issues related to the `@bigtest/webdriver` package
Milestone

Comments

@minkimcello
Copy link
Contributor

There was an issue with chromedriver not downloading/unzipping properly so our workaround was to include this in our Github Actions workflow:

run: echo "chromedriver_filepath=$CHROMEWEBDRIVER" >> .npmrc

We hoped this would solve our occasional timeout issue but the problem still occurs.

This is the error output:
Screen Shot 2020-11-06 at 1 25 59 PM

When it happens locally I just need to run the command again and it'll start up. And in CI as well, if you re-run the workflow it'll solve itself but I think we should at least have an explanation as to why this is still happening even when we include a local filepath to chromedriver.

@minkimcello minkimcello added this to the 1.0 Beta milestone Nov 6, 2020
@minkimcello minkimcello added the @bigtest/webdriver issues related to the `@bigtest/webdriver` package label Nov 6, 2020
@minkimcello minkimcello modified the milestones: 1.0 Beta, 1.0.0 Nov 6, 2020
@cowboyd
Copy link
Member

cowboyd commented Nov 6, 2020

I think we may just have to bounce the chrome driver process.... maybe say give it 2s to come up, and restart it 5 times or something like that.

@cowboyd
Copy link
Member

cowboyd commented Nov 30, 2020

This looks like a recurring failure in the windows cli tests https://github.com/thefrontside/bigtest/pull/659/checks?check_run_id=1460287789#step:7:197

GitHub
This is a first stab at adding docs via TypeDoc. Unfortunately this uses a frozen in time, outdated fork of TypeDoc, found here TypeStrong/typedoc#1184, because the output generated just isn't ...

@jbolda
Copy link
Contributor

jbolda commented Nov 30, 2020

@cowboyd It might be the same underlying issue, but @minkimcello's case fails due to timeout in webdriver where the test that you linked seems to fail to the timeout set in the bigtest cli test (which is also the same as the default when run in CI) .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@bigtest/webdriver issues related to the `@bigtest/webdriver` package
Projects
None yet
Development

No branches or pull requests

4 participants