Potentially randomly failing tests on low performance machines due to unreliable multiprocessing. Though these issues seem to primarily manifest when doing bad things (leaking tests) our running in parallel mode with more processes than cores.
I had to give up trying to get the internal tests to pass on Travis. On 3.4 and higher I can explicitly use the spawn strategy in multiprocessing which has slightly higher overhead but is more reliable. On lower versions you cannot choose the strategy, python picks it based on the os. As long as you use --vanilla on Travis you're safe, and on Travis you can't use any of the advanced features anyway, so using that flag makes sense. 2016年9月2日金曜日、czpython<[email protected]>さんは書きました: > Hey Jonas, > > Thanks for the update. > Just to clarify, when you say "unstable", do you mean random failing > tests? or just unsupported versions? > > On Friday, September 2, 2016 at 4:45:47 AM UTC-4, Jonas Obrist wrote: >> >> Managed to get the tests to work reliably (on Py 3.4 and higher). See >> https://github.com/ojii/django-better-test/pull/9 >> >> But had to remove Django 1.6 support (don't think too many people will >> get upset about this) and Py 2.7/3.3 are now "unstable". Without going to >> great lengths, I don't think I can fix that and I don't want to was too >> much time on ancient Python versions... >> >> Iacopo, do you think this is good enough? Did you see issues in django >> CMS tests (py2) with tests being "unstable" (in the current version)? >> >> Jonas >> >> On Tuesday, August 30, 2016 at 11:14:15 AM UTC+9, Jonas Obrist wrote: >>> >>> Hi everyone, >>> >>> Over the weekend at PyCon Malaysia I've updated django-classy-tags and >>> django-sekizai to 0.8.0 and 0.10.0 respectively. >>> >>> Both releases only changed Python/Django compatibility. >>> >>> Both now support: >>> >>> - Python 2.7, 3.3, 3.4 and 3.5 (dropped 2.6) >>> - Django 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10 (Added 1.10) >>> >>> Hopefully this doesn't break everything (as it tends to do :D). >>> >>> I also tried to update django-better-test to 1.10 (and I got it to >>> support it), but travis-ci is being uncooperative so I had to delay the >>> release. >>> >>> Jonas >>> >> -- > Message URL: https://groups.google.com/d/msg/django-cms-developers/ > topic-id/message-id > Unsubscribe: send a message to django-cms-developers+ > [email protected] > <javascript:_e(%7B%7D,'cvml','django-cms-developers%[email protected]');> > --- > You received this message because you are subscribed to the Google Groups > "django CMS developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <javascript:_e(%7B%7D,'cvml','django-cms-developers%[email protected]');> > . > To view this discussion on the web, visit https://groups.google.com/d/ > msgid/django-cms-developers/b5139003-fadf-4018-bd17- > ae444736a0cb%40googlegroups.com > <https://groups.google.com/d/msgid/django-cms-developers/b5139003-fadf-4018-bd17-ae444736a0cb%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/CAMS%3DEL1V7vLaRmHxw27fqd79aWsVt__Gh8MkcKVnFEkGumV2TA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
