Automatically running /usr/tests on stable/10 branch under Jenkins
Garrett Cooper
yaneurabeya at gmail.com
Sat Oct 25 06:48:05 UTC 2014
On Oct 24, 2014, at 23:44, Alfred Perlstein <alfred at freebsd.org> wrote:
> On 10/24/14 9:45 PM, Garrett Cooper wrote:
>> On Oct 24, 2014, at 21:20, Craig Rodrigues <rodrigc at freebsd.org> wrote:
>>
>>> On Thu, Oct 23, 2014 at 11:06 PM, K. Macy <kmacy at freebsd.org> wrote:
>>>
>>>>>> (2) Creates a bootable UFS image with makefs
>>>>> any chance zfs will be used as well?
>>>>>
>>>> Seconded. There are residual locking issues issues in ZFS.
>>>> Particularly in the less exercised areas.
>>>>
>>> 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:
>>>
>>> https://lists.freebsd.org/pipermail/freebsd-testing/2014-August/000503.html
>>>
>>>
>>> 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=191574 ). I’ll go ahead and commit my fixes to head from my github fork so it runs.
>>
>> 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.”
>>
>> Cheers,
>> -Garrett
>
> 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’m 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 “bail” calls I’m adding to the testcases.
Cheers,
-Garrett
PS FWIW the panics are recent. As I stated in the first bug, it didn’t occur on 10.0-RELEASE.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20141024/a8190640/attachment.sig>
More information about the freebsd-stable
mailing list