aaron> vila wrote:
>>>>>>> "Ian" == Ian Clatworthy writes:
>>
Ian> Public bug reported:
Ian> This has been introduced just recently in bzr.dev. It doesn't happen in
Ian> 0.91rc2. It happens on both python 2.4 and python 2.5. It doesn't
Ian> actually break tests but it's ugly noise.
>>
>> I can't reproduce it, any hint about your setup ? OS ?
aaron> I saw this when I tested your socket leak fix, on
aaron> Debian Etch/Python2.4.4. It only seems to happen on
aaron> one test case, but it wasn't clear which one.
Funny how all of you seem to be bitten by the bug while I couldn't
reproduce it on Solaris/OSX/Feisty :-)
aaron> I presume that your changes have exposed a latent bug.
aaron> But I felt they were still worth merging even if that
aaron> was the case.
For the record, there was several hundreds sockets left in a
listen state, so, I really think it was worth merging too.
I updated to gutsy (lost some hours with a CPU at 100% making it
hard to debug the issue (but I digress)).
I can reproduce it now, seems both pretty random while easy to
reproduce, let the fun continues :)
>>>>> "aaron" == Aaron Bentley> writes:
aaron> vila wrote:
>>>>>>> "Ian" == Ian Clatworthy writes:
>>
Ian> Public bug reported:
Ian> This has been introduced just recently in bzr.dev. It doesn't happen in
Ian> 0.91rc2. It happens on both python 2.4 and python 2.5. It doesn't
Ian> actually break tests but it's ugly noise.
>>
>> I can't reproduce it, any hint about your setup ? OS ?
aaron> I saw this when I tested your socket leak fix, on
aaron> Debian Etch/Python2.4.4. It only seems to happen on
aaron> one test case, but it wasn't clear which one.
Funny how all of you seem to be bitten by the bug while I couldn't
reproduce it on Solaris/OSX/Feisty :-)
aaron> I presume that your changes have exposed a latent bug.
aaron> But I felt they were still worth merging even if that
aaron> was the case.
For the record, there was several hundreds sockets left in a
listen state, so, I really think it was worth merging too.
I updated to gutsy (lost some hours with a CPU at 100% making it
hard to debug the issue (but I digress)).
I can reproduce it now, seems both pretty random while easy to
reproduce, let the fun continues :)