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

Work around issue with Node v14 and Puppeteer #2086

Merged
merged 1 commit into from Apr 27, 2020

Conversation

robertknight
Copy link
Member

Use the system version of Chrome if the developer has Node v14
installed, to work around an upstream issue with Puppeteer (see code
comment).

The observed behavior under Node 14 is that running make test fails with an error about Chrome not being captured (ie. Karma failed to launch Chrome)

Further details: puppeteer/puppeteer#5719

Use the system version of Chrome if the developer has Node v14
installed, to work around an upstream issue with Puppeteer (see code
comment).
@codecov
Copy link

codecov bot commented Apr 27, 2020

Codecov Report

Merging #2086 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2086   +/-   ##
=======================================
  Coverage   97.02%   97.02%           
=======================================
  Files         185      185           
  Lines        6213     6213           
  Branches     1395     1395           
=======================================
  Hits         6028     6028           
  Misses        185      185           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5f2824a...74253d1. Read the comment docs.

@robertknight robertknight merged commit 9ca6cf3 into master Apr 27, 2020
@robertknight robertknight deleted the node-v14-puppeteer-workaround branch April 27, 2020 16:25
robertknight added a commit to hypothesis/browser-extension that referenced this pull request Apr 28, 2020
Apply the same fix as was used in the "client" repo in
hypothesis/client#2086.
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.

None yet

2 participants