3.4 release fails tests #180
Comments
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): There are two issues here. The first is that the travis-run test suite didn't catch the failure. I'm not sure why that is, but it probably relates to the switch to running the tests using pytest. More importantly, however, is the issue that the implementation now fails. I'll address that promptly. |
Original comment by felixonmars (Bitbucket: felixonmars, GitHub: felixonmars): An updated patch was posted to the thread where #176 links to: https://mail.python.org/pipermail/distutils-sig/2008-April/009196.html A quick look to this patch indicates that it has an if for test_runner unspecified case. |
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): @felixonmars Yes, I did consider that approach in my tests. I wanted to avoid special-casing the test for that attribute and take advantage of the default value (None) for the parameter. I didn't properly consider the implications of the entry-point-style resolution. |
…is-is-very-1456944704555 (pull request #180) feature/msvc-discovery
Originally reported by: felixonmars (Bitbucket: felixonmars, GitHub: felixonmars)
The first problem I encountered is:
python setup.py test
just fails before running any tests. Commit related: https://bitbucket.org/pypa/setuptools/commits/affa32a2d30a1b1c0c29983aa21f4f48312b7edcTraceback:
After digging up a little bit, I tried out
-r "unittest:TextTestRunner"
as a workaround. (So I suggest this becomes a default value)A second problem is: 2 tests fail:
Python 2.7 and 3.4 fail on the same tests with same traceback. The second test (for test itself) indicates the first problem I mentioned above, and I've no idea about the other...
The text was updated successfully, but these errors were encountered: