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

I cannot get headless tests to run in Travis CI #42

Open
andrewdavidmackenzie opened this issue Jun 16, 2019 · 3 comments
Open

I cannot get headless tests to run in Travis CI #42

andrewdavidmackenzie opened this issue Jun 16, 2019 · 3 comments
Labels
question Further information is requested

Comments

@andrewdavidmackenzie
Copy link

Summary

When I run a similar project in Travis CI I get this error:

Running headless tests in Chrome with `/Users/travis/Library/Caches/.wasm-pack/chromedriver-b5d7e439698af816/chromedriver`
driver status: signal: 9
driver stdout:
    Starting ChromeDriver 2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e) on port 59072
    Only local connections are allowed.
    Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.

So I am not sure how you are able to get travis to run --chrome --headless

Any ideas?

BTW: In "-script" I see "cd testing" but there is no such folder. I don't see it created during setup, but maybe wrong.

@andrewdavidmackenzie andrewdavidmackenzie added the question Further information is requested label Jun 16, 2019
@xv-matt-u
Copy link

xv-matt-u commented Jul 31, 2019

@andrewdavidmackenzie Did you by any chance find a solution? I'm having the same issue on CircleCI.

Running the same command in the same Docker container works fine on my machine, so I'm guessing it's a CI quirk.

@spike1292
Copy link

Issue is also found here: rustwasm/wasm-pack#611
Hopefully fix by rustwasm/wasm-pack#706

Current workaround: rustwasm/wasm-pack#611 (comment)

I used the following command npm installl -g [email protected] to fix the issue

@zoechi
Copy link

zoechi commented Jun 9, 2020

npm i -g [email protected] worked for me for Chromium 80.0.3987.162

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants