Re: [Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2014-12-01 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"1f98ec2e53e4636863396ab54f671f4546f9ba4c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1f98ec2e53e4636863396ab54f671f4546f9ba4c"
 Fixed #23929 -- Added more tests for create_default_site.

 Refs: #15346, #15573, #16353, #16828.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e6ee4071b54dc3337b64a84082d68048%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2011-09-13 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
--+---
   Reporter:  aaugustin   |  Owner:  nobody
   Type:  Bug | Status:  closed
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   Severity:  Release blocker
 Resolution:  duplicate   |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  1
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Yeah, I think I just managed to report the same bug twice... and write
 exactly the same patch... *goes grab a coffee*.

 For the record, this problem was introduced in r16027 (trunk) and r16028
 (1.3.X).

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2011-09-13 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
--+---
   Reporter:  aaugustin   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   Severity:  Release blocker
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  1
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by julien):

 Or maybe is it a bug in trunk that has also been introduced in the 1.3.1
 release?

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2011-09-13 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
--+---
   Reporter:  aaugustin   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   Severity:  Release blocker
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  1
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by julien):

 Isn't this a duplicate of #16353?

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2011-09-13 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
--+---
   Reporter:  aaugustin   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   Severity:  Release blocker
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  1
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by aaugustin):

 This bug also exists on trunk.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2011-09-13 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
--+---
   Reporter:  aaugustin   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   Severity:  Release blocker
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  1
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by aaugustin):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases

2011-09-13 Thread Django 
#16828: Upgrade from 1.3 to 1.3.1 breaks manage.py test with multiple databases
---+-
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Milestone: |Component:  Testing framework
  Version:  1.3| Severity:  Release blocker
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
 To reproduce this problem:

 * `django-admin.py startproject regrtest && cd regrtest`
 * create a file called `routers.py` with this content (this is a dummy
 router that puts everything in the "default" database):
 {{{
 class TestRouter(object):

 def db_for_read(self, model, **hints):
 return 'default'

 def db_for_write(self, model, **hints):
 return 'default'

 def allow_relation(self, obj1, obj2, **hints):
 return True

 def allow_syncdb(self, db, model):
 return db == 'default'
 }}}
 * in `settings.py`, replace the default value of `DATABASES` with this
 content:
 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'default.sqlite3',
 },
 'other': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'other.sqlite3',
 },
 }

 DATABASE_ROUTERS = ['routers.TestRouter']
 }}}
 * `python manage.py test auth` works under 1.3 but not under 1.3.1:
 {{{

 aaugustin@aaugustin regrtest % . ../dj13_venv/bin/activate
 (dj13_venv)aaugustin@aaugustin regrtest % python manage.py test auth
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 
..
 --
 Ran 98 tests in 1.745s

 OK
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 (dj13_venv)aaugustin@aaugustin regrtest % . ../dj131_venv/bin/activate
 (dj131_venv)aaugustin@aaugustin regrtest % python manage.py test auth
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 Traceback (most recent call last):
   File "manage.py", line 14, in 
 execute_manager(settings)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/core/management/__init__.py", line 438, in execute_manager
 utility.execute()
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/core/management/__init__.py", line 379, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/core/management/base.py", line 191, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/core/management/base.py", line 220, in execute
 output = self.handle(*args, **options)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/core/management/commands/test.py", line 37, in handle
 failures = test_runner.run_tests(test_labels)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/test/simple.py", line 359, in run_tests
 old_config = self.setup_databases()
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/test/simple.py", line 296, in setup_databases
 test_db_name = connection.creation.create_test_db(self.verbosity,
 autoclobber=not self.interactive)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/db/backends/creation.py", line 384, in create_test_db
 if Site is not None and
 Site.objects.using(self.connection.alias).count() == 1:
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/db/models/query.py", line 334, in count
 return self.query.get_count(using=self.db)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/db/models/sql/query.py", line 401, in get_count
 number = obj.get_aggregation(using=using)[None]
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/db/models/sql/query.py", line 367, in get_aggregation
 result = query.get_compiler(using).execute_sql(SINGLE)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-
 packages/django/db/models/sql/compiler.py", line 735, in execute_sql
 cursor.execute(sql, params)
   File "/Users/aaugustin/Documents/dev/dj131_venv/lib/python2.6/site-