On Tue, Oct 7, 2014 at 4:38 PM, Craig Rodrigues <rodr...@freebsd.org> wrote:
> On Tue, Oct 7, 2014 at 4:30 PM, NGie Cooper <yaneurab...@gmail.com> wrote:
>> On Tue, Oct 7, 2014 at 2:04 PM, Craig Rodrigues <rodr...@freebsd.org>
>> > Hi,
>> > After committing this fix to yacc in HEAD (
>> > https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092553.html
>> > )
>> > I've been able to do: "cd /usr/tests; kyua test"
>> > and get 0 test failures:
>> > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/16/testReport/
>> Awesome -- hopefully this will be sustained for several runs (this
>> is part of the reason why I haven't integrated all of the NetBSD tests
>> Thank you for all your work in getting us to green!
> For any type of test framework, if the tests aren't run regularly
> and reported in an easy to understand manner,
> then the tests will bitrot and people will ignore them.
> I've seen this happen in multiple companies I have worked at.
> Hopefully we can do better with FreeBSD, and foster a community
> of people who are actively updating the tests, and taking test failures
> If we don't do this, then people will just ignore the tests.
Agreed. The problem with the NetBSD testcases and some of the bits
in tools/regression is that there are a certain batch which are
non-deterministic and blur the lines between functional and unittest.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"