Re: RELENG_10 to RELENG11 buildworld no possible ?
Hi all, > Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > Or maybe via 11.2R, if that can be built from RELENG_10? I just completed a successful build of RELENG_11_2 on a RELENG_10_4 system … Kind regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling ___ 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: RELENG_10 to RELENG11 buildworld no possible ?
On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > Hi all, > >> Am 08.07.2019 um 08:30 schrieb Thomas Mueller : >> Or maybe via 11.2R, if that can be built from RELENG_10? > I just completed a successful build of RELENG_11_2 on a > RELENG_10_4 system … > > Kind regards, > Patrick I am guessing all is good up until https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html If I svn update -r346291(commit before the import of the new clang) all builds fine. Not sure if its worth a note in UPDATING, or mentioning it here in the google archives will be good enough for anyone else who runs into it. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ 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: RELENG_10 to RELENG11 buildworld no possible ?
On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > > Hi all, > > > >> Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > >> Or maybe via 11.2R, if that can be built from RELENG_10? > > I just completed a successful build of RELENG_11_2 on a > > RELENG_10_4 system … > > > > Kind regards, > > Patrick > > I am guessing all is good up until > > > https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > > If I svn update -r346291(commit before the import of the new clang) all > builds fine. > > Not sure if its worth a note in UPDATING, or mentioning it here in the > google archives will be good enough for anyone else who runs into it. > I think it is worth a note. I'll add one. We should also followup with dim@ to see why static_assert from RELENG_10 is incompatible with the new compiler, and why it's used in a way that would break. 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"
FreeBSD CI Weekly Report 2019-06-30
(Please send the followup discussions to freebsd-testing@ list.) FreeBSD CI Weekly Report 2019-06-30 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-06-24 to 2019-06-30. During this period, we have: * 1764 builds (95.9% passed, 4.1% failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 333 test runs (57.1% passed, 33.6% unstable, 9.3% exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 44 doc builds (100% passed) (The statistics from experimental jobs are omitted) 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/BkT334Wer and archive is available at http://hackfoldr.org/freebsd-ci-report/, any help is welcome. ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * Analysis from kp@: * https://lists.freebsd.org/pipermail/freebsd-testing/2019-June/001933.html * https://lists.freebsd.org/pipermail/freebsd-testing/2019-June/001934.html * sys.opencrypto.runtests.main * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * Same as -head: * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * sys.opencrypto.runtests.main Failed with: ``` File "/usr/tests/sys/opencrypto/cryptodev.py", line 179, in __init__ ioctl(_cryptodev, CIOCGSESSION2, s, 1) IOError: [Errno 22] Invalid argument ``` * lib.libregex.exhaust_test.regcomp_too_big * flaky, sometimes failed with: ``` /usr/src/contrib/netbsd-tests/lib/libc/regex/t_exhaust.c:72: p != NULL not met ``` * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * local.kyua.* (31 cases) * local.lutok.* (3 cases) ## Failing and Flaky Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d https://bugs.freebsd.org/237641 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * This job is currently suffering from timeout because of https://bugs.freebsd.org/237652 * 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_loogle.com/ine_arguments https://bugs.freebsd.org/233587 * usr.bin.procstat.procstat_test.environment https://bugs.freebsd.org/233588 * sys.netinet.socket_afinet.socket_afinet_bind_zero (new) https://bugs.freebsd.org/238781 ## Issues ### New * https://bugs.freebsd.org/238828 Possible build race: lib/libsysdecode/tables.h:948: error: 'IPV6_MIN_MEMBERSHIPS' undeclared * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic ### Cause build fails * https://bugs.freebsd.org/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/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Open * https://bugs.freebsd.org/237077 possible race in build: /usr/src/sys/amd64/linux/linux_support.s:38:2: error: expected relocatable expression * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237652 tests.hotspare.hotspare_test.hotspare_snapshot_001_pos timeout since somewhere in (r346814, r 346845] * https://bugs.freebsd.org/237655 Non-deterministic panic when running pf tests in interface ioctl code (NULL passed to strncmp) * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/237657 sys.kern.pdeathsig.signal_delivered_ptrace timing out periodically on i386 * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded ### Others * [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) * https://issues.tmatesoft.com/issue
FreeBSD CI Weekly Report 2019-07-07
(Please send the followup discussions to freebsd-testing@ list.) FreeBSD CI Weekly Report 2019-07-07 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-07-01 to 2019-07-07. During this period, we have: * 1871 builds (96.2% passed, 3.8% failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 335 test runs (47.5% passed, 45.3% unstable, 7.2% exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 34 doc builds (100% passed) (The statistics from experimental jobs are omitted) 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/BJmFeVxbB and archive is available at http://hackfoldr.org/freebsd-ci-report/, any help is welcome. ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * Analysis from kp@: * https://lists.freebsd.org/pipermail/freebsd-testing/2019-June/001933.html * https://lists.freebsd.org/pipermail/freebsd-testing/2019-June/001934.html * sys.opencrypto.runtests.main * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * Same as -head: * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * sys.opencrypto.runtests.main Failed with: ``` File "/usr/tests/sys/opencrypto/cryptodev.py", line 179, in __init__ ioctl(_cryptodev, CIOCGSESSION2, s, 1) IOError: [Errno 22] Invalid argument ``` * lib.libregex.exhaust_test.regcomp_too_big * flaky, sometimes failed with: ``` /usr/src/contrib/netbsd-tests/lib/libc/regex/t_exhaust.c:72: p != NULL not met ``` * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * local.kyua.* (31 cases) * local.lutok.* (3 cases) ## Failing and Flaky Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d https://bugs.freebsd.org/237641 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * This job is currently suffering from timeout because of https://bugs.freebsd.org/237652 * 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_loogle.com/ine_arguments https://bugs.freebsd.org/233587 * usr.bin.procstat.procstat_test.environment https://bugs.freebsd.org/233588 * sys.netinet.socket_afinet.socket_afinet_bind_zero (new) https://bugs.freebsd.org/238781 ## Issues ### Cause build fails * https://bugs.freebsd.org/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/233769 Possible build race: ld: error: unable to find library -lgcc_s * https://bugs.freebsd.org/238828 Possible build race: lib/libsysdecode/tables.h:948: error: 'IPV6_MIN_MEMBERSHIPS' undeclared ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open * https://bugs.freebsd.org/237077 possible race in build: /usr/src/sys/amd64/linux/linux_support.s:38:2: error: expected relocatable expression * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237652 tests.hotspare.hotspare_test.hotspare_snapshot_001_pos timeout since somewhere in (r346814, r 346845] * https://bugs.freebsd.org/237655 Non-deterministic panic when running pf tests in interface ioctl code (NULL passed to strncmp) * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/237657 sys.kern.pdeathsig.signal_delivered_ptrace timing out periodically on i386 * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded ### Othe
Re: RELENG_10 to RELENG11 buildworld no possible ?
On 8 Jul 2019, at 17:38, Warner Losh wrote: > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: >>> Hi all, >>> Am 08.07.2019 um 08:30 schrieb Thomas Mueller : Or maybe via 11.2R, if that can be built from RELENG_10? >>> I just completed a successful build of RELENG_11_2 on a >>> RELENG_10_4 system … >>> >>> Kind regards, >>> Patrick >> >> I am guessing all is good up until >> >> >> https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html >> >> If I svn update -r346291(commit before the import of the new clang) all >> builds fine. >> >> Not sure if its worth a note in UPDATING, or mentioning it here in the >> google archives will be good enough for anyone else who runs into it. >> > > I think it is worth a note. I'll add one. > > We should also followup with dim@ to see why static_assert from RELENG_10 > is incompatible with the new compiler, and why it's used in a way that > would break. I took a quick look, but I don't think there is any quick solution. For some reason, clang 3.4.1 (which shipped with 10.4) cannot handle the static_asserts which are inside the piece of code in question. Also, there are several other compilation errors, due to it being unable or unwilling to cast pointers. Upstream LLVM has recently bumped the requirements for building quite aggressively, it could very well be that a higher version of clang or gcc is now required to build 8.0, precisely because of the above. At some point they apparently wanted to drop the workarounds for old compilers. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: RELENG_10 to RELENG11 buildworld no possible ?
On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote: > On 8 Jul 2019, at 17:38, Warner Losh wrote: > > > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > >>> Hi all, > >>> > Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > Or maybe via 11.2R, if that can be built from RELENG_10? > >>> I just completed a successful build of RELENG_11_2 on a > >>> RELENG_10_4 system … > >>> > >>> Kind regards, > >>> Patrick > >> > >> I am guessing all is good up until > >> > >> > >> > https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > >> > >> If I svn update -r346291(commit before the import of the new clang) all > >> builds fine. > >> > >> Not sure if its worth a note in UPDATING, or mentioning it here in the > >> google archives will be good enough for anyone else who runs into it. > >> > > > > I think it is worth a note. I'll add one. > > > > We should also followup with dim@ to see why static_assert from > RELENG_10 > > is incompatible with the new compiler, and why it's used in a way that > > would break. > > I took a quick look, but I don't think there is any quick solution. For > some reason, clang 3.4.1 (which shipped with 10.4) cannot handle the > static_asserts which are inside the piece of code in question. Also, > there are several other compilation errors, due to it being unable or > unwilling to cast pointers. > > Upstream LLVM has recently bumped the requirements for building quite > aggressively, it could very well be that a higher version of clang or > gcc is now required to build 8.0, precisely because of the above. At > some point they apparently wanted to drop the workarounds for old > compilers. > Could you look into what the new requirement is? If there's no simple workaround, I'd like to at least document what the minimum is better than I have. 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"
Re: RELENG_10 to RELENG11 buildworld no possible ?
On 9 Jul 2019, at 08:08, Warner Losh wrote: > > On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote: > On 8 Jul 2019, at 17:38, Warner Losh wrote: > > > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > >>> Hi all, > >>> > Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > Or maybe via 11.2R, if that can be built from RELENG_10? > >>> I just completed a successful build of RELENG_11_2 on a > >>> RELENG_10_4 system … > >>> > >>> Kind regards, > >>> Patrick > >> > >> I am guessing all is good up until > >> > >> > >> https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > >> > >> If I svn update -r346291(commit before the import of the new clang) all > >> builds fine. > >> > >> Not sure if its worth a note in UPDATING, or mentioning it here in the > >> google archives will be good enough for anyone else who runs into it. > >> > > > > I think it is worth a note. I'll add one. > > > > We should also followup with dim@ to see why static_assert from RELENG_10 > > is incompatible with the new compiler, and why it's used in a way that > > would break. > > I took a quick look, but I don't think there is any quick solution. For > some reason, clang 3.4.1 (which shipped with 10.4) cannot handle the > static_asserts which are inside the piece of code in question. Also, > there are several other compilation errors, due to it being unable or > unwilling to cast pointers. > > Upstream LLVM has recently bumped the requirements for building quite > aggressively, it could very well be that a higher version of clang or > gcc is now required to build 8.0, precisely because of the above. At > some point they apparently wanted to drop the workarounds for old > compilers. > > Could you look into what the new requirement is? If there's no simple > workaround, I'd like to at least document what the minimum is better than I > have. Okay, http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html#minimum-required-compiler-version says: Clang 3.5 Apple Clang 6.0 GCC 5.1 Visual Studio 2017 -Dimitry signature.asc Description: Message signed with OpenPGP
