Details
-
Bug
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
None
-
DevOps Sprint 129, DevOps Sprint 130, DevOps Sprint 131
-
FOLIO DevOps
Description
The Vagrant box builds have been failing for the last couple of days with the error:
testing: fatal: [default]: FAILED! => {"changed": true, "cmd": "yarn build output --okapi http://localhost:9130 --tenant diku --sourcemap", "delta": "0:09:41.779621", "end": "2021-12-17 06:14:38.860984", "msg": "non-zero return code", "rc": 134, "start": "2021-12-17 06:04:57.081363", "stderr": "\n<--- Last few GCs --->\n\n[46020:0x4f169d0] 565255 ms: Mark-sweep 3988.3 (4120.6) -> 3972.9 (4120.4) MB, 7693.4 / 0.0 ms (average mu = 0.107, current mu = 0.010) allocation failure scavenge might not succeed\n[46020:0x4f169d0] 573304 ms: Mark-sweep 3989.6 (4121.1) -> 3974.1 (4121.6) MB, 7923.7 / 0.0 ms (average mu = 0.062, current mu = 0.016) allocation failure scavenge might not succeed\n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory\n 1: 0xa389b0 node::Abort() [stripes-cli]\n 2: 0x96e0af node::FatalError(char const*, char const*) [stripes-cli]\n 3: 0xbb7a4e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [stripes-cli]\n 4: 0xbb7dc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [stripes-cli]\n 5: 0xd73fd5 [stripes-cli]\n 6: 0xd74b5f [stripes-cli]\n 7: 0xd8299b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [stripes-cli]\n 8: 0xd8655c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [stripes-cli]\n 9: 0xd54c3b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [stripes-cli]\n10: 0x109d21f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [stripes-cli]\n11: 0x1446379 [stripes-cli]\nAborted (core dumped)\nerror Command failed with exit code 134.", "stderr_lines": ["", "<--- Last few GCs --->", "", "[46020:0x4f169d0] 565255 ms: Mark-sweep 3988.3 (4120.6) -> 3972.9 (4120.4) MB, 7693.4 / 0.0 ms (average mu = 0.107, current mu = 0.010) allocation failure scavenge might not succeed", "[46020:0x4f169d0] 573304 ms: Mark-sweep 3989.6 (4121.1) -> 3974.1 (4121.6) MB, 7923.7 / 0.0 ms (average mu = 0.062, current mu = 0.016) allocation failure scavenge might not succeed", "", "", "<--- JS stacktrace --->", "", "FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory", " 1: 0xa389b0 node::Abort() [stripes-cli]", " 2: 0x96e0af node::FatalError(char const*, char const*) [stripes-cli]", " 3: 0xbb7a4e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [stripes-cli]", " 4: 0xbb7dc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [stripes-cli]", " 5: 0xd73fd5 [stripes-cli]", " 6: 0xd74b5f [stripes-cli]", " 7: 0xd8299b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [stripes-cli]", " 8: 0xd8655c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [stripes-cli]", " 9: 0xd54c3b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [stripes-cli]", "10: 0x109d21f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [stripes-cli]", "11: 0x1446379 [stripes-cli]", "Aborted (core dumped)", "error Command failed with exit code 134."], "stdout": "yarn run v1.22.17\n$ export NODE_OPTIONS=\"--max-old-space-size=4096 $NODE_OPTIONS\"; stripes build stripes.config.js output --okapi http://localhost:9130 --tenant diku --sourcemap\nBuilding...\ninfo Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.", "stdout_lines": ["yarn run v1.22.17", "$ export NODE_OPTIONS=\"--max-old-space-size=4096 $NODE_OPTIONS\"; stripes build stripes.config.js output --okapi http://localhost:9130 --tenant diku --sourcemap", "Building...", "info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command."]}
...which suggests a memory issue (i.e. --max-old-space-size should be higher).
But, this only appears to affect the packer builds. It does not happen when building EC2 system, nor when building a Vagrant box directly using Vagrant.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODDATAIMP-611 Verify the Authority Update workflow
-
- Closed
-
-
MODNOTES-189 Verify mod-notes according to spring way
-
- Closed
-