[issue16709] unittest discover order is filesystem specific - hard to reproduce

2013-03-18 Thread Jeff Ramnani
Jeff Ramnani added the comment: I've added tests for this behavior by un-sorting the test inputs for test_find_tests, and adding comments that the results should be sorted for reliable test execution. Attaching an updated patch. -- nosy: +jramnani Added file:

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2013-03-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset fe18f16dc2a6 by Michael Foord in branch 'default': Closes issue 16709. unittest test discovery sorts test files for consistent test ordering http://hg.python.org/cpython/rev/fe18f16dc2a6 -- nosy: +python-dev resolution: - fixed stage:

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2013-02-23 Thread Martin Melin
Martin Melin added the comment: Not sure if there was anything more to it than this, but please find an attempt to add this attached. -- keywords: +patch nosy: +mmelin Added file: http://bugs.python.org/file29197/issue16709.patch ___ Python tracker

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2013-02-23 Thread Petri Lehtinen
Petri Lehtinen added the comment: The patch looks good to me. -- nosy: +petri.lehtinen stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16709 ___

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2013-02-23 Thread Michael Foord
Michael Foord added the comment: As we're specifying this behaviour in the documentation it would be nice to test it. -- stage: patch review - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16709

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-25 Thread Ezio Melotti
Ezio Melotti added the comment: Should this be considered a new feature or should it be applied to older versions as well? -- keywords: +easy stage: - needs patch type: - enhancement ___ Python tracker rep...@bugs.python.org

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-25 Thread Michael Foord
Michael Foord added the comment: It smells like a feature to me (it isn't a direct bug fix anyway). It can be applied to earlier versions of Python through a new unittest2 release. -- versions: +Python 3.5 -Python 2.7, Python 3.2, Python 3.3 ___

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-21 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 3.1, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16709 ___ ___

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-18 Thread Michael Foord
Michael Foord added the comment: Seems reasonable. -- assignee: - michael.foord ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16709 ___ ___

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-18 Thread vila
Changes by vila v.ladeuil+bugs-pyt...@free.fr: -- nosy: +vila ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16709 ___ ___ Python-bugs-list mailing

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-17 Thread Robert Collins
New submission from Robert Collins: Openstack recently switched from nose to using discover. discover walks the filesystem using os.listdir(), and that is just a thin layer over readdir. On ext3/ext4 filesystems, readdir is in an arbitrary order dependent on file insertion into the directory

[issue16709] unittest discover order is filesystem specific - hard to reproduce

2012-12-17 Thread Antoine Pitrou
Antoine Pitrou added the comment: +1. It also makes test output nicer. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16709 ___ ___