Update: I am able to "reproduce" the test issues on my under-powered macbook air when simultaneously compiling some stuff (thus pegging the CPU at 100% usage). It's still non-deterministic and really odd, but at least I now sometimes get failing tests locally. The funny thing: It loses results (sub-tests aren't failing/succeeding unexpectedly, their result simply vanishes...).
Should anyone have ideas as to why high CPU usage breaks it, I'd love to hear it. 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 [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/0d65d1d8-0098-4299-880a-81bba107e83b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
