I just encountered this for the first time - which is kind of surprising!

Apparently, composer uses the GitHub API and there is a limit on the number of API requests from a particular IP or user. On Travis-CI, there are tons of projects using composer at the same time this will randomly occur.

According to this issue, adding --no-interaction to the composer command will stop it from using the GitHub API:

https://github.com/composer/composer/issues/1314

Needs to be tested!

CommentFileSizeAuthor
#7 issue-2185405.patch577 byteslsolesen

Comments

dsnopek’s picture

Status: Active » Fixed

Added the --no-interaction argument. Let's hope this works! No way to test except to see if it comes up again.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

dsnopek’s picture

Component: Code » Admin
Status: Closed (fixed) » Active

It looks like I re-introduced this issue by fixing: #2195445: Install Drush on Travis-CI via 'composer' rather than 'pear'

Now that we're using composer in a different place, I have to put the fix there too!

dsnopek’s picture

Tried --no-interaction and it appears to not have worked:

https://travis-ci.org/lsolesen/panopoly/jobs/18885859

Back to the drawing board!

Ari Gold’s picture

Have you tried --prefer-source ? Before trying it my builds stopped with "Errored"

With --prefer-source it seems to not use Github API and does not show "Errored" but then behat exits with status 255. Even though all behat tests pass the build "Fails"

https://travis-ci.org/ASU/webspark-drops-drupal7/builds/19999657

lsolesen’s picture

I just successfully used --prefer-source without the 255 exit status on Behat - and since I introduced it there is no Github Errored messages anymore (which was very frequent before).

lsolesen’s picture

Status: Active » Needs review
StatusFileSize
new577 bytes

This is what I succesfully used on Commerce Kickstart.

  • Commit ec48f2a on 7.x-1.x authored by lsolesen, committed by dsnopek:
    Issue #2185405: Builds on Travis-CI will randomly fail if over GitHub...
dsnopek’s picture

Status: Needs review » Fixed

Thanks @lsolesen and @arielqgold! I hope this is finally the end of this very frustrating issue. :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.