[bind10-dev] reporting disabled tests?

[Jeremy C. Reed]

On Fri, 16 Jul 2010, JINMEI Tatuya / ???? wrote:

> Some of our tests *temporarily* disabled.  I emphasized "temporarily"
> because it should basically be considered a short term workaround but
> in reality we tend to forget/ignore them.  This may be more so
> recently because the warning messages from gtest are often hidden from
> python test reports (you can see it by running make check on top of
> the source tree)

Can you please provide some specific examples?

I see a couple "make check" output with "YOU HAVE n DISABLED TESTS" 
and I see 
"[ RUN      ] CacheTest.disabled
[       OK ] CacheTest.disabled (0 ms)"

And I see code with DISABLED_foo.

But I don't see any correlation in the "make check" output itself to 
recognize the specific disabled checks.

> So I wonder whether we should be bugged about those periodically.
> 
> Does it make sense (and if so is it easy) to have buildbot report
> disabled tests if there's any with a moderate rate limiting (e.g. at
> most once a week)?

I will do this weekly. Can you please provide a regular expression 
pattern(s) I can use to match them (since I can't see them now)?