Date: Thu, 2 Oct 2014 13:56:42 -0400 From: Julio Merino <jmmv@freebsd.org> To: Craig Rodrigues <rodrigc@freebsd.org> Cc: 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: <CAFY7cWBG%2Bo08BvBUmXt5b6c9jdPctvnCuzPJfhVvKTLyuH=zsA@mail.gmail.com> In-Reply-To: <CAG=rPVcV6fsUJYezyxSsiTkcjXA8izqAHce8orujZur68YosGA@mail.gmail.com> References: <CAG=rPVcV6fsUJYezyxSsiTkcjXA8izqAHce8orujZur68YosGA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues <rodrigc@freebsd.org> wrote: > Hi, > > I have managed to eliminate all the test failures from /usr/tests in CURRENT > except for one failure. See: > > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ > > I can reproduce the failure by doing the following: > > mkdir /tmp/x > cd /tmp/x > /usr/tests/usr.bin/yacc/yacc_tests usr.bin.yacc.yacc_tests.main > > I then get a core file: /tmp/x/test/yacc.core > > Can someone help debug and fix this? 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).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFY7cWBG%2Bo08BvBUmXt5b6c9jdPctvnCuzPJfhVvKTLyuH=zsA>