#7715: admin_tests failures when running Django tests in one natural fashion
---------------------------------------+------------------------------------
Reporter: mtredinnick | Owner: nobody
Status: new | Milestone:
Component: Unit test system | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not seeing this problem myself, but I can't say I can identify an
obvious PEBCAK issue, either.
I have a Django checkout of [7882] in /Users/rkm/svn/django/trunk,
symlinked to /Users/rkm/svn/django/live. The 'live' directory is in my
PYTHONPATH. Using Python 2.5, and sqlite, I get no test failures. If I
clear my PYTHONPATH and use a symlink from my SVN checkout into site-
packages, I don't get failures, either. I don't know Karen Tracey's exact
setup, but she reported no failures under Ubuntu or Windows.
The buildbots aren't reporting completely clean, but those failures have
different causes:
* Sqlite, Python2.5 appears to have an intermittent caching issue with
templates
* Sqlite, Python2.4 One platform doesn't have write permission for *.pyc
files, so a test condition fails when looking for pyc files.
Postgres on Python 2.5 is building fine.
Some questions to help narrow this down:
* Which 11 tests are failing?
* Are the stack traces you are reporting coming from the test runner, or
from the embedded manage.py/django-admin execution?
* Can you provide any more depth in the stack trace than the one line of
ImportError?
* Are you seeing these failures as the usual ERROR case on test output,
or is the test runner getting interrupted?
* Does the order of test execution matter? Do you see the failures if you
run the whole suite, or just when you run the admin_scripts tests? If you
run other tests before/after admin_scripts, do you still see failures?
(The reason I ask this one is that [7877] was to fix a problem that was
test order dependent. I think I've fixed all the ordering problems, but I
could still be missing one)
--
Ticket URL: <http://code.djangoproject.com/ticket/7715#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
