bower install fails silently

[johanneswuerbach]

We have seen now multiple times on Travis that bower install just existed without installing any dependencies. bower install works fine on local, but on travis only sometimes.

As this is a private repo, here our files:
https://gist.github.com/johanneswuerbach/a1098a97da2c08fd2571

$ node --version
v0.8.25
$ npm --version
1.2.30
bower-1.2.4

Is there anything else I can provide to help fixing this issue?

[danielchatfield]

How long have you been having these issues? Travis is being very wobbly right now (I can't even load it at the moment).

[danielchatfield]

And the status board is completely useless: http://status.travis-ci.com/

All Systems Operational

[danielchatfield]

Travis is loading now. Could you post the full travis log?

[johanneswuerbach]

The issues appears since one or two weeks, I'll check, whether I can find a specific version. All other dependencies are installed successfully (npm, bundler), only bower fails without an error. We are using TravisPro, which seems to run fine atm.

Our app isn't testable without bower dependencies, so the first task which requires dependencies from bower fails (compiling bootstrap-sass), because the bower_components folder isn't created by bower. If I rebuild the task it works again in ~50% of the builds.

Warning: Errno::ENOENT on line ["33"] of /home/travis/.rvm/gems/ruby-1.9.3-p448/gems/compass-0.12.2/lib/compass/exec/global_options_parser.rb: No such file or directory - /home/travis/build/sixdoorsHQ/seller-html5/app/bower_components

[satazor]

The only silently fail reported till now is on unstable networks, see: #792.

If you count how many bower download occurrences exist in the log, there are exactly the same as bower extract (17). So one or more packages are ending unexpectedly in the extract step. This is exactly the same problem reported in #792. I will create an issue in node repository to get some help.

[satazor]

Watch nodejs/node-v0.x-archive#6143 to follow the discussion.