From owner-freebsd-testing@freebsd.org  Thu May 11 08:07:23 2017
Return-Path: <owner-freebsd-testing@freebsd.org>
Delivered-To: freebsd-testing@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98F13D63F90
 for <freebsd-testing@mailman.ysv.freebsd.org>;
 Thu, 11 May 2017 08:07:23 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 88155D9E
 for <freebsd-testing@freebsd.org>; Thu, 11 May 2017 08:07:23 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4B87M4E041909
 for <freebsd-testing@freebsd.org>; Thu, 11 May 2017 08:07:23 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-testing@freebsd.org
Subject: [Bug 217261] sys/aio/aio_test:aio_md_test fails semi-frequently with
 Jenkins with "aio_write failed: Operation not supported"
Date: Thu, 11 May 2017 08:07:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: tests
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217261-32464-DXMks8IdRo@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217261-32464@https.bugs.freebsd.org/bugzilla/>
References: <bug-217261-32464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>
List-Post: <mailto:freebsd-testing@freebsd.org>
List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2017 08:07:23 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217261

--- Comment #8 from commit-hook@freebsd.org ---
A commit references this bug:

Author: ngie
Date: Thu May 11 08:06:47 UTC 2017
New revision: 318180
URL: https://svnweb.freebsd.org/changeset/base/318180

Log:
  Mark all md tests as requiring unsafe AIO in order to function

  These tests have been flapping (failing<->passing) on Jenkins for months.
  It passes reliably for me if unsafe AIO is permitted, but it doesn't
  pass on Jenkins reliably if unsafe AIO is disabled (the current default).

  Mark the tests as requiring unsafe AIO to mitigate the intermittent
  failures when unsafe AIO isn't permitted. If the kernel code is changed
  to reliably function with md(4) devices using unsafe AIO, this commit can
  be reverted.

  MFC after:    2 months
  PR:           217261
  Reported by:  Jenkins
  Sponsored by: Dell EMC Isilon

Changes:
  head/tests/sys/aio/aio_test.c

--=20
You are receiving this mail because:
You are the assignee for the bug.=