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

Do not try to download Chromium by default #2364

Merged
merged 1 commit into from
May 21, 2019

Conversation

swissspidy
Copy link
Collaborator

This happens because the wordpress/scripts package depends on Puppeteer, which results in attempts to download Chromium when running npm install.

Once we use Puppeteer for end-to-end tests that can be run on Travis, we can enable the download again just for that stage. Until then, setting PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true should make Travis jobs a bit faster.

Related: #2363, WordPress/gutenberg#15712

This happens because the wordpress/scripts package depends on Puppeteer, which results in attempts to download Chromium when running `npm install`.

Once we use Puppeteer for end-to-end tests that can be run on Travis, we can enable the download again just for that stage.

Related: WordPress/gutenberg#15712
@googlebot googlebot added the cla: yes Signed the Google CLA label May 21, 2019
@westonruter
Copy link
Member

The directory where Chromium is being downloaded to could also be added to the list of cached directories.

@westonruter westonruter merged commit c949a0e into amp-stories-redux May 21, 2019
@westonruter westonruter deleted the fix/no-chromium-download branch May 21, 2019 13:36
@westonruter westonruter added this to the v1.2 milestone May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Signed the Google CLA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants