From owner-freebsd-testing@freebsd.org Tue Mar 26 11:51:55 2019 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FE0A154EBD1 for ; Tue, 26 Mar 2019 11:51:55 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41F4E8D667; Tue, 26 Mar 2019 11:51:55 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id D37E0884C; Tue, 26 Mar 2019 11:51:54 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f175.google.com with SMTP id j89so10845174ljb.1; Tue, 26 Mar 2019 04:51:54 -0700 (PDT) X-Gm-Message-State: APjAAAWteqvjNtSilmmEwhoFkuPGg3Ral2UYIvO4v6QcI4fUP/VWuRS/ hBN19U1CqS8oKNU/iCTMnpikGrxOzjXPgG0gkPw= X-Google-Smtp-Source: APXvYqyxGRKDjZ4y8tInmt7NmTO+3U2jBCMbce8Hx6+m6yGsMmGi+zOx9+yxA2fF9zJN5CaIBAKvlnGBmRn9nzTNUgA= X-Received: by 2002:a2e:9c09:: with SMTP id s9mr16125173lji.83.1553601113477; Tue, 26 Mar 2019 04:51:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Tue, 26 Mar 2019 06:51:42 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD CI Weekly Report 2019-03-24 To: Li-Wen Hsu Cc: freebsd-testing@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 41F4E8D667 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.92 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.92)[-0.917,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Mar 2019 11:51:55 -0000 On Mon, Mar 25, 2019 at 6:24 AM Li-Wen Hsu wrote: > > (bcc -current and -stable for more audience) > > FreeBSD CI Weekly Report 2019-03-24 > =================================== > > Here is a summary of the FreeBSD Continuous Integration results for > the period from 2019-03-18 to 2019-03-24. > > During this period, we have: > > * 2286 builds (98.3% passed, 1.7% failed) were executed on aarch64, > amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, > powerpcspe, riscv64, sparc64 architectures for head, stable/12, > stable/11 branches. > * 498 test runs (37.3% passed, 60.7% unstable, 2% exception) were > executed on amd64, i386, riscv64 architectures for head, stable/12, > stable/11 branches. > * 15 doc buils (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/rybS4spvN 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 > * lib.libc.sys.sendfile_test.fd_positive_shm_v4 > * lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 > The lib.libc.regex.exhaust_test.regcomp_too_big failure should be fixed by r345516 pulling in an rlimit bump from upstream. They didn't adjust the test metadata though -- it previously reflected a memory requirement of 64M, which matched the rlimit imposed. I would expect that needs increased if we're exhausting 64M like we were on some systems, but I'm unsure if we should just bump that sucker to 256M or try to find an intermediate that's sufficient. I suspect the 256M bump wasn't a measurement of usage. > [... snip ...] Thanks, Kyle Evans