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

Update karma-phantomjs-launcher #896

Merged
merged 1 commit into from
Dec 24, 2016
Merged

Update karma-phantomjs-launcher #896

merged 1 commit into from
Dec 24, 2016

Conversation

hamhands
Copy link
Contributor

@hamhands hamhands commented Dec 2, 2016

Change

  • karma-phantomjs-launcher to ^1.0.2

Issues

@jgravois
Copy link
Contributor

jgravois commented Dec 2, 2016

even though Travis currently targets node v4, tests aren't passing and i can reproduce the same thing locally. these look like pretty much the same errors that crop up when running our test suite on node v6 (#815). apparently there's some interplay between karma and/or phantomjs too.

@jgravois jgravois merged commit 92e5e4c into Esri:master Dec 24, 2016
@jgravois
Copy link
Contributor

i've had a heck of a time the last couple days trying to sort out the cause of lots of different test errors.

for the time being i'm proposing in #906 that we revert this change and get things sorted in node 6 first, then revisit migrating to karma-phantomjs-launcher 1.0.2 (and consequently PhantomJS 2.x) again very soon.

jgravois added a commit to jgravois/esri-leaflet that referenced this pull request Apr 23, 2022
Update karma-phantomjs-launcher
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.

2 participants