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

fix phantom use on travis #6536

Merged
merged 1 commit into from Dec 7, 2016
Merged

fix phantom use on travis #6536

merged 1 commit into from Dec 7, 2016

Conversation

kellyselden
Copy link
Member

I noticed an issue where phantom 1.9 was being used even though we were expecting 2.1 https://travis-ci.org/ember-cli/ember-addon-output/jobs/180486782#L447-L468

turns out we needed to install it globally. Here it is in action: https://travis-ci.org/kellyselden/ember-datetimepicker/jobs/181879916#L472

I targeted release branch because this seemed like a pretty silly/low risk bug fix that we should get to people soon.

@@ -27,8 +27,8 @@ before_install:
- npm config set spin false
- npm install -g bower
- bower --version
- npm install phantomjs-prebuilt
- node_modules/phantomjs-prebuilt/bin/phantomjs --version
- npm install -g phantomjs-prebuilt
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you combine that with the npm install -g bower call above? no need to invoke NPM twice :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@Turbo87 Turbo87 added the bug label Dec 7, 2016
@rwjblue
Copy link
Member

rwjblue commented Dec 7, 2016

Hmmm. Doesn't testem find the local node modules version first? Or does it only work if node_modules/.bin is in $PATH?

@Turbo87
Copy link
Member

Turbo87 commented Dec 7, 2016

I guess we'd have to ask @johanneswuerbach that 😉

@johanneswuerbach
Copy link
Contributor

Newer versions of testem should prefer locally installed modules. Which testem version were you using?

@kellyselden
Copy link
Member Author

So it looks like we have an issue with ember-try clearing out a local phantom install because it's not in the package.json.

This PR can be treated as a temp fix to get people back on phantom 2.1 while we figure out the real issue, or we can wait until the real fix comes along. I vote for temp fix. Thoughts?

@Turbo87
Copy link
Member

Turbo87 commented Dec 7, 2016

@kellyselden actually I think installing this globally is the right thing to do, not just a temp fix

@kellyselden
Copy link
Member Author

@nathanhammond or @Turbo87 can you verify I targeted this properly?

@Turbo87
Copy link
Member

Turbo87 commented Dec 7, 2016

@kellyselden yeah, should be good IMHO

@rwjblue
Copy link
Member

rwjblue commented Dec 7, 2016

@homu r+

@homu
Copy link
Contributor

homu commented Dec 7, 2016

📌 Commit b1e2099 has been approved by rwjblue

@homu
Copy link
Contributor

homu commented Dec 7, 2016

⚡ Test exempted - status

@homu homu merged commit b1e2099 into ember-cli:release Dec 7, 2016
homu added a commit that referenced this pull request Dec 7, 2016
fix phantom use on travis

I noticed an issue where phantom 1.9 was being used even though we were expecting 2.1 https://travis-ci.org/ember-cli/ember-addon-output/jobs/180486782#L447-L468

turns out we needed to install it globally. Here it is in action: https://travis-ci.org/kellyselden/ember-datetimepicker/jobs/181879916#L472

I targeted release branch because this seemed like a pretty silly/low risk bug fix that we should get to people soon.
@nathanhammond
Copy link
Contributor

LGTM

@kellyselden kellyselden deleted the travis branch December 7, 2016 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants