• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

michaelherold / pyIsEmail / 40 / 1
95%
master: 95%

Build:
DEFAULT BRANCH: master
Ran 18 Apr 2015 06:41PM UTC
Files 17
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Apr 2015 06:32PM UTC coverage: 95.636% (+0.04%) from 95.596%
40.1

push

travis-ci

michaelherold
Fail DNS tests when the query times out or fails

In the rare event that the DNS servers time out or no nameserver returns
an answer to a DNS query, we handle the error state returned for the DNS
check.

I made the decision to just add two more failure diagnoses for this
purpose. The alterative would be to try the query again, to see if an
answer will be returned on the retry. However, retrying isn't favorable
because:

1. When no nameservers return a response to a query, this indicates
a misconfiguration on the server running the check. That type of failure
isn't transient; it requires reconfiguration, so we shouldn't retry the
request.

2. `dnspython` times out a DNS request after 30 seconds. Retrying the
query could cause _another_ 30 second timeout to occur. Waiting a full
minute for a response is a terrible user experience, so we should make
the developer handle this case.

Fixes #3

526 of 550 relevant lines covered (95.64%)

0.96 hits per line

Source Files on job 40.1
  • Tree
  • List 0
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 40
  • Travis Job 40.1
  • f8f4af7b on github
  • Prev Job for on master (#39.1)
  • Next Job for on master (#41.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc