On Fri, Jan 16, 2009 at 9:43 AM, Alex Gaynor <alex.gay...@gmail.com> wrote:
> PgSQL is indeed PostgreSQL. Yes, I do still get the failures pre-fast > tests, I guess I'd never run those tests. I would like to say that when I > went back to test that the tests were unbearably slow, so that makes me > super happy about the new fast tests, thanks for all your hard work. > Yeah, one consequence of the new faster tests may be people start running the full suite more often and notice lurking errors that have been out there but just unseen. The machines where I have Oracle and PostgreSQL set up are old and slow and took 8+ hours to run the full Django suite prior to these changes, meaning I would really never run the full suite for those backends. Now I can run them in an hour or so -- still not real speedy but it's at least feasible to run the full suite. Sadly, only a few of my test setups pass completely clean. I see the errors you pointed out on PostgreSQL, others related to referential integrity & fixtures on InnoDB, some Windows temp file problems, some sqlite problems related to a specific sqlite/Python level, some Oracle errors that I think are something wrong in my DB setup, etc. On my wish list is getting some of these resolved, but I haven't had time to focus on that yet. What I did for the rollback test changes was manually verify that any errors/failures I saw with the changes were identical to what I saw without them. I do think all the problems I see (with the exception of the Oracle ones which I suspect are database setup related, but I've not had a chance to investigate much there) are either known with open tickets or known unfixable (e.g. sqlite bug for a specific version). It might be nice if we had a way to flag such things as "expected to fail (at the moment, in this configuration)" so that it's easier to run the full suite on a wide range of configurations and get a quick confirmation from the output that the results are as expected, even if there are known failures in some cases at the moment. I think I've seen this idea discussed before...but again I haven't had much time to look into it yet. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
