Date: Thu, 2 Oct 2014 11:10:19 -0700 From: Garrett Cooper <yaneurabeya@gmail.com> To: Julio Merino <jmmv@freebsd.org> Cc: Craig Rodrigues <rodrigc@freebsd.org>, Baptiste Daroussin <bapt@FreeBSD.org>, freebsd-current Current <freebsd-current@freebsd.org>, "freebsd-testing@freebsd.org" <testing@freebsd.org> Subject: Re: Need help debugging yacc test failure in CURRENT Message-ID: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> In-Reply-To: <CAFY7cWBG%2Bo08BvBUmXt5b6c9jdPctvnCuzPJfhVvKTLyuH=zsA@mail.gmail.com> References: <CAG=rPVcV6fsUJYezyxSsiTkcjXA8izqAHce8orujZur68YosGA@mail.gmail.com> <CAFY7cWBG%2Bo08BvBUmXt5b6c9jdPctvnCuzPJfhVvKTLyuH=zsA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Oct 2, 2014, at 10:56, Julio Merino <jmmv@freebsd.org> wrote: >=20 >> On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues <rodrigc@freebsd.org> wro= te: >> Hi, >>=20 >> I have managed to eliminate all the test failures from /usr/tests in CURR= ENT >> 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). There already is a bug (look or bugs I filed related to yacc). Someone broke= behavior in the kernel or libc that yacc depends on.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8E14869A-049B-4BBA-BE51-714AD202F191>