rayw
December 11, 2022, 1:07am
#1
I have the following build error for my 11ty site.
I can finish the build locally within 2 minutes. Is it possible to use a more powerful machine for the build on Netlify?
4:32:29 PM: ────────────────────────────
4:32:29 PM: Netlify Build Complete
4:32:29 PM: ──────────────────────
4:32:29 PM:
4:32:29 PM: (Netlify Build completed in 23m 1.8s)
4:32:29 PM: Execution timed out after 23m16.996078939s
4:32:29 PM: Error running command: Command did not finish within the time limit
4:32:30 PM: Failing build: Failed to build site
4:32:30 PM: Finished processing build request in 23m19.896921515s
elden
December 11, 2022, 5:28am
#2
Hi @rayw
I have increased the build timeout on your site from 15 to 30 minutes. Could you give that a try and let us know how it goes?
rayw
December 12, 2022, 12:04pm
#3
Hi @elden
Thank you so much for helping me with that, now the build could finish successfully.
I want to make it quick, if I purchase the $99/month plan, can I have your priority build environment? Please let me know.
Appreciate that!
SamO
December 12, 2022, 9:13pm
#4
Hi @rayw Welcome to the forums! Yes, if you move your plan up to business you will get build prioritizations. I am attaching a link to our pricing page which highlights the key benefits of each plan. I hope this helps! (;
rayw
December 17, 2022, 7:19am
#5
Hi @elden & @SamO ,
I have updated to $99 business plan. However, I still have the build error below, is there anything wrong with my Build Prioritization environment?
Please help check.
Thanks
11:36:58 PM: <--- Last few GCs --->
11:36:58 PM: [1437:0x622bc20] 722739 ms: Mark-sweep 1934.3 (2080.3) -> 1918.8 (2079.1) MB, 334.9 / 0.0 ms (average mu = 0.300, current mu = 0.309) allocation failure scavenge might not succeed
11:36:58 PM: [1437:0x622bc20] 722774 ms: Scavenge 1935.1 (2079.6) -> 1919.9 (2079.6) MB, 3.0 / 0.0 ms (average mu = 0.300, current mu = 0.309) allocation failure
11:36:58 PM: [1437:0x622bc20] 722812 ms: Scavenge 1935.5 (2080.1) -> 1920.8 (2080.6) MB, 8.6 / 0.0 ms (average mu = 0.300, current mu = 0.309) allocation failure
11:36:58 PM: <--- JS stacktrace --->
11:36:58 PM: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
11:36:58 PM: 1: 0xb08e80 node::Abort() [node]
11:36:58 PM: 2: 0xa1b70e [node]
11:36:58 PM: 3: 0xce1890 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
11:36:58 PM: 4: 0xce1c37 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
11:36:58 PM: 5: 0xe992a5 [node]
11:36:58 PM: 6: 0xe99d86 [node]
11:36:58 PM: 7: 0xea82ae [node]
11:36:58 PM: 8: 0xea8cf0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
11:36:58 PM: 9: 0xeabc6e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
11:36:58 PM: 10: 0xe6cee2 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
11:36:58 PM: 11: 0xe654f4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [node]
11:36:58 PM: 12: 0xe67551 v8::internal::FactoryBase<v8::internal::Factory>::NewRawTwoByteString(int, v8::internal::AllocationType) [node]
11:36:58 PM: 13: 0x10334b6 [node]
11:36:58 PM: 14: 0x10355b4 v8::internal::Intl::ConvertToLower(v8::internal::Isolate*, v8::internal::Handle<v8::internal::String>) [node]
11:36:58 PM: 15: 0x11e730b v8::internal::Runtime_StringToLowerCaseIntl(int, unsigned long*, v8::internal::Isolate*) [node]
11:36:58 PM: 16: 0x15d9c19 [node]
11:36:59 PM: Aborted (core dumped)
11:36:59 PM: ERROR: "prod:eleventy" exited with 134.
11:36:59 PM:
11:36:59 PM: ────────────────────────────────────────────────────────────────
11:36:59 PM: "build.command" failed
11:36:59 PM: ────────────────────────────────────────────────────────────────
11:36:59 PM:
11:36:59 PM: Error message
11:36:59 PM: Command failed with exit code 1: npm run build_prod (https://ntl.fyi/exit-code-1)
11:36:59 PM:
Hey @rayw ,
We’ve already answered this in the helpdesk. TL;DR, try using:
NODE_OPTIONS="--max-old-space-size=4096 npm run build_prod
as your build command.