Description

Trott

opened on Oct 13, 2016

Issue body actions

test-npm-install is currently failing consistently on freebsd11-x64 in CI.

Example failure: https://ci.nodejs.org/job/node-test-commit-freebsd/4792/nodes=freebsd11-x64/console

not ok 737 parallel/test-npm-install
# 
# assert.js:85
#   throw new assert.AssertionError({
#   ^
# AssertionError: npm install should run without an error
#     at ChildProcess.handleExit (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/parallel/test-npm-install.js:48:10)
#     at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/common.js:422:15)
#     at emitTwo (events.js:106:13)
#     at ChildProcess.emit (events.js:191:7)
#     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
  ---
  duration_ms: 2.45

/cc @thealphanerd @nodejs/testing

Activity

1. Trott

   added

   testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.

   freebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.

   npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.

   on Oct 13, 2016
2. Trott commented on Oct 13, 2016

   

   Trott

   on Oct 13, 2016

   MemberAuthor

   More actions

   It's a permissions issue.

   [iojs@test-digitalocean-freebsd11-x64-1 ~/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/tmp]$ ../../node ../../deps/npm/bin/npm-cli.js install
   npm ERR! tar.pack Could not write /home/iojs/.npm/package-name/1.2.3/package.tgz
   npm ERR! addLocalDirectory Could not pack /home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/fixtures/packages/main to /home/iojs/.npm/package-name/1.2.3/package.tgz
   npm ERR! addLocal Could not install /home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/fixtures/packages/main
   npm ERR! FreeBSD 11.0-RELEASE-p1
   npm ERR! argv "/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/out/Release/node" "/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/deps/npm/bin/npm-cli.js" "install"
   npm ERR! node v7.0.0-pre
   npm ERR! npm  v3.10.8
   npm ERR! path /home/iojs/.npm/package-name/1.2.3/package.tgz.4069004711
   npm ERR! code EACCES
   npm ERR! errno -13
   npm ERR! syscall open
   
   npm ERR! Error: EACCES: permission denied, open '/home/iojs/.npm/package-name/1.2.3/package.tgz.4069004711'
   npm ERR!  { Error: EACCES: permission denied, open '/home/iojs/.npm/package-name/1.2.3/package.tgz.4069004711'
   npm ERR!   errno: -13,
   npm ERR!   code: 'EACCES',
   npm ERR!   syscall: 'open',
   npm ERR!   path: '/home/iojs/.npm/package-name/1.2.3/package.tgz.4069004711' }
   npm ERR! 
   npm ERR! Please try running this command again as root/Administrator.
   
   npm ERR! Please include the following file with any support request:
   npm ERR!     /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/tmp/npm-debug.log
   [iojs@test-digitalocean-freebsd11-x64-1 ~/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/tmp]$
   
3. joaocgreis

   added a commit that references this issue on Oct 13, 2016

   test: use npm sandbox in test-npm-install

   06498b0
4. joaocgreis commented on Oct 13, 2016

   

   joaocgreis

   on Oct 13, 2016

   Member

   More actions

   Proposed solution: #9079
5. jbergstroem

   changed the title [-]test-npm-install failing on freebsd11-x64[/-] [+]test-npm-install failing on freebsd 10/11[/+] on Oct 13, 2016
6. jbergstroem commented on Oct 13, 2016

   

   jbergstroem

   on Oct 13, 2016

   Member

   More actions

   The problem was that jenkins slave ran as root prior. I've adjusted permissions but I'd still like to see #9079 land.
7. joaocgreis

   closed this as completedin 1847670on Oct 17, 2016
8. jasnell

   added a commit that references this issue on Oct 17, 2016

   test: use npm sandbox in test-npm-install

   47863a5
9. MylesBorins

   added 2 commits that reference this issue on Nov 11, 2016

   test: use npm sandbox in test-npm-install

   def6874

   test: use npm sandbox in test-npm-install

   f9b24f4

Issue actions