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

CI Build Fixes. #2941

Merged
merged 1 commit into from
Aug 1, 2016
Merged

CI Build Fixes. #2941

merged 1 commit into from
Aug 1, 2016

Conversation

bd82
Copy link
Contributor

@bd82 bd82 commented Jul 27, 2016

CI Build Fixes.

In Short:

  • Enable Travis Cache to mitigate phantomjs download issues.
  • Enable Travis & appveyor functionality to avoid race condition on CI builds
    and old node.js version (0.10/0.12)

Details:

Using https://bitbucket.org/ariya/phantomjs/downloads/
to download phantom (on travis) instead of http://cnpmjs.org/downloads
because Travis downloads from http://cnpmjs.org/downloads are horribly slow (30k/s)
and seem courrpt most of the time (smells like throttling)

Travis caching is by branch + build env (node version).
But it has a fallback to using the cache from the default branch
so it should help even with pull requests (which are new branches).

Secondly using travis_retry and appveyor_retry for npm install
to workaround race condition on with npm install and older versions of node.

mitigates #2898

@bd82 bd82 changed the title Enable Travis Cache to mitigate phantomjs download issues. CI Build Fixes. Jul 27, 2016
@bd82
Copy link
Contributor Author

bd82 commented Jul 28, 2016

integrated workaround for appveyor_retry from #2943

In Short:
* Enable Travis Cache to mitigate phantomjs download issues.
* Enable Travis & appveyor <retry> functionality to avoid race condition on CI builds
  and old node.js version (0.10/0.12)

Details:

Using <https://bitbucket.org/ariya/phantomjs/downloads/>
to download phantom (on travis)  instead of <http://cnpmjs.org/downloads>
because Travis downloads from http://cnpmjs.org/downloads are horribly slow (30k/s)
and seem courrpt most of the time (smells like throttling)

Travis caching is by branch + build env (node version).
But it has a fallback to using the cache from the default branch
so it should help even with pull requests (which are new branches).

Secondly using <travis_retry> and <appveyor_retry> for <npm install>
to workaround race condition on with npm install and older versions of node.

mitigates #2898
@matthew-dean matthew-dean merged commit 6399ebc into less:3.x Aug 1, 2016
@matthew-dean
Copy link
Member

Thanks!

@matthew-dean
Copy link
Member

@bd82 Can you look at why Travis is failing here and not Appveyor? #3158

@bd82
Copy link
Contributor Author

bd82 commented Jan 27, 2018

Had a look, but no idea as it seems to only fail on node.js version 6 on travis not on travis in general.

It also failed during the execution of the phantomjs tests not during the download phase.
Did you attempt to retry it? maybe it just randomly failed?

Also you may want to look into using something a a bit more modern for testing like Chrome Headless.

@matthew-dean
Copy link
Member

@bd82 I agree Chrome Headless is better option. Just don't have the cycles to do it.

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