From owner-freebsd-virtualization@FreeBSD.ORG Sat Oct 25 06:48:04 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D6465A25; Sat, 25 Oct 2014 06:48:04 +0000 (UTC) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B496B2F; Sat, 25 Oct 2014 06:48:04 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id r10so2660083pdi.30 for ; Fri, 24 Oct 2014 23:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=0W9DkqfiAld4WGNwRxVReCOvtZ/9P41LPKGt4Nci47w=; b=epVQvQOiEMDjjCGFLuY7SL5ke0xemxc8uTqDhVvyNveauSg6B9i8NJi8DnCp3U7vlU zbzCv0QK1I/jKkB70joNDOpMDkBSnR9JVznMLxbYUsqJvOXhWYVDMpN2TzgKFd5GLsK5 dhvnvmP0yXtj0Oi1ees9sCOvSyBtJNWDdXEVgO7dLKmWf8MzDFl4yqYM9PXu4KZ9AMXS 3kG+E40gcOtaHKcNgVCYUkh6+q5IifYCAkj0f6joAo6Lpr7WLo5wbHnn9lD4r/BS55Hf w7UdNjs4a+6tf8gJSeq6EcV20eBBdxKg8rKfrlN/xDsexhnnRZa/otfm/CPLDh4INnzZ FOCw== X-Received: by 10.68.213.101 with SMTP id nr5mr9344918pbc.81.1414219684005; Fri, 24 Oct 2014 23:48:04 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:4d3d:33a4:5ddc:37e2? ([2601:8:ab80:7d6:4d3d:33a4:5ddc:37e2]) by mx.google.com with ESMTPSA id nq2sm5418288pdb.74.2014.10.24.23.48.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 23:48:03 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_FDB23D5C-BB5E-410D-95B3-35CE9ACBE165"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Automatically running /usr/tests on stable/10 branch under Jenkins From: Garrett Cooper In-Reply-To: <544B46BA.4000008@freebsd.org> Date: Fri, 24 Oct 2014 23:48:01 -0700 Message-Id: References: <20141024053636.GH11222@dft-labs.eu> <81030948-E60F-4AAD-AAF1-16349607917D@gmail.com> <544B46BA.4000008@freebsd.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD stable , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Oct 2014 06:48:05 -0000 --Apple-Mail=_FDB23D5C-BB5E-410D-95B3-35CE9ACBE165 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Oct 24, 2014, at 23:44, Alfred Perlstein wrote: > On 10/24/14 9:45 PM, Garrett Cooper wrote: >> On Oct 24, 2014, at 21:20, Craig Rodrigues = wrote: >>=20 >>> On Thu, Oct 23, 2014 at 11:06 PM, K. Macy wrote: >>>=20 >>>>>> (2) Creates a bootable UFS image with makefs >>>>> any chance zfs will be used as well? >>>>>=20 >>>> Seconded. There are residual locking issues issues in ZFS. >>>> Particularly in the less exercised areas. >>>>=20 >>> I think what would be an interesting exercise is to set up a Jenkins = job to >>> build >>> and boot a bhyve VM with ZFS, and then run >>> the ZFS Test Suite, ported by Alan Somers to FreeBSD: >>>=20 >>> = https://lists.freebsd.org/pipermail/freebsd-testing/2014-August/000503.htm= l >>>=20 >>>=20 >>> Are there any volunteers who would like to help set that up and get = it >>> running >>> under Jenkins? >> I think getting tools/regression/zfs working first would be a better = idea (which means that ZFS developers will need to go debug/fix the = issue noted in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191574 = ). I=92ll go ahead and commit my fixes to head from my github fork so it = runs. >>=20 >> Alan also suggested against integrating the test suite as-is, because = as he said, "Remember, don't run these tests on a production system. = They WILL cause panics and deadlocks, and they may cause data loss too.=94= >>=20 >> Cheers, >> -Garrett >=20 > Wait, we want to sweep those bugs under the rug? What exactly is = wrong with making a test harness that can very easily reproduce a known = problem? The chances are that anyone will dive into it once the bug is = easily reproducible. Sweeping bugs under the rug is not what I plan on doing; I=92m = marking these as expected failures, as opposed to having them = continually panic a machine. Once a ZFS dev takes a look at the issue = and resolves them, then the ZFS dev can remove the =93bail=94 calls I=92m = adding to the testcases. Cheers, -Garrett PS FWIW the panics are recent. As I stated in the first bug, it didn=92t = occur on 10.0-RELEASE. --Apple-Mail=_FDB23D5C-BB5E-410D-95B3-35CE9ACBE165 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUS0eiAAoJEMZr5QU6S73ejxcIALZRkCzcpT6cfWtwDIgts2rz 5zUOJHgmExFkkijOtd7m9HEFnQQcEDQ8JJ0P/s6Fvol2/gKfRCtjd51+ip2Dj8ya g67V81qOxTFomCWo9VxWMWaBtPsowP8wwG/ZL0QkKCYQlLQITNNVu8/FsKODpIbm IKja9Bk97du9oI7+1T6L0FvkRvvk7m7MJxkzI373HKTb6+hmmt7YK9jRQ7fh5efG Qy7Ce4UUAffr6V/PHqhVvxZLiZkSa69hnY9MaAKXkVRPvIgUFTFhdYTCKqw7L8Ua vJx+zflZEzCnA2a9NC0Llcf0roNsnPV/E11F5vBzhhIY1ICx2dx2Gj99298zHPE= =pm2N -----END PGP SIGNATURE----- --Apple-Mail=_FDB23D5C-BB5E-410D-95B3-35CE9ACBE165--