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.

Sign up for GitHub

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

Jump to bottom

puppeteer unable to launch Chrome on Windows #154

Closed
Krinkle opened this issue Dec 28, 2018 · 3 comments
Closed

puppeteer unable to launch Chrome on Windows #154

Krinkle opened this issue Dec 28, 2018 · 3 comments

Comments

@Krinkle
Copy link
Contributor

Krinkle commented Dec 28, 2018

When using grunt-contrib-qunit on Travis CI with os: windows, it fails as follows:

>> There was an error with headless chrome
Fatal error: Failed to launch chrome!
[1228/225004.858:ERROR:main_dll_loader_win.cc(134)] Failed to load Chrome DLL from  node_modules\puppeteer\.local-chromium\win64-588429\chrome-win32\chrome.dll: The specified module could not be found. (0x7E)

I first encountered this when working on a commit that adds os: windows to the Travis CI build matrix of upstream qunitjs/qunit. But I was also able to reproduce it for this repository, at https://travis-ci.com/Krinkle/grunt-contrib-qunit/jobs/167451645.

Related reports}:
@Krinkle
Copy link
Contributor Author

Krinkle commented Dec 28, 2018

It looks like Chrome last worked correctly on "Windows Server 2016" during the Chromium 66 milestone, then was broken from Chromium 68 to 71, and fixed in Chromium 72.

Updating puppeteer to the latest version should do the trick.

Krinkle added a commit to Krinkle/grunt-contrib-qunit that referenced this issue Dec 28, 2018
@Krinkle
CI: Add Windows to Travis CI matrix
9180a0f 
Ref gruntjs#154.
Krinkle added a commit to Krinkle/grunt-contrib-qunit that referenced this issue Dec 28, 2018
@Krinkle
Update puppeteer to 1.11.0 with caret range
0baff9f 
Fixes gruntjs#154.
@Krinkle Krinkle mentioned this issue Dec 28, 2018
Merged
@Krinkle
Copy link
Contributor Author

Krinkle commented Dec 29, 2018

Thanks. Would also appreciate a minor release for the puppeteer update :)

@vladikoff
Copy link
Member

@Krinkle in 3.1.0 on npm

Krinkle added a commit to qunitjs/qunit that referenced this issue Dec 30, 2018
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix
56ec31a 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Fixes #1347.
Krinkle added a commit to qunitjs/qunit that referenced this issue Dec 30, 2018
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix
7aede99 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Fixes #1347.
@Krinkle Krinkle mentioned this issue Dec 30, 2018
Merged
Krinkle added a commit to qunitjs/qunit that referenced this issue Dec 30, 2018
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix
569c22c 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Fixes #1347.
Krinkle added a commit to qunitjs/qunit that referenced this issue Dec 30, 2018
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix
0856784 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Fixes #1347.
Krinkle added a commit to qunitjs/qunit that referenced this issue Dec 30, 2018
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix
c543b36 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Rename bin/qunit to bin/qunit.js, because otherwise ESLint fails:

> Expected linebreaks to be 'LF' but found 'CRLF'  linebreak-style

In theory, it should be possible to add an entry to `.gitattributes`
that will apply to bin/qunit what we apply to *.js, but I wasn't
able to find a way.

Fixes #1347.
Krinkle added a commit to qunitjs/qunit that referenced this issue Dec 30, 2018
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix
5494521 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Rename bin/qunit to bin/qunit.js, because otherwise ESLint fails:

> Expected linebreaks to be 'LF' but found 'CRLF'  linebreak-style

In theory, it should be possible to add an entry to `.gitattributes`
that will apply to bin/qunit what we apply to *.js, but I wasn't
able to find a way.

Fixes #1347.
Krinkle added a commit to qunitjs/qunit that referenced this issue Jan 2, 2019
@Krinkle
Build: Add macOS and Windows to the Travis CI test matrix (#1360)
681cee7 
Update grunt-contrib-qunit to 3.1.0, because grunt-contrib-qunit 3.0.1
uses a pinned (older) version of puppeteer. The older puppteer used an
older version of Chrome, which is incompatible with Windows Server 2016,
which is what Travis CI offers. AppVeyor was using Windows Server 2012,
whih was not affected by that Chrome bug.

Ref gruntjs/grunt-contrib-qunit#154.

For Windows, the build script is limited to `test:main`. This is the
same as it was before with AppVeyor, because the CLI tests are not passing
on Windows currently. Ref #1359.

Rename bin/qunit to bin/qunit.js, because otherwise ESLint fails:

> Expected linebreaks to be 'LF' but found 'CRLF'  linebreak-style

In theory, it should be possible to add an entry to `.gitattributes`
that will apply to bin/qunit what we apply to *.js, but I wasn't
able to find a way.

Fixes #1347.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vladikoff @Krinkle