Skip to content

Conversation

imlucas
Copy link
Contributor

@imlucas imlucas commented Nov 19, 2015

linux builds going to fail, but at least this checkpoints us at a confirmed working version for windows and OS X so we can cut the Compass 0.6.1 release.

@imlucas
Copy link
Contributor Author

imlucas commented Nov 19, 2015

@imlucas imlucas force-pushed the windows-keytar branch 2 times, most recently from f6f321c to 69c71b5 Compare November 19, 2015 16:34
@kangas
Copy link
Contributor

kangas commented Nov 19, 2015

Something spooky is happening when I run "npm run ci" on Windows with this branch.

It appears that npm v2.14.11 is somehow getting invoked in the error below. Then note that npm v3.3.12 is correctly reported below.

C:\workspace\compass\build\node_modules\scout-server\node_modules\mongodb\node_modules\kerberos>if not defined npm_config_node_gyp (node "C:\workspace\compass\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  kerberos.cc
  worker.cc
  security_buffer.cc
  security_buffer_descriptor.cc
  security_context.cc
  security_credentials.cc
  base64.c
  kerberos_sspi.c
  win_delay_load_hook.c
     Creating library C:\workspace\compass\build\node_modules\scout-server\node_modules\mongodb\node_modules\kerberos\build\Release\kerberos.lib and object C:\workspace\compass\build\node_modules\scout-server\node_modules\mongodb\node_modules\kerberos\build\Release\kerberos.exp
  Generating code
  Finished generating code
  kerberos.vcxproj -> C:\workspace\compass\build\node_modules\scout-server\node_modules\mongodb\node_modules\kerberos\build\Release\\kerberos.node
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\workspace\\compass\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production" "--quiet" "--loglevel" "error"
npm ERR! node v4.2.2
npm ERR! npm  v2.14.11
npm ERR! path C:\workspace\data\npm-cache\forever-agent\0.6.1\package\package.json.66b024bb268310984f0e3671d8a57115
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall rename

npm ERR! Error: EPERM: operation not permitted, rename 'C:\workspace\data\npm-cache\forever-agent\0.6.1\package\package.json.66b024bb268310984f0e3671d8a57115' -> 'C:\workspace\data\npm-cache\forever-agent\0.6.1\package\package.json'
npm ERR!     at Error (native)
npm ERR!  { [Error: EPERM: operation not permitted, rename 'C:\workspace\data\npm-cache\forever-agent\0.6.1\package\package.json.66b024bb268310984f0e3671d8a57115' -> 'C:\workspace\data\npm-cache\forever-agent\0.6.1\package\package.json']
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'rename',
npm ERR!   path: 'C:\\workspace\\data\\npm-cache\\forever-agent\\0.6.1\\package\\package.json.66b024bb268310984f0e3671d8a57115',
npm ERR!   dest: 'C:\\workspace\\data\\npm-cache\\forever-agent\\0.6.1\\package\\package.json',
npm ERR!   parent: 'request' }
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!     C:\workspace\compass\build\npm-debug.log
[11:34:31] 'npm:install' errored after 4.8 min
[11:34:31] Error: Command `npm install --production --quiet --loglevel error` failed with exit code 4294963248
    at ChildProcess.exithandler (child_process.js:203:12)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:818:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
[11:34:31] 'release' errored after 4.88 min
[11:34:31] Error in plugin 'run-sequence'
Message:
    An error occured in task 'npm:install'.
[11:34:31] 'build' errored after 4.88 min
[11:34:31] Error in plugin 'run-sequence'
Message:
    An error occured in task 'release'.
[11:34:31] 'build' errored after 4.9 min
[11:34:31] Error in plugin 'run-sequence'
Message:
    An error occured in task 'npm:install'.

npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\workspace\\compass\\node_modules\\npm\\bin\\npm-cli.js" "run" "release"
npm ERR! node v4.2.2
npm ERR! npm  v2.14.11
npm ERR! code ELIFECYCLE
npm ERR! mongodb-compass@0.6.0 release: `gulp release`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mongodb-compass@0.6.0 release script 'gulp release'.
npm ERR! This is most likely a problem with the mongodb-compass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp release
npm ERR! You can get their info via:
npm ERR!     npm owner ls mongodb-compass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\workspace\compass\npm-debug.log

npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "ci"
npm ERR! node v4.2.2
npm ERR! npm  v3.3.12
npm ERR! code ELIFECYCLE
npm ERR! mongodb-compass@0.6.0 ci: `npm run check && npm test && npm run release`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mongodb-compass@0.6.0 ci script 'npm run check && npm test && npm run release'.

@imlucas
Copy link
Contributor Author

imlucas commented Nov 19, 2015

@imlucas
Copy link
Contributor Author

imlucas commented Nov 19, 2015

imlucas added a commit that referenced this pull request Nov 19, 2015
@imlucas imlucas merged commit b29423d into master Nov 19, 2015
@imlucas imlucas deleted the windows-keytar branch November 19, 2015 22:13
@imlucas imlucas restored the windows-keytar branch February 8, 2016 02:05
@durran durran deleted the windows-keytar branch December 1, 2016 15:17
@durran durran restored the windows-keytar branch December 1, 2016 15:17
@durran durran deleted the windows-keytar branch December 1, 2016 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants