Date: Mon, 15 Jul 2024 08:20:55 +0800 From: Philip Paeps <philip@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: mmel@freebsd.org, freebsd-arm@freebsd.org Subject: Re: A better alternative to having builds of main-armv7-default fully disabled and last-built be months out of date Message-ID: <016A1875-EE40-4815-964D-9762597206B7@freebsd.org> In-Reply-To: <274FAB06-4204-415D-941F-69F623E11266@yahoo.com> References: <91287D15-F0A9-4425-A265-B07418B8714D.ref@yahoo.com> <91287D15-F0A9-4425-A265-B07418B8714D@yahoo.com> <816ef6c9-836f-48bb-9f89-b46898431c87@freebsd.org> <274FAB06-4204-415D-941F-69F623E11266@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=_MailMate_7F94123E-2EFD-4CA3-BB5C-C097F28827B0_= Content-Type: text/plain; format=flowed Sorry for not following up to this thread earlier. I've been occupied elsewhere in the cluster. On 2024-07-07 16:25:32 (+0800), Mark Millard wrote: > On Jul 6, 2024, at 21:35, Michal Meloun <meloun.michal@gmail.com> > wrote: >> On 07.07.2024 5:42, Mark Millard wrote: >>> main's armv7 packages that are distributed are getting to be months >>> behind because of the build hangups preventing the builds on >>> ampere2. It's worth reinforcing that this only affects main (15-CURRENT). Our stable/13 and stable/14 packages for armv7 are reasonably up to date. Reasonably for a tier-2 architecture anyway. Whatever is causing this, it's only in main. > The only known failures are on ampere2 as far as I know. > As far as I know there is no known way to configure to > match the formal build procedures used on ampere2. According to the current schedule, armv7 builds happen on ampere3, not ampere2: ampere1: - quarterly arm64.aarch64 13.3-RELEASE 133arm64 -a ampere1: - quarterly arm.armv7 releng/13.3 133releng-armv7 -a ampere1: - quarterly arm64.aarch64 14.0-RELEASE 140arm64 -a ampere1: - quarterly arm.armv7 releng/14.0 140releng-armv7 -a ampere2: - default arm64.aarch64 main main-arm64 -a ampere3: - default arm64.aarch64 13.3-RELEASE 133arm64 -a ampere3: - default arm.armv7 releng/13.3 133releng-armv7 -a ampere3: - default arm64.aarch64 14.0-RELEASE 140arm64 -a ampere3: - default arm.armv7 releng/14.0 140releng-armv7 -a I've attached the poudriere.conf from that machine. It's the same one we have on all the builders. >> I've seen some strange live lockups in arm32 jail, but never managed >> to reproduce it. > > On what kind(s) of hardware? > Any kind of relevant context known? In case it helps: ref15-aarch64.freebsd.org (available to all developers) is an identical configuration as ampereX.nyi.freebsd.org. The former has a newer BIOS (for some reason) but that hopefully should not make a difference. If we reach the point where we think the BIOS version matters, I can try to upgrade the BIOS on the ampereXen. smbios.bios.reldate="06/25/2020" smbios.bios.revision="1.14" smbios.bios.vendor="LENOVO" smbios.bios.version="hve104q-1.14" smbios.bios.reldate="05/30/2019" smbios.bios.revision="1.8" smbios.bios.vendor="LENOVO" smbios.bios.version="HVE104J-1.08" Philip --=_MailMate_7F94123E-2EFD-4CA3-BB5C-C097F28827B0_= Content-Disposition: attachment; filename=poudriere.conf Content-Type: text/plain; name=poudriere.conf Content-Transfer-Encoding: quoted-printable # !!!! DO NOT EDIT THIS FILE, IT IS TRACKED IN SVN (https://pm-svn.freebs= d.org/cluster) !!!! # vim: set filetype=3Dsh: ZPOOL=3Dzroot ZROOTFS=3D/poudriere RESOLV_CONF=3D/etc/resolv.conf BASEFS=3D/usr/local/poudriere USE_PORTLINT=3Dno USE_TMPFS=3Dall DISTFILES_CACHE=3D/usr/ports/distfiles SVN_HOST=3Dsvn0.us-east.FreeBSD.org GIT_BASEURL=3Dgit.freebsd.org/src.git GIT_PORTSURL=3Dgit.freebsd.org/ports.git CHECK_CHANGED_OPTIONS=3Dyes CHECK_CHANGED_DEPS=3Dyes NO_RESTRICTED=3Dyes NO_FORCE_PACKAGE=3Dyes URL_BASE=3D"https://pkg-status.freebsd.org/$(hostname -s)" #MAX_MEMORY=3D8 ATOMIC_PACKAGE_REPOSITORY=3Dno PKG_REPO_FROM_HOST=3Dyes SIGNING_COMMAND=3D"ssh pkg-sign" PRIORITY_BOOST=3D"iridium-browser ungoogled-chromium" PRIORITY_BOOST_VALUE=3D20 ALLOW_MAKE_JOBS_PACKAGES=3D"pkg chromium electron29 iridium-browser llvm-= devel qt5-webengine qt6-webengine ungoogled-chromium" TMPFS_BLACKLIST=3D"chromium electron29 iridium-browser ungoogled-chromium= " TMPFS_BLACKLIST_TMPDIR=3D${BASEFS}/data/wrkdirs HTML_JSON_UPDATE_INTERVAL=3D10 USE_PTSORT=3Dno DETERMINE_BUILD_FAILURE_REASON=3Dno # 48 hours for chromium based browsers MAX_EXECUTION_TIME=3D172800 # 2 hours for chromium based browsers = MAX_EXECUTION_TIME_EXTRACT=3D7200 MAX_FILES_RStudio=3D4096 MAX_FILES_RStudio_server=3D4096 MAX_FILES_atom_ide=3D4096 MAX_FILES_traefik=3D2048 MAX_FILES_gatk=3D2048 MAX_FILES_screego=3D8192 MAX_FILES_vscode=3D8192 BUILD_AS_NON_ROOT=3Dno # Use jail src for native-xtools builds XDEV_SRC_JAIL=3Dyes #CCACHE_DIR=3D/ccache calc_builders() { local GB_PER_BUILDER ncpu arcsize physmem swap vmem emem GB_PER_BUILDER=3D12 ncpu=3D$(/sbin/sysctl -n hw.ncpu) PREPARE_PARALLEL_JOBS=3D$((ncpu + 5)) # Tune BUILD_PARALLEL_JOBS based on amount of VM. physmem=3D$(($(/sbin/sysctl -n hw.physmem) / 1024 / 1024 / 1024)) arcsize=3D$(($(/sbin/sysctl -n vfs.zfs.arc_max) / 1024 / 1024 / 1024)) swap=3D$(($(/sbin/sysctl -n vm.swap_total) / 1024 / 1024 / 1024)) vmem=3D$((physmem + swap)) # Calculate "effective" memory; Ignore greedy ARC. emem=3D$((vmem - arcsize)) if [ ${emem} -lt 0 ]; then # The ARC is probably too big. emem=3D$((emem + arcsize)) fi # Give each builder GB_PER_BUILDER BUILD_PARALLEL_JOBS=3D$((emem / GB_PER_BUILDER)) if [ ${BUILD_PARALLEL_JOBS} -gt ${ncpu} ]; then BUILD_PARALLEL_JOBS=3D${ncpu} elif [ ${ncpu} -ge $((2 * BUILD_PARALLEL_JOBS)) ]; then ALLOW_MAKE_JOBS=3Dyes fi if [ $# -gt 0 ]; then echo "calc_builders(): ncpu=3D${ncpu} physmem=3D${physmem} arcsize=3D${= arcsize} JOBS=3D${BUILD_PARALLEL_JOBS}" >&2 fi } calc_builders "$@" #case "$(hostname -s)" in # foul2) # BUILD_PARALLEL_JOBS=3D20 # ;; #esac --=_MailMate_7F94123E-2EFD-4CA3-BB5C-C097F28827B0_=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?016A1875-EE40-4815-964D-9762597206B7>