Uploaded image for project: '[Read Only] - Addon Channel Manager'
  1. [Read Only] - Addon Channel Manager

Channel manager can not be build on Windows with front-end build v3.0 and NodeJs 6



    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 4.0.1, 4.1.0
    • Fix Version/s: 4.0.2, 4.1.0
    • Labels:
    • Similar issues:
    • Processed by team:
    • Sprint:
      Tiger Sprint 135


      On windows following error is shown and build is failed on Frontend next Generation after frontend is bumped to v3.0.0.Check below error

      node-pre-gyp ERR! Tried to download: https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.14/fse-v1.0.14-node-v48-win32-x64.tar.gz
      node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.14 and node@6.3.0 (node-v48 ABI) (falling back to source compile with node-gyp)
      gyp ERR! configure error
      gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
      gyp ERR! stack     at failNoPython (E:\channelmanager_4.0\frontend-ng\node_modules\node-gyp\lib\configure.js:449:14)
      gyp ERR! stack     at E:\channelmanager_4.0\frontend-ng\node_modules\node-gyp\lib\configure.js:404:11
      gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
      gyp ERR! System Windows_NT 6.1.7601
      gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "E:\\channelmanager_4.0\\frontend-ng\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=E:\\channelmanager_4.0\\frontend-ng\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node" "--module_name=fse" "-
      gyp ERR! cwd E:\channelmanager_4.0\frontend-ng\node_modules\fsevents
      gyp ERR! node -v v6.3.0
      gyp ERR! node-gyp -v v3.4.0
      gyp ERR! not ok
      node-pre-gyp ERR! build error
      node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe E:\channelmanager_4.0\frontend-ng\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=E:\channelmanager_4.0\frontend-ng\node_modules\fsevents\lib\binding\Release\node-v48-win32-x64\fse.node --module_name=fse
       --module_path=E:\channelmanager_4.0\frontend-ng\node_modules\fsevents\lib\binding\Release\node-v48-win32-x64' (1)
      node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (E:\channelmanager_4.0\frontend-ng\node_modules\fsevents\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
      node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
      node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
      node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:852:16)
      node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
      node-pre-gyp ERR! System Windows_NT 6.1.7601
      node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "E:\\channelmanager_4.0\\frontend-ng\\node_modules\\fsevents\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
      node-pre-gyp ERR! cwd E:\channelmanager_4.0\frontend-ng\node_modules\fsevents
      node-pre-gyp ERR! node -v v6.3.0
      node-pre-gyp ERR! node-pre-gyp -v v0.6.29
      node-pre-gyp ERR! not ok
      Failed to execute 'C:\Program Files\nodejs\node.exe E:\channelmanager_4.0\frontend-ng\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=E:\channelmanager_4.0\frontend-ng\node_modules\fsevents\lib\binding\Release\node-v48-win32-x64\fse.node --module_name=fse --module_path=E:\channelmanage
      r_4.0\frontend-ng\node_modules\fsevents\lib\binding\Release\node-v48-win32-x64' (1)
      npm ERR! Windows_NT 6.1.7601
      npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
      npm ERR! node v6.3.0
      npm ERR! npm  v3.10.3
      npm ERR! code ELIFECYCLE
      npm ERR! fsevents@1.0.14 install: `node-pre-gyp install --fallback-to-build`
      npm ERR! Exit status 1
      npm ERR!
      npm ERR! Failed at the fsevents@1.0.14 install script 'node-pre-gyp install --fallback-to-build'.
      npm ERR! Make sure you have the latest version of node.js and npm installed.
      npm ERR! If you do, this is most likely a problem with the fsevents package,
      npm ERR! not with npm itself.
      npm ERR! Tell the author that this fails on your system:
      npm ERR!     node-pre-gyp install --fallback-to-build
      npm ERR! You can get information on how to open an issue for this project with:
      npm ERR!     npm bugs fsevents
      npm ERR! Or if that isn't available, you can get their info via:
      npm ERR!     npm owner ls fsevents
      npm ERR! There is likely additional logging output above.
      npm ERR! Please include the following file with any support request:
      npm ERR!     E:\channelmanager_4.0\frontend-ng\npm-debug.log
      [INFO] ------------------------------------------------------------------------
      [INFO] Reactor Summary:
      [INFO] Hippo Addon Channel Manager ........................ SUCCESS [  1.466 s]
      [INFO] Addon Channel Manager Frontend API ................. SUCCESS [  3.466 s]
      [INFO] Addon Channel Manager Frontend Next Generation ..... FAILURE [ 28.359 s]
      [INFO] Addon Channel Manager Frontend ..................... SKIPPED
      [INFO] Addon Channel Manager Repository ................... SKIPPED
      [INFO] ------------------------------------------------------------------------
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 33.478 s
      [INFO] Finished at: 2016-07-21T11:37:23+02:00
      [INFO] Final Memory: 20M/451M
      [INFO] ------------------------------------------------------------------------
      [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:exec (npm-install) on project hippo-addon-channel-manager-frontend-ng: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
      [ERROR] After correcting the problems, you can resume the build with the command




            • Assignee:
              pgupta Pankaj Gupta (Inactive)
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: