Cannot install urchin on windows 7 #5737

Closed
zonplm opened this Issue Jul 20, 2014 · 2 comments

Projects

None yet

3 participants

zonplm commented Jul 20, 2014

ERR! Error: ENOENT, open 'C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package\tests\Urchin should do a sanity check so that directories like the user home are not specified as tests.\If Urchin is run on a file named something like "test", no Molly-guard should be presented.'

C:\Users\tpm-dev>npm install -g urchin

npm http GET https://registry.npmjs.org/urchin
npm http 304 https://registry.npmjs.org/urchin
npm http GET https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz
npm http 200 https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz
npm ERR! Error: ENOENT, open 'C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package\tests\Urchin should do a sanity check so that directories like the user home are not specified as tests.\If Urchin is run
on a file named something like "test", no Molly-guard should be presented.'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "urchin"
npm ERR! cwd C:\Users\tpm-dev
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! path C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package\tests\Urchin should do a sanity check so that directories like the user home are
something like "test", no Molly-guard should be presented.
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\tpm-dev\npm-debug.log
npm ERR! not ok code 0

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   'urchin' ]
2 info using npm@1.4.9
3 info using node@v0.10.28
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 verbose cache add [ 'urchin', null ]
6 verbose cache add name=undefined spec="urchin" args=["urchin",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url   slashes: null,
7 verbose parsed url   auth: null,
7 verbose parsed url   host: null,
7 verbose parsed url   port: null,
7 verbose parsed url   hostname: null,
7 verbose parsed url   hash: null,
7 verbose parsed url   search: null,
7 verbose parsed url   query: null,
7 verbose parsed url   pathname: 'urchin',
7 verbose parsed url   path: 'urchin',
7 verbose parsed url   href: 'urchin' }
8 silly lockFile cf7c6f07-urchin urchin
9 verbose lock urchin C:\Users\tpm-dev\AppData\Roaming\npm-cache\cf7c6f07-urchin.lock
10 silly lockFile cf7c6f07-urchin urchin
11 silly lockFile cf7c6f07-urchin urchin
12 verbose addNamed [ 'urchin', '' ]
13 verbose addNamed [ null, '*' ]
14 silly lockFile eda9e205-urchin urchin@
15 verbose lock urchin@ C:\Users\tpm-dev\AppData\Roaming\npm-cache\eda9e205-urchin.lock
16 silly addNameRange { name: 'urchin', range: '*', hasData: false }
17 verbose url raw urchin
18 verbose url resolving [ 'https://registry.npmjs.org/', './urchin' ]
19 verbose url resolved https://registry.npmjs.org/urchin
20 info trying registry request attempt 1 at 17:26:20
21 verbose etag "78R3FE03KSGD5RHUW759YOE3J"
22 http GET https://registry.npmjs.org/urchin
23 http 304 https://registry.npmjs.org/urchin
24 silly registry.get cb [ 304,
24 silly registry.get   { date: 'Sun, 20 Jul 2014 21:26:20 GMT',
24 silly registry.get     server: 'Apache',
24 silly registry.get     via: '1.1 varnish',
24 silly registry.get     'last-modified': 'Sun, 20 Jul 2014 21:26:21 GMT',
24 silly registry.get     'cache-control': 'max-age=60',
24 silly registry.get     etag: '"78R3FE03KSGD5RHUW759YOE3J"',
24 silly registry.get     'x-served-by': 'cache-iad2125-IAD',
24 silly registry.get     'x-cache': 'MISS',
24 silly registry.get     'x-cache-hits': '0',
24 silly registry.get     'x-timer': 'S1405891580.807481,VS0,VE198',
24 silly registry.get     vary: 'Accept',
24 silly registry.get     'content-length': '0',
24 silly registry.get     'keep-alive': 'timeout=10, max=50',
24 silly registry.get     connection: 'Keep-Alive' } ]
25 verbose etag urchin from cache
26 silly addNameRange number 2 { name: 'urchin', range: '*', hasData: true }
27 silly addNameRange versions [ 'urchin', [ '0.0.0', '0.0.1', '0.0.2' ] ]
28 verbose addNamed [ 'urchin', '0.0.2' ]
29 verbose addNamed [ '0.0.2', '0.0.2' ]
30 silly lockFile f2d3582f-urchin-0-0-2 urchin@0.0.2
31 verbose lock urchin@0.0.2 C:\Users\tpm-dev\AppData\Roaming\npm-cache\f2d3582f-urchin-0-0-2.lock
32 silly lockFile d0e3b176-pmjs-org-urchin-urchin-0-0-2-tgz https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz
33 verbose lock https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz C:\Users\tpm-dev\AppData\Roaming\npm-cache\d0e3b176-pmjs-org-urchin-urchin-0-0-2-tgz.lock
34 verbose addRemoteTarball [ 'https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz',
34 verbose addRemoteTarball   '636461e40545e475fa55467b65aac9f0e629d9ee' ]
35 info retry fetch attempt 1 at 17:26:21
36 verbose fetch to= C:\Users\tpm-dev\AppData\Local\Temp\npm-8156-_N-xmK6n\1405891581114-0.3310684096068144\tmp.tgz
37 http GET https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz
38 http 200 https://registry.npmjs.org/urchin/-/urchin-0.0.2.tgz
39 verbose tar unpack C:\Users\tpm-dev\AppData\Local\Temp\npm-8156-_N-xmK6n\1405891581114-0.3310684096068144\tmp.tgz
40 silly lockFile c731fb18-g-npm-cache-urchin-0-0-2-package tar://C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package
41 verbose lock tar://C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package C:\Users\tpm-dev\AppData\Roaming\npm-cache\c731fb18-g-npm-cache-urchin-0-0-2-package.lock
42 silly lockFile 473ed1c0-81114-0-3310684096068144-tmp-tgz tar://C:\Users\tpm-dev\AppData\Local\Temp\npm-8156-_N-xmK6n\1405891581114-0.3310684096068144\tmp.tgz
43 verbose lock tar://C:\Users\tpm-dev\AppData\Local\Temp\npm-8156-_N-xmK6n\1405891581114-0.3310684096068144\tmp.tgz C:\Users\tpm-dev\AppData\Roaming\npm-cache\473ed1c0-81114-0-3310684096068144-tmp-tgz.lock
44 silly gunzTarPerm modes [ '755', '644' ]
45 silly gunzTarPerm extractEntry package.json
46 silly gunzTarPerm extractEntry .npmignore
47 silly gunzTarPerm extractEntry LICENCE
48 silly gunzTarPerm extractEntry .gitmodules
49 silly gunzTarPerm extractEntry HISTORY
50 silly gunzTarPerm extractEntry cross-shell-tests
51 silly gunzTarPerm extractEntry readme.md
52 silly gunzTarPerm extractEntry tests/.npmignore
53 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup_dir runs only oncea
54 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup
55 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup has run twice b
56 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup_dir
57 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup_dir runs
58 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup has run twice a
59 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/setup_dir runs only onceb
60 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/teardown
61 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/teardown has run twice a
62 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/teardown has run twice b
63 silly gunzTarPerm extractEntry tests/Setup and teardown/.test/teardown_dir
64 silly gunzTarPerm extractEntry tests/Setup and teardown/_dir files should be run once per directory, and the others should be run once per file.
65 silly gunzTarPerm extractEntry tests/- directories starting with a hypen.../Should work
66 silly gunzTarPerm extractEntry tests/Command-line help contents/The -f flag should be documented.
67 silly gunzTarPerm extractEntry tests/Command-line help contents/Urchin should exit 0 if run with the -h flag.
68 silly gunzTarPerm extractEntry tests/Command-line help contents/Urchin should exit 1 if help is displayed without being requested.
69 silly gunzTarPerm extractEntry tests/Command-line help contents/XSD output (-xsd flag) should be documented.
70 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/faila
71 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/failb
72 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/failc
73 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passa
74 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passb
75 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passc
76 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passd
77 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passe
78 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passf
79 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test/passg
80 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test-one/fail
81 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./.test-one/pass
82 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./Singular form is used for a single failure.
83 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./Singular form is used for a single pass.
84 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./There should be seven successes.
85 silly gunzTarPerm extractEntry tests/Counts should be kept of successes and failures./There should be three failures.
86 silly gunzTarPerm extractEntry tests/Exit codes of zero should pass.
87 silly gunzTarPerm extractEntry tests/Failing tests should be marked in red.
88 silly gunzTarPerm extractEntry tests/.example-test-suite/this should fail
89 silly gunzTarPerm extractEntry tests/.example-test-suite/this should pass
90 silly gunzTarPerm extractEntry tests/Succeeding tests should be marked in green.
91 silly gunzTarPerm extractEntry tests/The setup script should not be sourced./A variable exported from setup should not be visible in an associated test script.
92 silly gunzTarPerm extractEntry tests/The setup script should not be sourced./setup
93 silly gunzTarPerm extractEntry tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./.chainsaw/successful test
94 silly gunzTarPerm extractEntry tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./.test/successful test
95 silly gunzTarPerm extractEntry tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./If Urchin is run on a file named something like "test", no Molly-guard should be presented.
96 silly gunzTarPerm extractEntry tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./The -f flag should disable the Molly-guard.
97 silly gunzTarPerm extractEntry tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./Urchin should warn if it is run on something that does not look like a test.
98 silly gunzTarPerm extractEntry tests/Urchin should recognize that the filesystem is sane./.fixtures/bladyblah
99 silly gunzTarPerm extractEntry tests/Urchin should recognize that the filesystem is sane./The bin directory should exist.
100 silly gunzTarPerm extractEntry tests/Urchin should recognize that the filesystem is sane./The file "bladyblah" should contain the phrase "blah".
101 silly gunzTarPerm extractEntry tests/Urchin should recognize that the filesystem is sane./The filesystem root directory should exist.
102 silly gunzTarPerm extractEntry tests/Urchin should recognize that the filesystem is sane./The filesystem route should contain no "aoeuaoeuaoeu" file.
103 silly gunzTarPerm extractEntry tests/XSD output should work./.fixture/fail
104 silly gunzTarPerm extractEntry tests/XSD output should work./.fixture/pass
105 silly gunzTarPerm extractEntry tests/XSD output should work./XSD output should produce XML.
106 silly gunzTarPerm extractEntry tests/setup
107 silly gunzTarPerm extractEntry tests/teardown
108 silly gunzTarPerm extractEntry urchin
109 error Error: ENOENT, open 'C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package\tests\Urchin should do a sanity check so that directories like the user home are not specified as tests.\If Urchin is run on a file named something like "test", no Molly-guard should be presented.'
110 error If you need help, you may report this *entire* log,
110 error including the npm and node versions, at:
110 error     <http://github.com/npm/npm/issues>
111 error System Windows_NT 6.1.7601
112 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "urchin"
113 error cwd C:\Users\tpm-dev
114 error node -v v0.10.28
115 error npm -v 1.4.9
116 error path C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package\tests\Urchin should do a sanity check so that directories like the user home are not specified as tests.\If Urchin is run on a file named something like "test", no Molly-guard should be presented.
117 error code ENOENT
118 error errno 34
119 verbose exit [ 34, true ]
@othiym23 othiym23 changed the title from Cannot install urchin on windows 7: ERR! Error: ENOENT, open 'C:\Users\tpm-dev\AppData\Roaming\npm-cache\urchin\0.0.2\package\tests\Urchin should do a sanity check so that directories like the user home are not specified as tests.\If Urchin is run on a file named something like "test", no Molly-guard should be presented.' to Cannot install urchin on windows 7 Jul 20, 2014
@othiym23 othiym23 added the windows label Jul 20, 2014
Contributor
smikes commented Dec 27, 2014

Is this still a problem for you?

This looks like it was a race condition in older versions of npm.

There have been a lot of improvements to npm -- especially around conflicts and race conditions during install -- since 1.4.9. Can you try updating your npm installation?

To update npm on Windows, follow the instructions here: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)

Thanks!

Contributor

Closing as abandoned.

@othiym23 othiym23 closed this Jan 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment