BIND 10 #1845: SQLite3Update.rollbackFailure test fails

[BIND 10 Development]

#1845: SQLite3Update.rollbackFailure test fails
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  vorner                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 It appears to be due to a behavior change in SQLite3 3.7.11:
 http://sqlite.org/releaselog/3_7_11.html

   Pending statements no longer block ROLLBACK. Instead, the pending
   statement will return SQLITE_ABORT upon next access after the
   ROLLBACK.

 The change itself seems to be reasonable as ROLLBACK shouldn't easily
 fail.  But unless it ensures it never fails (which is not clear from
 the SQLite3 doc) it's better to have a test case for that.  And, as a
 matter of fact, we are also using older versions of SQLite3 where
 ROLLBACK would fail due to a pending statement.

 My suggestion is:

 - Try to find another reliable way to make ROLLBACK fail and use it in
   this test.
 - If it's not possible or is very difficult, enable this test only
   for older versions of SQLite3 (<= 3.7.10).

-- 
Ticket URL: <http://bind10.isc.org/ticket/1845#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development