Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2018-11-16T16:33:55.5519983Z ##[section]Starting: npm run
- 2018-11-16T16:33:55.5523941Z ==============================================================================
- 2018-11-16T16:33:55.5524097Z Task : npm
- 2018-11-16T16:33:55.5524198Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Package Management.
- 2018-11-16T16:33:55.5524340Z Version : 1.0.30
- 2018-11-16T16:33:55.5524436Z Author : Microsoft Corporation
- 2018-11-16T16:33:55.5524516Z Help : [More Information](https://go.microsoft.com/fwlink/?LinkID=613746)
- 2018-11-16T16:33:55.5524639Z ==============================================================================
- 2018-11-16T16:33:55.8335164Z SYSTEMVSSCONNECTION exists true
- 2018-11-16T16:33:55.9637015Z SYSTEMVSSCONNECTION exists true
- 2018-11-16T16:33:56.0570922Z [command]/usr/local/bin/npm --version
- 2018-11-16T16:33:56.2369945Z 6.4.1
- 2018-11-16T16:33:58.0363898Z [command]/usr/local/bin/npm config list
- 2018-11-16T16:33:58.0364051Z ; cli configs
- 2018-11-16T16:33:58.0364386Z metrics-registry = "https://registry.npmjs.org/"
- 2018-11-16T16:33:58.0364466Z scope = ""
- 2018-11-16T16:33:58.0365116Z user-agent = "npm/6.4.1 node/v8.12.0 linux x64"
- 2018-11-16T16:33:58.0365168Z
- 2018-11-16T16:33:58.0365252Z ; environment configs
- 2018-11-16T16:33:58.0365323Z userconfig = "/home/vsts/work/1/npm/416.npmrc"
- 2018-11-16T16:33:58.0365386Z
- 2018-11-16T16:33:58.0365454Z ; node bin location = /usr/local/bin/node
- 2018-11-16T16:33:58.0365545Z ; cwd = /home/vsts/work/1/s/Web/TMC.Cloud.Web.Frontend
- 2018-11-16T16:33:58.0365622Z ; HOME = /home/vsts
- 2018-11-16T16:33:58.0365894Z ; "npm config ls -l" to show all defaults.
- 2018-11-16T16:33:58.0365945Z
- 2018-11-16T16:33:58.0366248Z [command]/usr/local/bin/npm run build:prod
- 2018-11-16T16:37:23.3649694Z
- 2018-11-16T16:37:23.3652522Z FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
- 2018-11-16T16:37:23.3652943Z > tms-admin@2.0.2 build:prod /home/vsts/work/1/s/Web/TMC.Cloud.Web.Frontend
- 2018-11-16T16:37:23.3654146Z 1: node::Abort() [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3654413Z > npm run build -- --prod --aot=false --build-optimizer=false
- 2018-11-16T16:37:23.3655582Z 2: 0x8cbf4c [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3655666Z
- 2018-11-16T16:37:23.3656534Z 3: v8::Utils::ReportOOMFailure(char const*, bool) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3656628Z
- 2018-11-16T16:37:23.3657512Z 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3657816Z > tms-admin@2.0.2 build /home/vsts/work/1/s/Web/TMC.Cloud.Web.Frontend
- 2018-11-16T16:37:23.3659016Z 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3659285Z > ng build "--prod" "--aot=false" "--build-optimizer=false"
- 2018-11-16T16:37:23.3660991Z 6: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::NewInternal(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3661152Z
- 2018-11-16T16:37:23.3662320Z 7: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::New(v8::internal::Isolate*, int, v8::internal::PretenureFlag, v8::internal::MinimumCapacity) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3662464Z
- 2018-11-16T16:37:23.3663732Z 8: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::EnsureCapacity(v8::internal::Handle<v8::internal::StringTable>, int, v8::internal::PretenureFlag) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3664021Z <--- Last few GCs --->
- 2018-11-16T16:37:23.3665252Z 9: v8::internal::StringTable::LookupString(v8::internal::Isolate*, v8::internal::Handle<v8::internal::String>) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3665509Z
- 2018-11-16T16:37:23.3666478Z 10: v8::internal::Runtime_HasProperty(int, v8::internal::Object**, v8::internal::Isolate*) [ng build --prod --aot=false --build-optimizer=false]
- 2018-11-16T16:37:23.3666848Z [3672:0x296d110] 200688 ms: Mark-sweep 1284.8 (1432.7) -> 1284.8 (1432.7) MB, 1816.5 / 0.0 ms allocation failure GC in old space requested
- 2018-11-16T16:37:23.3667491Z 11: 0x2bd8b8a042fd
- 2018-11-16T16:37:23.3667889Z [3672:0x296d110] 202756 ms: Mark-sweep 1284.8 (1432.7) -> 1284.8 (1424.2) MB, 2067.4 / 0.0 ms last resort GC in old space requested
- 2018-11-16T16:37:23.3668505Z Aborted (core dumped)
- 2018-11-16T16:37:23.3668897Z [3672:0x296d110] 204300 ms: Mark-sweep 1284.8 (1424.2) -> 1284.8 (1424.2) MB, 1544.6 / 0.0 ms last resort GC in old space requested
- 2018-11-16T16:37:23.3670221Z npm ERR! code ELIFECYCLE
- 2018-11-16T16:37:23.3670297Z
- 2018-11-16T16:37:23.3670965Z npm ERR! errno 134
- 2018-11-16T16:37:23.3671016Z
- 2018-11-16T16:37:23.3671978Z npm ERR! tms-admin@2.0.2 build: `ng build "--prod" "--aot=false" "--build-optimizer=false"`
- 2018-11-16T16:37:23.3672260Z <--- JS stacktrace --->
- 2018-11-16T16:37:23.3673126Z npm ERR! Exit status 134
- 2018-11-16T16:37:23.3673177Z
- 2018-11-16T16:37:23.3673906Z npm ERR!
- 2018-11-16T16:37:23.3673978Z ==== JS stack trace =========================================
- 2018-11-16T16:37:23.3674738Z npm ERR! Failed at the tms-admin@2.0.2 build script.
- 2018-11-16T16:37:23.3674794Z
- 2018-11-16T16:37:23.3675587Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
- 2018-11-16T16:37:23.3675693Z Security context: 0x2eefd8f25879 <JSObject>
- 2018-11-16T16:37:23.3676195Z
- 2018-11-16T16:37:23.3676313Z 2: has [0xbc82d2822d1 <undefined>:294] [bytecode=0x17f9fcb6bed9 offset=16](this=0x29f60232601 <Dictionary map = 0x18735867cdd9>,key=4685)
- 2018-11-16T16:37:23.3676888Z npm ERR! A complete log of this run can be found in:
- 2018-11-16T16:37:23.3677024Z 3: add [0xbc82d2822d1 <undefined>:279] [bytecode=0xa42bfb42eb9 offset=7](this=0x29f60232601 <Dictionary map = 0x18735867cdd9>,key=4685,val=0x2147686cea91 <AST_VarDef map = 0x187358671ac1>)
- 2018-11-16T16:37:23.3678020Z npm ERR! /home/vsts/.npm/_logs/2018-11-16T16_37_22_766Z-debug.log
- 2018-11-16T16:37:23.3678110Z 4: /* anonymous */(aka /* anonymous */) [0xbc82d2822d1 <und...
- 2018-11-16T16:37:23.3678718Z npm ERR! code ELIFECYCLE
- 2018-11-16T16:37:23.3678763Z
- 2018-11-16T16:37:23.3679372Z npm ERR! errno 134
- 2018-11-16T16:37:23.3681007Z npm ERR! tms-admin@2.0.2 build:prod: `npm run build -- --prod --aot=false --build-optimizer=false`
- 2018-11-16T16:37:23.3682005Z npm ERR! Exit status 134
- 2018-11-16T16:37:23.3682989Z npm ERR!
- 2018-11-16T16:37:23.3685193Z npm ERR! Failed at the tms-admin@2.0.2 build:prod script.
- 2018-11-16T16:37:23.3776553Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
- 2018-11-16T16:37:23.3777946Z
- 2018-11-16T16:37:23.3778710Z npm ERR! A complete log of this run can be found in:
- 2018-11-16T16:37:23.3780341Z npm ERR! /home/vsts/.npm/_logs/2018-11-16T16_37_23_292Z-debug.log
- 2018-11-16T16:37:25.1119836Z Found npm debug log, make sure the path matches with the one in npm's output: /home/vsts/.npm/_logs/2018-11-16T16_37_23_292Z-debug.log
- 2018-11-16T16:37:25.1120218Z 0 info it worked if it ends with ok
- 2018-11-16T16:37:25.1120530Z 1 verbose cli [ '/usr/local/bin/node',
- 2018-11-16T16:37:25.1120815Z 1 verbose cli '/usr/local/bin/npm',
- 2018-11-16T16:37:25.1121076Z 1 verbose cli 'run',
- 2018-11-16T16:37:25.1121338Z 1 verbose cli 'build:prod' ]
- 2018-11-16T16:37:25.1121420Z 2 info using npm@6.4.1
- 2018-11-16T16:37:25.1121512Z 3 info using node@v8.12.0
- 2018-11-16T16:37:25.1121816Z 4 verbose run-script [ 'prebuild:prod', 'build:prod', 'postbuild:prod' ]
- 2018-11-16T16:37:25.1122116Z 5 info lifecycle tms-admin@2.0.2~prebuild:prod: tms-admin@2.0.2
- 2018-11-16T16:37:25.1122739Z 6 info lifecycle tms-admin@2.0.2~build:prod: tms-admin@2.0.2
- 2018-11-16T16:37:25.1123051Z 7 verbose lifecycle tms-admin@2.0.2~build:prod: unsafe-perm in lifecycle true
- 2018-11-16T16:37:25.1123882Z 8 verbose lifecycle tms-admin@2.0.2~build:prod: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/vsts/work/1/s/Web/TMC.Cloud.Web.Frontend/node_modules/.bin:"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
- 2018-11-16T16:37:25.1124260Z 9 verbose lifecycle tms-admin@2.0.2~build:prod: CWD: /home/vsts/work/1/s/Web/TMC.Cloud.Web.Frontend
- 2018-11-16T16:37:25.1124536Z 10 silly lifecycle tms-admin@2.0.2~build:prod: Args: [ '-c',
- 2018-11-16T16:37:25.1124800Z 10 silly lifecycle 'npm run build -- --prod --aot=false --build-optimizer=false' ]
- 2018-11-16T16:37:25.1125088Z 11 silly lifecycle tms-admin@2.0.2~build:prod: Returned: code: 134 signal: null
- 2018-11-16T16:37:25.1125350Z 12 info lifecycle tms-admin@2.0.2~build:prod: Failed to exec build:prod script
- 2018-11-16T16:37:25.1125680Z 13 verbose stack Error: tms-admin@2.0.2 build:prod: `npm run build -- --prod --aot=false --build-optimizer=false`
- 2018-11-16T16:37:25.1125802Z 13 verbose stack Exit status 134
- 2018-11-16T16:37:25.1126105Z 13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
- 2018-11-16T16:37:25.1126226Z 13 verbose stack at emitTwo (events.js:126:13)
- 2018-11-16T16:37:25.1126302Z 13 verbose stack at EventEmitter.emit (events.js:214:7)
- 2018-11-16T16:37:25.1126636Z 13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
- 2018-11-16T16:37:25.1126752Z 13 verbose stack at emitTwo (events.js:126:13)
- 2018-11-16T16:37:25.1126829Z 13 verbose stack at ChildProcess.emit (events.js:214:7)
- 2018-11-16T16:37:25.1126929Z 13 verbose stack at maybeClose (internal/child_process.js:915:16)
- 2018-11-16T16:37:25.1127046Z 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
- 2018-11-16T16:37:25.1127275Z 14 verbose pkgid tms-admin@2.0.2
- 2018-11-16T16:37:25.1127377Z 15 verbose cwd /home/vsts/work/1/s/Web/TMC.Cloud.Web.Frontend
- 2018-11-16T16:37:25.1127594Z 16 verbose Linux 4.15.0-1023-azure
- 2018-11-16T16:37:25.1127694Z 17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build:prod"
- 2018-11-16T16:37:25.1127794Z 18 verbose node v8.12.0
- 2018-11-16T16:37:25.1127861Z 19 verbose npm v6.4.1
- 2018-11-16T16:37:25.1127945Z 20 error code ELIFECYCLE
- 2018-11-16T16:37:25.1128013Z 21 error errno 134
- 2018-11-16T16:37:25.1128320Z 22 error tms-admin@2.0.2 build:prod: `npm run build -- --prod --aot=false --build-optimizer=false`
- 2018-11-16T16:37:25.1128429Z 22 error Exit status 134
- 2018-11-16T16:37:25.1128678Z 23 error Failed at the tms-admin@2.0.2 build:prod script.
- 2018-11-16T16:37:25.1128792Z 23 error This is probably not a problem with npm. There is likely additional logging output above.
- 2018-11-16T16:37:25.1128888Z 24 verbose exit [ 134, true ]
- 2018-11-16T16:37:25.1128947Z
- 2018-11-16T16:37:25.1187216Z ##[error]Error: Npm failed with return code: 134
- 2018-11-16T16:37:25.1211365Z ##[section]Finishing: npm run
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement