Skip Menu |

This queue is for tickets about the Net-DNS-DynDNS CPAN distribution.

Report information
The Basics
Id: 95607
Status: resolved
Priority: 0/
Queue: Net-DNS-DynDNS

People
Owner: Nobody in particular
Requestors: CHORNY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.995
Fixed in: (no value)



Subject: tests sometimes fail
On Tue May 13 18:43:58 2014, CHORNY wrote: Show quoted text
> See for ex. this report > http://www.cpantesters.org/cpan/report/5c9a11f1-6c1c-1014-bb34- > 9608d676aea3 and this report > http://www.cpantesters.org/cpan/report/71073d76-bde5-11e3-ac1a- > fc1bfffb7322 , they have different errors.
Hi Alexandr, Thanks for your work on CPAN Testers. I know that Net::DNS::DynDNS occansionally fails, but I have seen instances where it works on seemingly identical testing configurations. I've been assuming the test failures are caused by local conditions (such as being firewalled/disconnected from the internet) or remote conditions (such as dyn.com having an outage), both of which it is difficult to get more feedback on. Can you help me with a suggestion for improving the test suite? Cheers Dave
On 2014-05-13 02:15:29, DDICK wrote: Show quoted text
> On Tue May 13 18:43:58 2014, CHORNY wrote:
> > See for ex. this report > > http://www.cpantesters.org/cpan/report/5c9a11f1-6c1c-1014-bb34- > > 9608d676aea3 and this report > > http://www.cpantesters.org/cpan/report/71073d76-bde5-11e3-ac1a- > > fc1bfffb7322 , they have different errors.
> > Hi Alexandr, > > Thanks for your work on CPAN Testers. I know that Net::DNS::DynDNS > occansionally fails, but I have seen instances where it works on > seemingly identical testing configurations. I've been assuming the > test failures are caused by local conditions (such as being > firewalled/disconnected from the internet) or remote conditions (such > as dyn.com having an outage), both of which it is difficult to get > more feedback on. Can you help me with a suggestion for improving the > test suite?
You could make a simple network connection at the top of each test (say via a shared t/lib module) that will let you determine if the network is available, and gracefully skip the tests that are dependent on that.
On Wed May 14 02:41:21 2014, ETHER wrote: Show quoted text
> You could make a simple network connection at the top of each test > (say via a shared t/lib module) that will let you determine if the > network is available, and gracefully skip the tests that are dependent > on that.
Done in 0.996 being uploaded to PAUSE now. Closing if this is sufficient. Feel free to re-open if you need more.