On 2021 Mar 02 (Tue) at 10:33:45 -0500 (-0500), Kurt Miller wrote:
:On Mon, 2021-03-01 at 16:06 -0700, [email protected] wrote:
:> bulk build on arm64.ports.openbsd.org
:> started on Fri Feb 26 03:16:18 MST 2021
:> finished at Mon Mar 1 16:06:12 MST 2021
:> lasted 3D12h49m
:> done with kern.version=OpenBSD 6.9-beta (GENERIC.MP) #1041: Fri Feb 26
02:14:59 MST 2021
:>
:> built packages:11001
:> Feb 26:3589
:> Feb 27:844
:> Feb 28:1368
:> Mar 1:5199
:>
:>
:> critical path missing pkgs:
http://build-failures.rhaalovely.net/aarch64/2021-02-26/summary.log
:>
:> build failures: 50
:> http://build-failures.rhaalovely.net/aarch64/2021-02-26/www/chromium.log
:
:This failed due to lack of memory. Seems like its time to bump
:datasize-cur on aarch64 again. My systems max out at 4g so I cant
:probe the needed value. Perhaps it should just match amd64's value
:8192M now.
:
:python ../../v8/tools/run.py ./mksnapshot --turbo_instruction_scheduling
--target_os=openbsd --target_arch=arm64 --
:embedded_src gen/v8/embedded.S --embedded_variant Default --random-seed
314159265 --startup_blob snapshot_blob.bin --no-
:native-code-counters
:
:
:#
:# Fatal error in , line 0
:# Fatal process out of memory: Failed to reserve memory for new V8 Isolate
:#
:#
:#
:#FailureMessage Object: 0x7ffffa5a20
:==== C stack trace ===============================
I've bumped the pbuild class in login.conf already. The machines have
128G of RAM.
pbuild:\
:datasize-max=infinity:\
:datasize-cur=16G:\
:stacksize-cur=8M:\
:maxproc=2048:\
:priority=5:\
:tc=default:
--
Oh, well, I guess this is just going to be one of those lifetimes.
