Message147489
> 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. |
|
Date |
User |
Action |
Args |
2011-11-12 14:35:07 | eric.araujo | set | recipients:
+ eric.araujo, paul.moore, vinay.sajip, pitrou, nadeem.vawda, tarek, rpetrov, flox, alexis, michael.mulich, westley.martinez, python-dev, jlove, higery, francismb |
2011-11-12 14:35:07 | eric.araujo | set | messageid: <1321108507.89.0.308466488672.issue13193@psf.upfronthosting.co.za> |
2011-11-12 14:35:07 | eric.araujo | link | issue13193 messages |
2011-11-12 14:35:06 | eric.araujo | create | |
|