Date: Mon, 1 Apr 2019 23:08:35 +0800 From: Li-Wen Hsu <lwhsu@freebsd.org> To: Kyle Evans <kevans@freebsd.org> Cc: Enji Cooper <yaneurabeya@gmail.com>, freebsd-testing@freebsd.org Subject: Re: FreeBSD CI Weekly Report 2019-03-24 Message-ID: <CAKBkRUy8vvez-aJ6hJHNbM_O%2BLutvm5A-XzjGYNc508ojyjHRw@mail.gmail.com> In-Reply-To: <CACNAnaEHbZq7Bve2YdV92Nyf40g9DY==rSJXP2zHiEcpO3ob-A@mail.gmail.com> References: <CAKBkRUz5zBfn=Aw4R_Z3mUgcxi55EBkOpKKSpAYyL=3r8iZkPQ@mail.gmail.com> <CACNAnaFC=N4K9_yqhUd_W_cDay3dH_Jss6RgCrguJw0rambMLQ@mail.gmail.com> <41F71A29-A934-408D-B57D-844EB4BC3C83@gmail.com> <CACNAnaEHbZq7Bve2YdV92Nyf40g9DY==rSJXP2zHiEcpO3ob-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 26, 2019 at 10:10 PM Kyle Evans <kevans@freebsd.org> wrote: > Looking back at the NetBSD history, I do see that you upstreamed the > 64M limit and dropped the requirements from 120M to 64M in the > metadata. =-( Apologies for not researching that more closely- I had > only seen that they upped the setrlimit ~two weeks ago and assumed it > was safe at this point. r345516 does fix the case, and the MFC waiting period (3 days) has passed. Do you want to MFC it and fix stable/12? Thanks, Li-Wen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKBkRUy8vvez-aJ6hJHNbM_O%2BLutvm5A-XzjGYNc508ojyjHRw>