Official stable/14 builds of armv6 have been broken for over a month ( Tier 3 for stable/14 )
The build just after the last successful one for stable/14 armv6 looks to be: https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/ #1008 (Mon Sep 09 21:44:50 GMT 2024) 755e773877e9f3abab3bed2d46d9d87978e303d9 https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/console 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: zfs_sha256_block_armv7 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so 15:32:05 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: zfs_sha512_block_armv7 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so But builds from today show the same type of error: https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/ #1206 (Sun Oct 20 15:18:03 GMT 2024) edbeda6b759459a9c2c5e8e12b18294d41959270 https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/console 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: zfs_sha256_block_armv7 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so 08:53:28 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: zfs_sha512_block_armv7 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so So around 1.3 months without a successful build. It would seem one of the following would be better than wasting machine resources on failing, long-running qemu based builds . . . ) stop trying to have stable/14 armv6 builds or: ) get the stable/14 armv6 builds working again Note: I do not use armv6 builds. I just happened to notice this when I was looking at https://ci.freebsd.org/tinderbox/ for other reasons. === Mark Millard marklmi at yahoo.com
Re: Official stable/14 builds of armv6 have been broken for over a month ( Tier 3 for stable/14 )
On Oct 20, 2024, at 10:41, Mark Millard wrote: > The build just after the last successful one for stable/14 armv6 looks to be: > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/ > > #1008 (Mon Sep 09 21:44:50 GMT 2024) > 755e773877e9f3abab3bed2d46d9d87978e303d9 > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/console > > 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha256_block_armv7 > 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > 15:32:05 > 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha512_block_armv7 > 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > > > But builds from today show the same type of error: > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/ > > #1206 (Sun Oct 20 15:18:03 GMT 2024) > edbeda6b759459a9c2c5e8e12b18294d41959270 > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/console > > 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha256_block_armv7 > 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > 08:53:28 > 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha512_block_armv7 > 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > > > So around 1.3 months without a successful build. It would seem > one of the following would be better than wasting machine > resources on failing, long-running qemu based builds . . . Ignore my mistaken reference to qemu being involved. It still took around 9hrs in one case or 15.5 hrs in the other case for the above 2 examples to fail. How many build attempts were there over the 10.3 months or so? > ) stop trying to have stable/14 armv6 builds > or: > ) get the stable/14 armv6 builds working again > > > Note: I do not use armv6 builds. I just happened to notice this > when I was looking at https://ci.freebsd.org/tinderbox/ for > other reasons. === Mark Millard marklmi at yahoo.com
Re: Official stable/14 builds of armv6 have been broken for over a month ( Tier 3 for stable/14 )
[Looks like it is not going to be a great day . . .] On Oct 20, 2024, at 11:20, Mark Millard wrote: > On Oct 20, 2024, at 10:41, Mark Millard wrote: > >> The build just after the last successful one for stable/14 armv6 looks to be: >> >> >> https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/ >> >> #1008 (Mon Sep 09 21:44:50 GMT 2024) >> 755e773877e9f3abab3bed2d46d9d87978e303d9 >> >> >> https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/console >> >> 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: >> zfs_sha256_block_armv7 >> 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so >> 15:32:05 >> 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: >> zfs_sha512_block_armv7 >> 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so >> >> >> But builds from today show the same type of error: >> >> >> https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/ >> >> #1206 (Sun Oct 20 15:18:03 GMT 2024) >> edbeda6b759459a9c2c5e8e12b18294d41959270 >> >> >> https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/console >> >> 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: >> zfs_sha256_block_armv7 >> 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so >> 08:53:28 >> 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: >> zfs_sha512_block_armv7 >> 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so >> >> >> So around 1.3 months without a successful build. It would seem >> one of the following would be better than wasting machine >> resources on failing, long-running qemu based builds . . . > > Ignore my mistaken reference to qemu being involved. It > still took around 9hrs in one case or 15.5 hrs in the > other case for the above 2 examples to fail. How many > build attempts were there over the 10.3 months or so? 1.3 months, of course, not 10.3 months. >> ) stop trying to have stable/14 armv6 builds >> or: >> ) get the stable/14 armv6 builds working again >> >> >> Note: I do not use armv6 builds. I just happened to notice this >> when I was looking at https://ci.freebsd.org/tinderbox/ for >> other reasons. === Mark Millard marklmi at yahoo.com
Re: Official stable/14 builds of armv6 have been broken for over a month ( Tier 3 for stable/14 )
On Sun, Oct 20, 2024 at 10:41:54AM -0700, Mark Millard wrote: > The build just after the last successful one for stable/14 armv6 looks to be: > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/ > > #1008 (Mon Sep 09 21:44:50 GMT 2024) > 755e773877e9f3abab3bed2d46d9d87978e303d9 > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1008/console > > 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha256_block_armv7 > 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > 15:32:05 > 15:32:05 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha512_block_armv7 > 15:32:05 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > > > But builds from today show the same type of error: > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/ > > #1206 (Sun Oct 20 15:18:03 GMT 2024) > edbeda6b759459a9c2c5e8e12b18294d41959270 > > > https://ci.freebsd.org/job/FreeBSD-stable-14-armv6-build/1206/console > > 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha256_block_armv7 > 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > 08:53:28 > 08:53:28 ld: error: undefined reference due to --no-allow-shlib-undefined: > zfs_sha512_block_armv7 > 08:53:28 >>> referenced by /usr/obj/usr/src/arm.armv6/tmp/usr/lib/libicp.so > > > So around 1.3 months without a successful build. It would seem > one of the following would be better than wasting machine > resources on failing, long-running qemu based builds . . . > > ) stop trying to have stable/14 armv6 builds > or: > ) get the stable/14 armv6 builds working again > > > Note: I do not use armv6 builds. I just happened to notice this > when I was looking at https://ci.freebsd.org/tinderbox/ for > other reasons. I've pushed some missing cherry-picks which fix the build failures for me. Thanks for reporting this.
