From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 18:14:20 2014 Return-Path: Delivered-To: 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 3336A570; Thu, 2 Oct 2014 18:14:20 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (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 E37D3B74; Thu, 2 Oct 2014 18:14:19 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id eu11so3085771pac.28 for ; Thu, 02 Oct 2014 11:14:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=QWQ8L25jEUSh/OJsFH/urv+76F/w2C0VfIjoHg4shr0=; b=xwZbSQfzMqNMNv3Xo3ekMcyBpqZLjOpL9uvSJ4V6en+0bBh5wxeW0+Spls5IJ6KYTA 1IyB4kSoTYMWbO1Y+sK7XUaoGtTvJt8dWl9HnKseasjdUTDeLjle5glfSTO259PFJ6dn JTN74HVc8uaexae/XKjsOxi+3n7LcFoE66/eXW6xJK9fYT4ix4WXaHXC88nr7/gGqitE eX2ORB3AoUmSXUOUH+PpLsqcnrLoH6dXmWo3d2Qspt6a4oIHmf3v+yfV60gvO2287xXV OQZqTrA2lZ5xpQIX74dsdoFddANM7OfpQrzsj1aGyyVlqKX3sJQPfCG+3drRIAaVBFDb WSDA== X-Received: by 10.69.31.1 with SMTP id ki1mr782485pbd.100.1412273657998; Thu, 02 Oct 2014 11:14:17 -0700 (PDT) Received: from [192.168.20.11] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id ot8sm4438660pbc.1.2014.10.02.11.14.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 11:14:17 -0700 (PDT) References: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> Mime-Version: 1.0 (1.0) In-Reply-To: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <3B9D64BE-9982-4334-B20B-E316A8361466@gmail.com> X-Mailer: iPhone Mail (11D257) From: Garrett Cooper Subject: Re: Need help debugging yacc test failure in CURRENT Date: Thu, 2 Oct 2014 11:14:17 -0700 To: Julio Merino Cc: Baptiste Daroussin , freebsd-current Current , "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 18:14:20 -0000 > On Oct 2, 2014, at 11:10, Garrett Cooper wrote: >=20 >=20 >>> On Oct 2, 2014, at 10:56, Julio Merino wrote: >>>=20 >>> On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wr= ote: >>> Hi, >>>=20 >>> I have managed to eliminate all the test failures from /usr/tests in CUR= RENT >>> except for one failure. See: >>>=20 >>> https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport= / >>>=20 >>> I can reproduce the failure by doing the following: >>>=20 >>> mkdir /tmp/x >>> cd /tmp/x >>> /usr/tests/usr.bin/yacc/yacc_tests usr.bin.yacc.yacc_tests.main >>>=20 >>> I then get a core file: /tmp/x/test/yacc.core >>>=20 >>> Can someone help debug and fix this? >>=20 >> What you'd do until someone fixes the yacc bug is file a PR for this >> crash and then mark the test as "expected failure" (or TODO in TAP >> terms). >=20 > There already is a bug (look or bugs I filed related to yacc). Someone bro= ke behavior in the kernel or libc that yacc depends on. Let me rephrase that. Using an older atf/kyua didn't repro the bug, so it's p= robably atf/kyua=