On Fri, Apr 16, 2010 at 11:00 PM, Tom X. Tobin <tomxto...@tomxtobin.com>wrote:
> [snip details of run times]
>
> Sticking out like a sore thumb is API_TESTS under
> modeltests.fixtures.models.__test__, which clocks in at 1090
> seconds(!). The serializer tests also seem to take a pretty chunk of
> time at about 1-3 minutes each. I run the test suite fairly regularly
> (since we merge from upstream aggressively), and the total run time
> recently jumped from about 20 minutes to around an hour. Any ideas as
> to why these tests are taking so long?
>
>
The ones that are sticking out like sore thumbs have always been sticking
out like sore thumbs (on my slow machines). Whenever I glance at a test run
to see how it's going it's almost invariably "stalled" on one of those you
mention. And I know why. There are 10 of these:
>>> management.call_command('flush', verbosity=0, interactive=False)
for example, in modeltests/fixtures/models.py. That's a full re-build of the
entire test database. Many if not all of the others cited above have at
least one of those calls.
These are not new, so the question is why are you suddenly noticing them?
Did some recent change make re-syncing the DB even more expensive than it
used to be? Or has the number of test apps and model tables just been
growing, growing, growing slowly and now it's noticeably slower? You
mention, though, a recent jump from 20 minutes to an hour -- specifics on
what changeset(s), exactly, caused that dramatic difference in time might
give a clue.
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-develop...@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.
