On Wed, Oct 02, 2013 at 09:55:46AM +0200, Christian Walde
<[email protected]> wrote:
> You're right, not all system breakages can be or can be expected to be
> detected and worked around by tests. I was describing the intent of the
> cpantesters infrastructure and why i believe that your specific test is an
> ideal case that can do this.
If cpantesters infrastructure uses a broken DNS setup then this is a great
disservice to it's users, and should be fixed ASAP. There is no point in
creating an environment that is broken on purpose, creating false test
failures and wasting everybodies time.
> >How would you dteect the breakage? All your proposed is hardcoding
> >OpenDNS servers somehow. That doesn't detect any breakage.
>
> My first thoughts on this were naive, but in the meantime i've picked up
> better ideas on the matter. A very simple way of testing for a DNS service
> that returns bogus results instead of failing properly would simply
> be this:
Can you explain how this actually detects a broken dns service? It seems
you are simply skipping the test on failure, which is the same as not
having it in the first place.
In any case, it's pretty easy to break perl modules willingly in a lot of
ways. If you already know that your environment is misconfigured, then you
can simply skip the tests yourself.
As it is, the test diagnoses actual problems that people have. There is no
need to make the test ineffective for artificially created problems that a
single user has created.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
anyevent mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/anyevent
