npm install fails on windows #284

sergioharo · 2015-01-28T20:07:07Z

Our current build process (on windows) is failing on version 1.9.15. The last successful build used 1.9.13. We get the following stack trace:

[email protected] install d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs
node install.js

Download already available at C:\Users\tempuser\AppData\Local\Temp\phantomjs\phantomjs-1.9.8-windows.zip
Extracting zip contents
Phantom installation failed [Error: Can't move source into dest if dest is in source.] Error: Can't move source into dest if dest is in source.
at mv (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\fs-extra\lib\move.js:22:15)
at fs.move (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\fs-extra\lib\index.js:51:3)
at onBoundPromise (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\kew\kew.js:703:10)
at Object.nfcall (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\kew\kew.js:685:44)
at Promise._successFn (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\install.js:341:20)
at Promise._call (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\kew\kew.js:373:13)
at Promise._withInput (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\kew\kew.js:333:25)
at Promise.resolve (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\kew\kew.js:105:27)
at resolver (d:\builds\jenkins\workspace\js\unit-tests\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\node_modules\kew\kew.js:409:17)
at CB (d:\builds\jenkins\workspace\js\unit-tests\node_modules\rimraf\rimraf.js:68:5)
npm ERR! [email protected] install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls phantomjs
npm ERR! There is likely additional logging output above.

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" "--loglevel" "warn"
npm ERR! cwd d:\builds\jenkins\workspace\js\unit-tests
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npmBuild step 'Conditional steps (multiple)' marked build as failure

Our package.json includes the following dependencies:
{
"karma": "^0.12.1",
"karma-jasmine": "^0.2.2",
"karma-requirejs": "^0.2.1",
"karma-phantomjs-launcher": "^0.1.2",
"karma-chrome-launcher": "^0.1.3",
"karma-coverage": "^0.2.1",
"karma-ng-html2js-preprocessor": "^0.1.0",
"karma-junit-reporter": "^0.2.2",
"rimraf": "^2.2.8"
}

Adding 1.9.13 to the dependencies fixes our build

The text was updated successfully, but these errors were encountered:

nicks · 2015-01-28T20:13:37Z

is that the full error log? It's conspicuously missing some important information.

sergioharo · 2015-01-28T20:16:35Z

Thats what shows up in our jenkins log. If you're looking for something specific, let me know and I can look around for it or turn up the log level. Its currently set to warn on npm.

adammlr · 2015-01-28T20:37:08Z

I'm also getting the issue now

nicks · 2015-01-28T20:40:02Z

we need the logs on what it's trying to copy where. Those logs show up for me; I don't know where they're getting eaten in your pipeline.

adammlr · 2015-01-28T20:40:38Z

[email protected] install D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs
node install.js

Download already available at C:\Temp\phantomjs\phantomjs-1.9.8-windows.zip
Extracting zip contents
Removing D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\lib\phantom
Copying extracted folder C:\Temp\phantomjs\phantomjs-1.9.8-windows.zip-extract-1422477496915\phantomjs-1.9.8-windows -> D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phant
omjs\lib\phantom
Phantom installation failed [Error: Can't move source into dest if dest is in source.] Error: Can't move source into dest if dest is in source.
at mv (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\fs-extra\lib\move.js:22:15)
at fs.move (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\fs-extra\lib\index.js:51:3)
at onBoundPromise (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\kew\kew.js:703:10)
at Object.nfcall (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\kew\kew.js:685:44)
at Promise._successFn (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\install.js:341:20)
at Promise._call (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\kew\kew.js:373:13)
at Promise._withInput (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\kew\kew.js:333:25)
at Promise.resolve (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\kew\kew.js:105:27)
at resolver (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\kew\kew.js:409:17)
at CB (D:\Apps\ContentDirect\Consumer\HTML\Build\node_modules\phantomjs\node_modules\fs-extra\node_modules\rimraf\rimraf.js:68:5)
npm ERR! [email protected] install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls phantomjs
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master/v/0.10.33/node.exe" "C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-
master\bin\node_modules\npm\bin\npm-cli.js" "install" "phantomjs"
npm ERR! cwd D:\Apps\ContentDirect\Consumer\HTML\Build
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.6
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\Apps\ContentDirect\Consumer\HTML\Build\npm-debug.log
npm ERR! not ok code 0

nicks · 2015-01-28T20:50:53Z

thanks, i filed this as jprichardson/node-fs-extra#109

nicks · 2015-01-28T20:55:29Z

for now, I think you can work around this by setting the TEMP environment variable to a directory on the same drive as your install directory

sergioharo · 2015-01-28T21:01:42Z

cool, thanks!

jprichardson · 2015-01-28T21:03:58Z

@sergioharo Can you try again? The phantomjs will now use the latest [email protected].

adammlr · 2015-01-28T21:06:38Z

seems to have fixed it for me. Thanks for the quick turn around.

nicks · 2015-01-28T21:17:02Z

ya, @jprichardson is pretty fast ⚡ ⚡ ⚡ . thanks all.

sergioharo · 2015-01-28T21:43:41Z

Yep, fixed for me too

prettycode · 2015-03-21T07:54:57Z

What version of phantomjs do I need to use to get the version that uses [email protected]? Using 1.9.15 and having this issue.

jprichardson · 2015-03-21T10:50:20Z

fs-extra author here. Have you verified that 0.16.3 works and that 0.16.5
does not?

On Saturday, March 21, 2015, Chris [email protected] wrote:

What version of phantomjs node package do I need to use to get the version
that uses [email protected]?

—
Reply to this email directly or view it on GitHub
#284 (comment).

Simple & Secure Bitcoin Wallet: https://www.coinbolt.com
Bitcoin / JavaScript: http://cryptocoinjs.com
Follow JP Richardson on Twitter: https://twitter.com/jprichardson

jprichardson · 2015-03-21T11:06:43Z

Also, if you could verify 0.16.4. I could then revert the offending patches
and publish 0.16.6.

On Saturday, March 21, 2015, JP Richardson [email protected] wrote:

fs-extra author here. Have you verified that 0.16.3 works and that 0.16.5
does not?

On Saturday, March 21, 2015, Chris <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

What version of phantomjs node package do I need to use to get the
version that uses [email protected]?

—
Reply to this email directly or view it on GitHub
#284 (comment).

Simple & Secure Bitcoin Wallet: https://www.coinbolt.com
Bitcoin / JavaScript: http://cryptocoinjs.com
Follow JP Richardson on Twitter: https://twitter.com/jprichardson

Simple & Secure Bitcoin Wallet: https://www.coinbolt.com
Bitcoin / JavaScript: http://cryptocoinjs.com
Follow JP Richardson on Twitter: https://twitter.com/jprichardson

prettycode · 2015-03-21T21:58:44Z

@jprichardson Actually, this issue appears to better capture what I'm experiencing: #297.

It's hard to reproduce. Happens about 1/5 installs. It's running on our build server and randomly, what's shown in that issued I linked, happens. We've been using 1.9.15 the whole time, so couldn't tell you about other versions.

Sorry to cause alarm. There's definitely a problem, but have no idea about fs-extra's dependency being involved.

nicks closed this as completed Jan 28, 2015

nicks mentioned this issue Jan 29, 2015

npm install failure after 1.9.15 on Windows 2008 Server #286

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

npm install fails on windows #284

npm install fails on windows #284

sergioharo commented Jan 28, 2015

nicks commented Jan 28, 2015

sergioharo commented Jan 28, 2015

adammlr commented Jan 28, 2015

nicks commented Jan 28, 2015

adammlr commented Jan 28, 2015

nicks commented Jan 28, 2015

nicks commented Jan 28, 2015

sergioharo commented Jan 28, 2015

jprichardson commented Jan 28, 2015

adammlr commented Jan 28, 2015

nicks commented Jan 28, 2015

sergioharo commented Jan 28, 2015

prettycode commented Mar 21, 2015

jprichardson commented Mar 21, 2015

jprichardson commented Mar 21, 2015

prettycode commented Mar 21, 2015

npm install fails on windows #284

npm install fails on windows #284

Comments

sergioharo commented Jan 28, 2015

nicks commented Jan 28, 2015

sergioharo commented Jan 28, 2015

adammlr commented Jan 28, 2015

nicks commented Jan 28, 2015

adammlr commented Jan 28, 2015

nicks commented Jan 28, 2015

nicks commented Jan 28, 2015

sergioharo commented Jan 28, 2015

jprichardson commented Jan 28, 2015

adammlr commented Jan 28, 2015

nicks commented Jan 28, 2015

sergioharo commented Jan 28, 2015

prettycode commented Mar 21, 2015

jprichardson commented Mar 21, 2015

jprichardson commented Mar 21, 2015

prettycode commented Mar 21, 2015