[pacman-dev] cygwin and pactest weirdness
For the last few months, I have been getting random failures, at almost every make check run. For example : ================================================================================ Running 'sync042' Install a sync package conflicting with a local one -------------------------------------------------------------------------------- ==> Generating test environment Traceback (most recent call last): File "./pactest/pactest.py", line 104, in <module> env.run() File "/divers/pacman/pactest/pmenv.py", line 71, in run t.generate() File "/divers/pacman/pactest/pmtest.py", line 108, in generate shutil.rmtree(self.root) File "/usr/lib/python2.5/shutil.py", line 169, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.5/shutil.py", line 169, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.5/shutil.py", line 169, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.5/shutil.py", line 169, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.5/shutil.py", line 169, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.5/shutil.py", line 169, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib/python2.5/shutil.py", line 178, in rmtree onerror(os.rmdir, path, sys.exc_info()) File "/usr/lib/python2.5/shutil.py", line 176, in rmtree os.rmdir(path) OSError: [Errno 90] Directory not empty: '/divers/pacman/root/var/lib/pacman/sync/sync/pkg1-1.0-1' make[2]: *** [check-local] Error 1 make[2]: Leaving directory `/divers/pacman' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/divers/pacman' make: *** [check-recursive] Error 1 make check 300.15s user 425.34s system 98% cpu 12:15.82 total $ ls /divers/pacman/root/var/lib/pacman/sync/sync/* /divers/pacman/root/var/lib/pacman/sync/sync/pkg1-1.0-1: /divers/pacman/root/var/lib/pacman/sync/sync/pkg2-1.0-1: depends desc It looks like pkg1 directory is actually empty afterward. So it looks like some odd race conditions. I am not sure what triggered it. Maybe I did a python update. Or my system/disk became slower. I don't really know, but it's quite annoying, and I am not sure what to do. I guess I should try to write a minimal testcase, like a python script creating and removing a bunch of files, see if I can reproduce it.
participants (1)
-
Xavier