Often error running conan test_package

We get this error often in random places:

opencv/3.1.1@******/stable: WARN: Forced build from source
ERROR: [Error 145] The directory is not empty: 'C:\\Users\\WinBuilder\\.conan\\data\\opencv\\3.1.1\\merlin-ext\\stable\\build\\22357e08bed3f975c745816eb96079b8fc475506\\opencv\\.git\\logs\\refs\\remotes'

grpc/0.15.0@******/stable: WARN: Forced build from source
ERROR: [Error 145] The directory is not empty: u'C:/.conan\\f8jip9\\1\\grpc\\tools\\dockerfile'

We run conan test_package --build=package_name --build=missing Please help

[KindDragon]

“No” was answer to “Does it usually fail in such “.git” folders?” 😃

[memsharded]

Nop, it could seem so, but conan is running in python, in a single thread, nothing concurrent at all. It is the OS that leaves some file handles open (maybe file caching in RAM before writing to disk), and seems the operations have finished, but actually when you try a subsequent action, it fails. It is not the first time it happens, sometimes (always Win), a build of an .exe has finished, you launch it, and it happens to launch the previous version of the .exe, because for some reason, it wasn’t overwritten yet (even if the compile/build process finished). Those tests are usually fixed with one time.sleep(1) second. For removal, it is more complicated, sometimes the handles are just not released by Windows, who knows why.

Still a matter of active investigation, thanks for the feedback!