Dave Malcolm <dmalc...@redhat.com> added the comment: On Sat, 2012-01-28 at 23:56 +0000, Terry J. Reedy wrote: > Terry J. Reedy <tjre...@udel.edu> added the comment: > > > I think you should check with randomization enabled, if only to see the > > nature of the failures and if they are expected. > > Including the list of when-enabled expected failures in the release > notes would help those who compile and test.
OK, though note that because it's random, I'll have to run it a few times, and we'll see what shakes out. Am running with: $ make test TESTPYTHONOPTS=-R leading to: ./python -E -bb -R ./Lib/test/regrtest.py -l BTW, I see: Testing with flags: sys.flags(debug=0, division_warning=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=1, verbose=0, bytes_warning=2) which doesn't list the new flag. Should I add it to sys.flags? (or does anyone ever do tuple-unpacking of that PyStructSequence and thus rely on the number of elements?) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13703> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
