On Mon, Aug 19, 2013 at 4:13 PM, VernonCole <[email protected]> wrote:
> Kris: > 9 failures and 17 errors are not an unusual number (out of 556 tests) > given the complexity of django and the number of platforms it works on. > The number and selection of failed tests will vary depending on the exact > implementation you are running. However, I notice that _none_ of the errors > your are seeing are in core django -- all are in either django.contrib or > another package. Also -- you are not running a development (or indeed, > even a current) version of django, so the errors you have seen have very > possibly been fixed in the latest version(s). > Given that "The project I'm working on seems to work fine" I would say > that there is no cause for concern. If you wish to help test and/or debug > django, you should do so using the latest version. > Wow… that's… a concerning opinion. A test failure is a problem - period. There's no safe level of test failures. Django's test suite should not have *any* failures in it. A repeatable test failure in Django's suite is considered a release blocking bug. If you're happy to live with "The app seems to work fine", why bother having a test suite in the first place. The purpose of at test suite is to draw your attention to the myriad ways that your app may *not* be fine. It's difficult to establish exactly what has caused these errors without seeing all the code, but the errors you're getting point to something fairly fundamental going wrong. Failures caused by tables not being created are a fairly fundamental failure. The way your UserCreationForm is failing is also suspicious. Two possibilities that spring to mind: * You don't *actually* have Django 1.4.3 -- you may have a corrupted half install of two different versions (possibly by installing one version over another in an unusual way) * There's something in the rest of your stack that is messing with Django's internals. The first step -- try to run Django's own test suite. This should pass without any errors. Second step -- run the test suite on a clean project (i.e., no extra apps installed). This should also pass without errors. Then, you can progressively start introducing new components until you either have a full app with a fully passing test suite, or you can identify the component that is causing problems. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
