[tahoe-dev] win32 buildslave is wedged again

[Nathan]

I find this odd.

Could you provide more details on the symptoms?  Do all outgoing TCP
connections fail after X time, or does some small fraction fail
overall?  How is the time X distributed?  Do other networking
functions remain unchanged?  Do other TCP processes besides
builtbot/tahoe function?

What are the potential causes?  Here's my brainstorm from most likely to least:
a. network config
b. virtualization glitch/bug (ethernet driver flakiness?)  Which vm do you use?
c. XP driver bug (especially for a strange VM device).
d. SSL or other strange connection libraries.
d. Tahoe in general.
e. Twisted.
f. General XP kernel bug.

If you discover the cause, could you please post details?  -at least
if it's not a., I'd find the result educational.

Although scripting a vm reboot or reset every so often may solve the
problem, it's good to know exactly what the test environment tests.
-although frequent reboots may provide a more realistic test model for
XP boxes.


N



On Dec 17, 2007 3:03 PM, zooko <zooko at zooko.com> wrote:
> Folks:
>
> Unfortunately, it seems like the virtual machine that the Win32
> buildslave runs in tends to lose its ability to open outgoing TCP
> connections every so often:
>
> http://allmydata.org/buildbot/builders/windows
>
> Could we configure the host to reset the guest OS every so often, or
> something?
>
> Regards,
>
> Zooko
>
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
>