On 09/01/2013 19:46, Jim Gish wrote:
It's a Windows feature. We discovered this recently in debugging
another test failure. Windows is documented to do asynchronous
deletes. You can't depend on a file.delete() which returns true to
have actually deleted the file. It may be the case that another
process has a file handle which it has not yet released, or it's
simply a delay.
I don't get this, the issue sounds more like AV software or Windows
application quality service/agent thing accessing the file but I might
be wrong of course. Are you able to duplicate this reliably and if so,
have you looked at it with any tools to see what/who is accessing it
that is causing the delay?
-Alan.
