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

Trying to fix CI #10983

Merged
merged 1 commit into from Apr 29, 2020
Merged

Trying to fix CI #10983

merged 1 commit into from Apr 29, 2020

Conversation

ahocevar
Copy link
Member

@ahocevar ahocevar commented Apr 29, 2020

Looks like recent versions of Puppeteer do not work with node 14, which is what CircleCI is using now. This pull request fixes the CI, which is broken for all new pull requests since some time yesterday.

@ahocevar ahocevar merged commit 0549951 into openlayers:master Apr 29, 2020
@ahocevar ahocevar deleted the fix-ci branch April 29, 2020 18:08
@tschaub
Copy link
Member

tschaub commented May 7, 2020

It looks like a bug in node that affected puppeteer has been fixed nodejs/node#32968. No reason to rush it, but it may be safe to upgrade again. See also puppeteer/puppeteer#5719.

@ahocevar
Copy link
Member Author

@tschaub Done already by @dependabot, in #11002.

@tschaub
Copy link
Member

tschaub commented May 11, 2020

#11002 brought in puppeteer@3.0.2, which only logged an error in Node 14. This update is what was causing builds to fail.

It looks like #11032 will bring in puppeteer@3.0.4, which is the version that works with Node 14.1 and doesn't log a warning (see puppeteer/puppeteer#5816).

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