For the lock wait timeout errors, it's probable something (another test run?) is still connected to the database and holding the locks. Try restarting mysql.
And if you are still having problems, knowing the version of MySQL you're using, plus how you installed it, would be helpful. On 10 March 2017 at 22:14, Tim Graham <[email protected]> wrote: > For the error, "Database returned an invalid datetime value. Are time zone > definitions for your database installed?", see https://docs.djangoproject. > com/en/dev/ref/databases/#time-zone-definitions. > > Adding this to the 'default' and 'other' dictionaries in DATABASES may > solve some of the encoding problems: > > 'TEST': { > 'CHARSET': 'utf8', > 'COLLATION': 'utf8_general_ci', > }, > > If you still have some errors after that, please post an updated output. > > On Friday, March 10, 2017 at 5:03:51 PM UTC-5, Anton Samarchyan wrote: >> >> I have a pull request in which some tests for some of environments are >> failing. (it's fine for the default tests with sqlite and some others) - >> https://github.com/django/django/pull/7994 >> >> Now, I am trying to run the tests with the database set to mysql. >> >> I added a file settings_mysql.py which I put in the tests folder: >> http://pastebin.com/113Xx2Am >> >> To try it out I use the master branch (commit >> c577d8a4981233b4d0f65c6ce57ae33d304095b9). >> >> Then I run ./runtests.py --settings settings_mysql and I am getting >> errors. >> >> Then I rerun it with parallel=1 - ./runtests.py --settings settings_mysql >> --parallel=1 >> >> and I get the following result: >> >> FAILED (failures=56, errors=42, skipped=1046, expected failures=4) >> >> Full log - https://paste.ee/p/Tfc9H >> >> Does anyone have an idea what might be wrong and what is the best way to >> run tests for different databases? >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/6f86afff-c4c1-481e-8e17- > 7aae2cf0bde7%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/6f86afff-c4c1-481e-8e17-7aae2cf0bde7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Adam -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1KNVFfJhBO-AbPH15se0TosZe%2BhygeRneTEv%3D0yKuJAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
