Date: Thu, 31 Jan 2019 06:48:33 +0800 From: Li-Wen Hsu <lwhsu@freebsd.org> To: Kyle Evans <kevans@freebsd.org> Cc: freebsd-testing@freebsd.org Subject: Re: FreeBSD CI Weekly Report 2018-01-20 Message-ID: <CAKBkRUx047-a3GHjW%2BgbDWm=TcFNH6qtxPP0BmHBhOwRKWJEyA@mail.gmail.com> In-Reply-To: <CACNAnaFHPHU_Sj3F9%2B3OwKKAFXSNV5vS%2By47Ev%2Bv8mD%2B5rUV=A@mail.gmail.com> References: <20190122044429.GA32825@freefall.freebsd.org> <CACNAnaFHPHU_Sj3F9%2B3OwKKAFXSNV5vS%2By47Ev%2Bv8mD%2B5rUV=A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 23, 2019 at 9:55 AM Kyle Evans <kevans@freebsd.org> wrote: > I'll take a poke at the bectl and *regex failures. Is there any way to > see an excerpt of the cleanup from these bectl tests? The failure > there is a symptom of the zpool from one of the other tests not > getting cleaned up properly, presumably the bectl jail test. I can't > seem to reproduce it locally, though. Do you mean how do you see if your commit fixes the test? One possible way is checking the "build summary" page, e.g. https://ci.freebsd.org/job/FreeBSD-head-amd64-test/lastCompletedBuild/ and see if that build contains your commit. For reproducing, I think the easiest way for now is using the VM files at https://artifact.ci.freebsd.org . If the test cases failed because of the test environment, please let me know and I'll fix that. Thanks, Li-Wen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKBkRUx047-a3GHjW%2BgbDWm=TcFNH6qtxPP0BmHBhOwRKWJEyA>