• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tmatilai / vagrant-proxyconf / 231 / 3
70%
master: 70%

Build:
DEFAULT BRANCH: master
Ran 03 Apr 2014 09:38AM UTC
Files 34
Run time 3s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Apr 2014 09:33AM UTC coverage: 77.196%. Remained the same
1.9.3, VAGRANT_VERSION=v1.2.7

Pull #59

travis-ci

spul
Test for npm availability in sudo context

npm proxy provider runs
@machine.communicate.sudo(command).

cap provider verifies availability of npm with `which' NOT
using sudo.

This may result in:
- which succeeds for the ssh user (mostly vagrant)
- machine.communicate.sudo('npm do something') does not
  succeed because sudo target user does not have the same
  PATH variable configured.

This may result in the following error message breaking the
Vagrant environment completely:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

npm config set proxy http://some.configured.proxy.here:8080/

Stdout from the command:

Stderr from the command:

bash: line 2: npm: command not found
Pull Request #59: Test for npm availability in sudo context

501 of 649 relevant lines covered (77.2%)

13.07 hits per line

Source Files on job 231.3 (1.9.3, VAGRANT_VERSION=v1.2.7)
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 231
  • Travis Job 231.3
  • 779d53f9 on github
  • Prev Job for 1.9.3, VAGRANT_VERSION=v1.2.7 on master (#230.3)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc