[bind10-dev] proposal: skipping time sensitive tests on VMs
JINMEI Tatuya / 神明達哉
jinmei at isc.org
Wed Mar 16 23:22:13 UTC 2011
This failure (false positive) has happened so many times:
http://bind10.isc.org/~tester/builder//BIND10-distcheck/20110316160000-FreeBSD8-i386/logs/distcheck.out
and it has wasted someone's time just even if it's a 30sec check to
confirm it's a non issue. According to the jabber chat a few hours
ago I think we should now deploy a measure to avoid further waste,
even if it's an ugly ad hoc hack.
My proposal is this: set the gtest filter via the TESTS_ENVIRONMENT
and GTEST_FILTER environment variable before running the buildbot on
systems that are known to report a common false positive. We can
begin with this on the freebsd8 VM box, disabling
RecursiveQueryTest.forwardClientTimeout as follows:
TESTS_ENVIRONMENT='GTEST_FILTER=-RecursiveQueryTest.forwardClientTimeout' make [dist]check
I think we can begin with a list of exact matching until we see a
scalability issue. Also, for simplicity, I think we don't have to try
to auto-detect the need for a filter for now.
---
JINMEI, Tatuya
More information about the bind10-dev
mailing list