[twill] Temporary Failure in Name Resolution

[Krieghan J. Riley]

I've been investigation this problem for a few days, now.  I'm somewhat
reluctant to post to this list, as this issue could easily be with my
network/development environment, etc.  However, twill code is in the
traceback, so I figure someone might be able to give me some pointers.

My twill script does a great deal of repetitive actions on a web
application.  Right now, the same operations get executed over and over
with different parameters.  Execution of the script goes as planned
until 10-15 minutes in it dumps with the following:

Traceback (most recent call last):
  File "testclient.py", line 131, in ?
  File "testclient.py", line 60, in RunTestSet
  File "testclient.py", line 43, in Loop
  File "/home/kriley/krileydev/autotest.py", line 120, in RunTest
  File "/home/kriley/krileydev/autotest.py", line 159, in Get
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/browser.py", line 113, in go
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/browser.py", line 516, in _journey
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/other_packages/mechanize/_mechanize.py", line 156, in open
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/other_packages/mechanize/_mechanize.py", line 182, in _mech_open
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/other_packages/mechanize/_opener.py", line 180, in open
  File "urllib2.py", line 376, in _open
  File "urllib2.py", line 337, in _call_chain
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/_browser.py", line 19, in http_open
  File
"/usr/lib/python2.4/site-packages/twill-0.9b1-py2.4.egg/twill/other_packages/mechanize/_http.py", line 644, in do_open
urllib2.URLError: <urlopen error (-3, 'Temporary failure in name
resolution')>
  

The first part of the traceback, the part before it hits twill, is my
code.  The parts that it's tripping over have been executed repeatedly
over the course of execution - it's only after a certain amount of time
has passed that there's a problem.  I should also add that this problem
is consistent - there are no runs where it does not occur.  I have no
network problems that I know of.  I am somewhat stumped...