Thank you Michal, I was not aware of this issue. I fixed it and committed again - https://github.com/speedy-net/speedy-net/commit/6570e00edb9d58c8d855f8b7ea6a8129c774eb33. Thanks for your help!
Thanks, אורי (Uri) u...@speedy.net On Wed, Jan 16, 2019 at 11:39 AM Michal Petrucha < michal.petru...@koniiiik.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On Wed, Jan 16, 2019 at 09:11:47AM +0200, אורי wrote: > > Hi, > > > > I recently have problems with testing my project on Travis CI. Tests > > started to fail 2 days ago. The error message is > > `psycopg2.OperationalError: FATAL: database "speedy" does not exist` > and I > > don't know why. It seems to me that the first test which fail for this > > reason is https://travis-ci.org/speedy-net/speedy-net/builds/479248003 > and > > the commit is > > > https://github.com/speedy-net/speedy-net/commit/04c4c891f64c4eee3accc393e59b5d18f0c8bbcc > , > > but I don't know what in this commit causes the tests to fail. When I run > > the tests locally they run without problems. Do you know why our tests > fail > > on Travis CI? > > Hi Uri, > > The problem is the following line: > > https://github.com/speedy-net/speedy-net/commit/04c4c891f64c4eee3accc393e59b5d18f0c8bbcc#diff-c1494957b796412b658b8c2c97136711R6 > That line tries to execute a database query during import, which will > not work – you don't want to make import-time queries, because those > will be routed to the production database even when you're running > tests, and they will also make it impossible for you to run migrations > in a fresh, empty database. > > Good luck, > > Michal > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQIcBAEBCgAGBQJcPvvRAAoJEHA7T/IPM/kl4gsP/j2Pyl8YQsUi94saQFnIaEIH > sxQ28wm4a5vlfAyKxDDNZqcBBwVq0YPkpflEe5DnmFjQdcsanjZgxt+ejwwONmFF > +kP7gjD1mPmGG4V2XT5MllzI0VR5clZiP7leXgnQq+Xgtb0+xdfQHjZMm8JszhVe > oWbCgRlBNOXDPhnSS5mu5rh//zbBGaOQHjN6vcmmT+M7OQcjDD4nmsEnz3fY3b5J > mh3Y/X8h0dzCao0cAul7m8Pynu/xDl5THQS9dI4YIEOrzdQBkjNZMonNr0rK7e5o > 49MbfHOGRmDNdF53w2AfKe+9FN/I+C9WXR6XQNE2858aveGM0o+hw+P+1RhNUPBF > /oov5rDu0vmyLDd2ip3lHZ0ki12mkMKYMZQ6Yfit4X1nLaob/6oQ4KkMCzawrIWS > CekjFC2HQY6SJJRpS0VGjft5qlRvEgO9isn+THoNDIEZDJj1XT07RJldA+6/g1Jy > POeneUyxa7j1F3gcW86lazCfavLO7LhPnAcWKjntc9j5Xq5/l0TyJcORV6yJFMSu > Wgh3YrqjIZcOMkX+YiJ0pr5iqkZ3M/hieLALuaM13iYbx1NtL+k34rx76ROz8sw4 > BpAO/oUMJnDS+2yT/G2FmTdhJisznTjsqgwfyDSAdlMSpADjxNj62ykojgCTjhpB > J6DfyIn1PH3LaTeWK4bi > =zAwN > -----END PGP SIGNATURE----- > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/20190116093929.GZ8269%40koniiiik.org > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABD5YeGsY6Fk0DooCVYXbbg9knL4wn7Y2Y%3D2y_Gitm5-sFrbVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
