From owner-freebsd-testing@FreeBSD.ORG  Thu Dec 18 20:59:45 2014
Return-Path: <owner-freebsd-testing@FreeBSD.ORG>
Delivered-To: freebsd-testing@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 4F29715F
 for <freebsd-testing@freebsd.org>; Thu, 18 Dec 2014 20:59:45 +0000 (UTC)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com
 [209.85.216.172])
 (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 188A4225F
 for <freebsd-testing@freebsd.org>; Thu, 18 Dec 2014 20:59:45 +0000 (UTC)
Received: by mail-qc0-f172.google.com with SMTP id m20so1528891qcx.17
 for <freebsd-testing@freebsd.org>; Thu, 18 Dec 2014 12:59:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
 :date:message-id:subject:to:cc:content-type;
 bh=uu37QRaZV9Zx9ghxG4fL/Xd+RewebzC9dzQp3FtGsHs=;
 b=EBAP8VFyC5gpFOQ9s9wGyQV1VABW0KWv8BM9WAJNzJBlbZVtA8HoXZcjApeXUIVfMa
 GK4/SsUAtX8P4Rgq9S5JrfHH/uRbx88vE47yUiNEQVnEBvwpYtIMN+BMvOEsWB1jFmGb
 3C1n6SExSvWSvXUkrALRzpn3WbN7SaWhJysKmUq3XSGYO1VvYG8UKL+5bHLCI5fucpFE
 crFUS3DlFygjyYy1faBpl4zkbIuZXI1uR3QxH+kZSj6094khL08cys84uppeW95mSwvw
 SHU7sdfF4Wwzf5imS2NmGR2kRJAIHdxK4aOJm4bbvE4i1WWP7fGCwDjqxXPhWwB8BWF1
 dMNQ==
X-Gm-Message-State: ALoCoQn3vjSKw4h0ADVS4MCTzpwyRIMhrKsNjtt4ToQT5jwQuCB/Gn6YRth23nnx1Y7Zn++tsogo
X-Received: by 10.140.40.51 with SMTP id w48mr7336666qgw.34.1418936384053;
 Thu, 18 Dec 2014 12:59:44 -0800 (PST)
MIME-Version: 1.0
Sender: jmmv@meroh.net
Received: by 10.96.154.4 with HTTP; Thu, 18 Dec 2014 12:59:23 -0800 (PST)
X-Originating-IP: [2620:0:1003:1007:51a6:ae44:98bd:55f]
In-Reply-To: <CAG=rPVf-73AZ2tbd6Wz7HEOJ9Z8XKCxqewu3j1jj8+0A35wmww@mail.gmail.com>
References: <E4E2C35985835241BF1BFB6F497FBB7A12E21247@SIXPRD3002MB012.064d.mgd.msft.net>
 <CAG=rPVf-73AZ2tbd6Wz7HEOJ9Z8XKCxqewu3j1jj8+0A35wmww@mail.gmail.com>
From: Julio Merino <jmmv@freebsd.org>
Date: Thu, 18 Dec 2014 15:59:23 -0500
X-Google-Sender-Auth: LjJLKfPReilKTt7rUTQstfvIzYw
Message-ID: <CAFY7cWA7xPWdyjFwtchmeGV8a2mvwiRW-M0U2_t2w=tDXZgakg@mail.gmail.com>
Subject: Re: One kyua test failure in FreeBSD10.1 running on Hyper-V 2012R2
To: Craig Rodrigues <rodrigc@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>,
 "Andy Zhang \(AZURE\)" <xiazhang@microsoft.com>
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.18-1
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, 18 Dec 2014 20:59:45 -0000

On Fri, Dec 5, 2014 at 4:29 PM, Craig Rodrigues <rodrigc@freebsd.org> wrote:
> On Fri, Dec 5, 2014 at 4:10 AM, Andy Zhang (AZURE) <xiazhang@microsoft.com>
> wrote:
>
>>
>>    - usr.bin/yacc/legacy_test:main
>>    <http://usr.bin_yacc_legacy_test_main.html>
>>
>>
>>
> Andy,
>
> Thank you for taking the time to run the FreeBSD tests, and report
> the results after running them in Hyper-V.  Your input is valuable.
>
> I believe that the yacc test failures are known and have been reported in
> our
> bug system:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499
>
> Unfortunately, the fix for this test did not make it into 10.1-RELEASE,
> but should be available in newer FreeBSD versions.

We should mark this test as an "expected failure". Unfortunately, this
is currently not possible with the plain interface so the easiest way
would be to wrap the test into an ATF test program.