Re: [Django] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-10-09 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
 Reporter:  jsdalton |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by loewis):

 In [16950]:
 {{{
 #!CommitTicketReference repository="" revision="16950"
 Merged revisions
 
16743,16745,16747-16750,16752-16754,16756-16760,16770,16773-16800,16802-16804,16806,16808,16811,16813,16815,16817-16826,16829-16833,16835-16836,16838-16843,16845-16858,16860-16866,16868,16871-16877,16882-16890,16893-16947
 via svnmerge from
 https://code.djangoproject.com/svn/django/trunk

 
   r16743 | gabrielhurley | 2011-09-09 23:36:58 +0200 (Fr, 09 Sep 2011) | 2
 lines

   Fixed #16791 -- Updated a broken URL in the README file. Thanks to
 paulcwatts for the report and patch.
 
   r16745 | Alex | 2011-09-09 23:45:58 +0200 (Fr, 09 Sep 2011) | 1 line

   Switch to using explicit new-style division behavior, rather than
 relying on teh classic behavior.
 
   r16747 | SmileyChris | 2011-09-10 00:32:38 +0200 (Sa, 10 Sep 2011) | 1
 line

   Fix and test for cleaning a non-string value in a URLField
 
   r16748 | gabrielhurley | 2011-09-10 00:33:28 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #16786 -- Minor cleanups in the memcached section of the caching
 topic guide. Thanks to jamesp for the report and patch.
 
   r16749 | jbronn | 2011-09-10 00:34:23 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16408 -- Fixed conversion of dates, and other problems with the
 SpatiaLite backend.
 
   r16750 | jbronn | 2011-09-10 00:47:18 +0200 (Sa, 10 Sep 2011) | 1 line

   Removed extra call to `syncdb` that slipped in with r16749.
 
   r16752 | SmileyChris | 2011-09-10 00:57:12 +0200 (Sa, 10 Sep 2011) | 1
 line

   Fixes #16664 -- URLField's to_python method fails with ValueError on
 some urls on python 2.7. Based on patch by zigzag.
 
   r16753 | russellm | 2011-09-10 01:02:33 +0200 (Sa, 10 Sep 2011) | 1 line

   Added two pointless query repeats to work around a known issue with
 MySQL that was causing failures in our test suite.
 
   r16754 | gabrielhurley | 2011-09-10 01:25:48 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #16782 -- Corrected a broken cross-reference to the database
 engine setting in the tutorial. Thanks to mjumbewu for the report and
 patch.
 
   r16756 | kmtracey | 2011-09-10 02:05:48 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #15722: ensure formsets evaluate to True even if they have no
 forms. Thanks mlavin.
 
   r16757 | jbronn | 2011-09-10 02:29:34 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #13670 -- Comparisons with the spatial adapter won't blow up in
 some corner cases.  Thanks, milosu for the bug report and jpaulett for the
 patch.
 
   r16758 | russellm | 2011-09-10 02:46:38 +0200 (Sa, 10 Sep 2011) | 1 line

   Added protection against spoofing of X_FORWARDED_HOST headers. A
 security announcement will be made shortly.
 
   r16759 | russellm | 2011-09-10 02:46:48 +0200 (Sa, 10 Sep 2011) | 1 line

   Corrected an issue which could allow attackers to manipulate session
 data using the cache. A security announcement will be made shortly.
 
   r16760 | russellm | 2011-09-10 02:47:00 +0200 (Sa, 10 Sep 2011) | 1 line

   Altered the behavior of URLField to avoid a potential DOS vector, and to
 avoid potential leakage of local filesystem data. A security announcement
 will be made shortly.
 
   r16770 | Alex | 2011-09-10 03:53:56 +0200 (Sa, 10 Sep 2011) | 1 line

   Make ``Formset.__getitem__`` O(1), rather than O(n).  If you override
 ``__iter__`` you now need to also override ``__getitem__`` for consistant
 behavior.  Thanks to Carl and Russ for the review.
 
   r16773 | Alex | 2011-09-10 04:42:05 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #11404.  Added ``FormSet.has_changed``, for consistancy with
 ``Form.has_changed``. Thanks to michelts for the patch.
 
   r16774 | Alex | 2011-09-10 04:52:37 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16793. Added more cross referencing to the load tag's
 documentation.  Thanks to bluejeansummer for the patch.
 
   r16775 | jbronn | 2011-09-10 05:04:30 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16790 --

Re: [Django] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-09-10 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Normal
 Resolution:  fixed  |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by russellm):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [16784]:
 {{{
 #!CommitTicketReference repository="" revision="16784"
 Fixed #16490 -- Skipped a test failure that only occurs under Python 2.6.1
 (it's the old iteration-eats-exceptions problem).
 }}}

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-09-10 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by russellm):

 For the record, the Python bug is http://bugs.python.org/issue1242657

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-09-10 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by russellm):

 I've worked out the cause of the other problem -- it's the old "Python
 2.6.1 eats exceptions" problem. The DatabaseError raised when NOWAIT isn't
 available is eaten by the iteration process in execute_sql. This only
 affects Python 2.6.1; our approach on other instances of this problem has
 been to skip the test, rather than try and work around a bug that exists
 in one version of Python.

 A fix will be landing shortly.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-09-10 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by russellm):

 In [16781]:
 {{{
 #!CommitTicketReference repository="" revision="16781"
 Refs #16490 - Add a commit to ensure that a fresh read is provided; this
 is only a problem for databases in REPEATABLE READ mode, which is MySQL
 InnoDB's default. Thanks to Jim Dalton for the report and patch.
 }}}

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-09-09 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by adamnelson):

 * stage:  Accepted => Ready for checkin


Comment:

 patch applies and test does not fail for me on Lion with MySQL 5.5.14

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-08-17 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
+---
   Reporter:  jsdalton  |  Owner:  nobody
   Type:  Bug   | Status:  reopened
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+---
Changes (by ramiro):

 * component:  Database layer (models, ORM) => Testing framework


-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-08-15 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  1
-+-
Changes (by jsdalton):

 * status:  closed => reopened
 * has_patch:  0 => 1
 * resolution:  duplicate =>
 * easy:  0 => 1


Comment:

 After doing some investigation on #13906, I've come to the conclusion that
 this issue does not need to wait for a decision about REPEATABLE READ to
 be made in order to be addressed. A simple `transaction.commit()` in the
 `test_block()` method before the final select will ensure that MySQL
 performs a fresh read. The test runs cleanly now on all backends with no
 side effects from the commit (since no data is actually being inserted or
 updated on this connection). Note that `transaction.rollback()` would also
 have the same effect, but in my opinion that makes the test a bit more
 confusing to the casual observer, since it makes it look like we're
 rolling back the work we just did.

 Patch attached, this should be an easy one.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-08-06 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution:  duplicate  |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by kmtracey):

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


Comment:

 The first failure is due to repeatable read, see #13906. The 2nd failure I
 can't recreate either. I'm going to close this one as a dupe of #13906; we
 should figure out what to do about the repeatable read issue and that will
 either fix the first failure or involve "fixing" this test to avoid the
 problem. If anyone else sees the `test_unsupported_nowait_raises_error`
 failure we can reopen this one to address that here.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-07-21 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by jsdalton):

 Well, hm. I upgraded to Lion last night which may have changed my MySQL
 version, so I no longer can replicate the conditions under which the
 original report occurred. I do know that I was running it under an up-to-
 date master branch.

 Regardless, I can no longer replicate the NO WAIT error, but I do get the
 other one `test_block()`  still. I'm happy about that because I was
 absolutely confounded by that other error, so now I can chalk it up to a
 fluke :).

 So, yes, one test failure now, and this is running Python 2.6.6, MySQL
 5.1.40, InnoDB.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-07-21 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by ramiro):

 I see the first error
 (`modeltests.select_for_update.tests.SelectForUpdateTests.test_block`)
 when running tests with a pristine checkout of trunk against MySQL 5.1.58
 so this doesn't seem to be introduced by your patch for #11665. Graham
 King tells us he doesn't see it with Maybe tehre is some change of
 behavior in MySQL betwen 5.1.54 and 5.1.58? What version are you using?

 But I don't see the second one
 
(`modeltests.select_for_update.tests.SelectForUpdateTests.test_unsupported_nowait_raises_error`),
 this is strange because the !SelectForUpdateTests tests
 
[https://code.djangoproject.com/browser/django/trunk/tests/modeltests/select_for_update/tests.py#L21
 inherits] from !TransactionTestCase and in theory shoudn't be affected by
 your changes to !TestCase handling of transactions in #11665.

 I tried with both Python 2.6 and 2.7, MySQL storage backend is InnoDB.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-07-20 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-07-19 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage: |   Keywords:
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by jsdalton):

 * cc: jim.dalton@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

2011-07-19 Thread Django 
#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
--+--
 Reporter:  jsdalton  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Database layer (models, ORM)
  Version:  SVN   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+--
 The following test fails on MySQL InnoDB. This appears to relate to the
 work recently done on #2705.

 {{{
 $ ./runtests.py --settings=testproject.settings
 select_for_update.SelectForUpdateTests
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 F.s...F
 ==
 FAIL: test_block (modeltests.select_for_update.tests.SelectForUpdateTests)
 --
 Traceback (most recent call last):
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/modeltests/select_for_update/tests.py",
 line 209, in test_block
 self.assertEqual('Fred', p.name)
 AssertionError: 'Fred' != u'Reinhardt'

 ==
 FAIL: test_unsupported_nowait_raises_error
 (modeltests.select_for_update.tests.SelectForUpdateTests)
 --
 Traceback (most recent call last):
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/test/testcases.py",
 line 615, in skip_wrapper
 return test_func(*args, **kwargs)
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/modeltests/select_for_update/tests.py",
 line 138, in test_unsupported_nowait_raises_error
 Person.objects.all().select_for_update(nowait=True)
 AssertionError: DatabaseError not raised

 --
 Ran 7 tests in 10.342s

 FAILED (failures=2, skipped=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...

 }}}


 The DatabaseError is not being raised because -- well, I wish I knew. The
 code block is being executed but the error is being caught, i.e. I can
 print to stdout but any exception is not being raised. The thread related
 error is also something I'm unclear on.

 As part of the work I am doing right now on #11665, these two issues are
 the *only* remaining failures in the MySQL test suite. Seriously, the only
 remaining failures. Given that this feature seems to be quite new, I'm
 hopeful that it's fresh on everyone's minds and easy enough to address,
 perhaps by the folks who worked so hard on #2705. If I can be of any
 assistance, let me know.

-- 
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.