This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients belopolsky, musically_ut, ned.deily, serhiy.storchaka, vstinner
Date 2017-07-05.14:28:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYy3PUb8iC7WFXh1Mtgx_7TYtAkT7MMFfsEGVHjtBN6QQ@mail.gmail.com>
In-reply-to <1499263743.63.0.634853682458.issue30822@psf.upfronthosting.co.za>
Content
> These tests were supposed to be exhaustive and I did not expect them to be run by default.  that's why I introduced the -utzdata flag in the first place.

Buildbots use "-u all" and so enables tzdata tests. Is it useful to
run all these tests on all branches for each Python commit?

Maybe we should disable these tests on all CI, and maybe setup a
buildbot which runs these tests?

Instead of being exhaustive, would it be possible to pick a few
significant tests?
History
Date User Action Args
2017-07-05 14:28:57vstinnersetrecipients: + vstinner, belopolsky, ned.deily, serhiy.storchaka, musically_ut
2017-07-05 14:28:57vstinnerlinkissue30822 messages
2017-07-05 14:28:57vstinnercreate