luoxiao123 commented on issue #10997:
URL: 
https://github.com/apache/incubator-superset/issues/10997#issuecomment-734629681


   0 info it worked if it ends with ok
   1 verbose cli [
   1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
   1 verbose cli   
'C:\\Users\\lx\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
   1 verbose cli   'run',
   1 verbose cli   'build'
   1 verbose cli ]
   2 info using [email protected]
   3 info using [email protected]
   4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
   5 info lifecycle [email protected]~prebuild: [email protected]
   6 info lifecycle [email protected]~build: [email protected]
   7 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true
   8 verbose lifecycle [email protected]~build: PATH: 
C:\Users\lx\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\lx_workspace\pythonspace\workspace5\incubator-superset-0.38.0\superset-frontend\node_modules\.bin;E:\lx_workspace\xshell\;C:\Windows\System32;c:\windows\system32\WindowsPowershell\v1.0;E:\lx_workspace\jdk_dir\jdk1.8.0_191\bin;E:\lx_workspace\jdk_dir\jdk1.8.0_191\jre\bin;C:\Users\lx\Android\Sdk\platform-tools;C:\Program
 Files\Git\cmd;C:\Program 
Files\nodejs\;E:\lx_soft\Tesseract-OCR;E:\lx_workspace\pythonspace\sdk3.7.7;E:\lx_workspace\pythonspace\sdk3.7.7\Scripts;C:\Users\lx\AppData\Roaming\npm
   9 verbose lifecycle [email protected]~build: CWD: 
E:\lx_workspace\pythonspace\workspace5\incubator-superset-0.38.0\superset-frontend
   10 silly lifecycle [email protected]~build: Args: [
   10 silly lifecycle   '/d /s /c',
   10 silly lifecycle   'cross-env NODE_OPTIONS=--max_old_space_size=8192 
NODE_ENV=production webpack --mode=production --colors'
   10 silly lifecycle ]
   11 silly lifecycle [email protected]~build: Returned: code: 2  signal: null
   12 info lifecycle [email protected]~build: Failed to exec build script
   13 verbose stack Error: [email protected] build: `cross-env 
NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production webpack 
--mode=production --colors`
   13 verbose stack Exit status 2
   13 verbose stack     at EventEmitter.<anonymous> 
(C:\Users\lx\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
   13 verbose stack     at EventEmitter.emit (events.js:310:20)
   13 verbose stack     at ChildProcess.<anonymous> 
(C:\Users\lx\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
   13 verbose stack     at ChildProcess.emit (events.js:310:20)
   13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
   13 verbose stack     at Process.ChildProcess._handle.onexit 
(internal/child_process.js:286:5)
   14 verbose pkgid [email protected]
   15 verbose cwd 
E:\lx_workspace\pythonspace\workspace5\incubator-superset-0.38.0\superset-frontend
   16 verbose Windows_NT 6.1.7601
   17 verbose argv "C:\\Program Files\\nodejs\\node.exe" 
"C:\\Users\\lx\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" 
"run" "build"
   18 verbose node v12.16.2
   19 verbose npm  v6.14.8
   20 error code ELIFECYCLE
   21 error errno 2
   22 error [email protected] build: `cross-env 
NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production webpack 
--mode=production --colors`
   22 error Exit status 2
   23 error Failed at the [email protected] build script.
   23 error This is probably not a problem with npm. There is likely additional 
logging output above.
   24 verbose exit [ 2, true ]
   
   
   
![image](https://user-images.githubusercontent.com/13344955/100408292-999ef280-30a5-11eb-9910-8089c0fba000.png)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to