[Python-Dev] freeze build slave (original) (raw)
Victor Stinner victor.stinner at gmail.com
Mon Mar 31 08:11:32 CEST 2014
- Previous message: [Python-Dev] freeze build slave
- Next message: [Python-Dev] Treating tokenize.Untokenizer as private
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I disagree. Running tests in debug code tests more things thanks to assertions, and provides more info in case of test failure or crash. Some assertions only fail on some platforms. See for example test_locale which fails with an assertion error on solaris (since Python 3.3).
Adding one or two slaves should not hurt. You need maybe at least one on Windows and another on OS X.
Victor
Le dimanche 30 mars 2014, Stefan Krah <stefan at bytereef.org> a écrit :
"Martin v. L?wis" <martin at v.loewis.de javascript:;> wrote: > C: pro: compared to B, build time is reduced (need only > to build once per branch); disk space is also reduced > con: it would test a debug build, not a release build
It would be an option to run half of the Unix slaves (especially the ones with the more aggressive compilers) in release mode. I think that is beneficial anyway.
Stefan Krah
Python-Dev mailing list Python-Dev at python.org javascript:; https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140331/9bc312d0/attachment.html>
- Previous message: [Python-Dev] freeze build slave
- Next message: [Python-Dev] Treating tokenize.Untokenizer as private
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]