FreeBSD CI Weekly Report 2019-03-17
(bcc -current and -stable for more audience) FreeBSD CI Weekly Report 2019-03-17 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-03-11 to 2019-03-17. During this period, we have: * 1918 builds (93.2% passed, 2.3% failed, 86% exception) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 339 test runs (54.9% passed, 44.8% unstable, 0.3% exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 15 doc buils (100% passed) (For more meaningful statistics, we omitted the numbers from experimental jobs) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/s/SJc5jaHw4 and archive is available at http://hackfoldr.org/freebsd-ci-report/, any help is welcome. ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ * lib.libarchive.functional_test.test_fuzz_zip (flakey) See https://bugs.freebsd.org/236300 for more details * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * sys.netmap.ctrl-api-test.main * sys.opencrypto.runtests.main * lib.libc.regex.exhaust_test.regcomp_too_big * lib.libregex.exhaust_test.regcomp_too_big * sys.kern.coredump_phnum_test.coredump_phnum WIP: https://reviews.freebsd.org/D18495 * (New) lib.libc.sys.sendfile_test.fd_positive_shm_v4 * (New) lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * sbin.bectl.bectl_test.bectl_mount * sys.netmap.ctrl-api-test.main * sys.opencrypto.runtests.main * lib.libc.regex.exhaust_test.regcomp_too_big * lib.libregex.exhaust_test.regcomp_too_big * sys.kern.coredump_phnum_test.coredump_phnum WIP: https://reviews.freebsd.org/D18495 * https://ci.freebsd.org/job/FreeBSD-stable-11-amd64-test/ * usr.bin.procstat.procstat_test.kernel_stacks * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * sys.netmap.ctrl-api-test.main * sys.opencrypto.runtests.main * usr.bin.procstat.procstat_test.kernel_stacks * local.kyua.* (31 cases) * local.lutok.* (3 cases) * lib.libc.sys.sendfile_test.fd_positive_shm_v4 * lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 ## Failing Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * common.rates.t_dtrace_contrib.tst_switchrate_d * common.syscall.t_dtrace_contrib.tst_args_d * common.misc.t_dtrace_contrib.tst_dynopt_d * common.ip.t_dtrace_contrib.tst_ipv4localsctp_ksh * common.ip.t_dtrace_contrib.tst_localsctpstate_ksh * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~60 failing cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details ## Disabled Tests * lib.libc.sys.mmap_test.mmap_truncate_signal https://bugs.freebsd.org/211924 * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * usr.bin.procstat.procstat_test.command_line_arguments https://bugs.freebsd.org/233587 * usr.bin.procstat.procstat_test.environment https://bugs.freebsd.org/233588 ## Open Issues * Flakey test case: lib.libarchive.functional_test.test_fuzz_zip https://bugs.freebsd.org/236300 ### Cause build fails * [29: genassym.o build race](https://bugs.freebsd.org/29) * Patch available: https://people.freebsd.org/~bdrewery/patches/PR29.diff * [233735: Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory](https://bugs.freebsd.org/233735) * [233769: Possible build race: ld: error: unable to find library -lgcc_s](https://bugs.freebsd.org/233769) ### Others [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Fedora Contact List
Hi, Thank you for taking the time to read this email. I would like to know if you are interested in acquiring Fedora Contact List. We offer email lists based on your requirements. If you could send me your target audience (Industry / Geography / Job Titles), I'll come up with the data counts, costs & more information. Please let me know if interested, So that I can send you something much better for less than you are currently paying. If you do not wish to receive our email kindly reply back with exclude in the subject line. Erica turner Marketing Executive ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ifuncs check flawed?
On Mon, 18 Mar 2019 at 13:03, Dan Allen wrote: > > The buildworld and buildkernel steps both immediately fail due to the linker > not supporting ifuncs. By default FreeBSD/i386 uses lld as the bootstrap linker (i.e., the linker used for building the kernel, libraries, and userland binaries) but still installs GNU ld as /usr/bin/ld on stable/12 due to issues in the ports tree. There are a few different ways you could address this: 1. Build either the buildworld or kernel-toolchain targets before make buildkernel, which will then use the built toolchain including lld. 2. Set LD=ld.lld to explicitly use lld for the kernel link. 3. Build and install world WITH_LLD_IS_LD in src.conf, so that /usr/bin/ld is lld. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ifuncs check flawed?
> On 19 Mar 2019, at 9:34 AM, Ed Maste wrote: > > There are a few different ways you could address this: > 1. Build either the buildworld or kernel-toolchain targets before make > buildkernel, which will then use the built toolchain including lld. I did this, and it did not work. I always build the system in the canonical order: buildworld buildkernel installkernel installworld That is why I think the check is flawed! I am using the lld linker. It is present in the snapshot. The system should be using it, but it immediately fails due to the aforementioned checks. That is the bug that I am raising. Dan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
boot/pxeboot broken in freebsd-12?
Hello -stable, We have a PXE environemt that builds FreeBSD-11 boxes. We've started to dip our toes into the 12.x waters, but have had trouble getting FreeBSD-12 to pxeboot. It would crash and burn like so: Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: device not configured On a whim, I pulled the boot/pxeboot binary from our FreeBSD-11 environment into the new FreeBSD-12 environment, and PXE clients started coming right up. Is FreeBSD-12's pxeboot broken or have I missed something? -Snow ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: boot/pxeboot broken in freebsd-12?
On Tue, Mar 19, 2019 at 4:53 PM James Snow wrote: > Hello -stable, > > We have a PXE environemt that builds FreeBSD-11 boxes. We've started > to dip our toes into the 12.x waters, but have had trouble getting > FreeBSD-12 to pxeboot. It would crash and burn like so: > > Startup error in /boot/lua/loader.lua: > LUA ERROR: cannot open /boot/lua/loader.lua: device not configured > > On a whim, I pulled the boot/pxeboot binary from our FreeBSD-11 > environment into the new FreeBSD-12 environment, and PXE clients started > coming right up. > > Is FreeBSD-12's pxeboot broken or have I missed something? > You need to set the NFS mount point properly. I've been able to boot the FreeBSD 12.0R installer with PXE (after fixing some issues downstream) and had that error before I had dnsmasq answering queries properly: dhcp-vendorclass=BIOS,PXEClient:Arch:0 dhcp-userclass=FreeBSD,FreeBSD dhcp-boot=net:BIOS,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-boot=net:BIOS,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=net:BIOS,option:root-path,10.0.0.5:/tftpboot/12.0R-i386-bootonly dhcp-host=mr_noodle,set:mr_noodle dhcp-boot=tag:mr_noodle,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=tag:mr_noodle,option:root-path,10.0.0.5: /tftpboot/12.0R-i386-bootonly dhcp-boot=tag:FreeBSD,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=tag:FreeBSD,option:root-path,10.0.0.5: /tftpboot/12.0R-i386-bootonly is what I used in dnsmasq to get the job done. It was likely overkill (10.0.0.5 was the NFS, ftfpd and other servers for this exercise). I had to (a) create a blank /etc/fstab in the mdconfig mounted image and (b) create the proper /etc/resolv.conf in the F4 shell window just after I hit commit to make things work. And then configure the network by hand because the installer's config was wrong. So we've had some regression, just not the regression you are seeing. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
