Éric Araujo <mer...@netwok.org> added the comment: > This problem was not trivial to find, because it appears that test execution > order may not be > entirely deterministic: I couldn't see any other reason why the flag would > have different values > on different machines. On my machine, it looks like unittest runs them in the order they’re found. I have only one core, but maybe tests are run in parallel on your machine, so with the missing call to enable_cache, that would explain the test failures.
Antoine, I appreciate that you took time to fix this bug while I was without Internet and without Windows, but unfortunately I will have to backout your commit. Postel’s Law doesn’t win here: It is documented that the MANIFEST template only accepts /-delimited paths, so I have to find a fix for the tests without changing the code to avoid breaking the feature freeze. I’ll get a Windows VM before I do that, to avoid making the bots red again. In the future, please feel free to add unittest.expectedFailure decorators to problematic tests when I’m too long to come up with a fix, so that other people can see when their commits add problems. ---------- resolution: fixed -> stage: committed/rejected -> status: closed -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13193> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
