Uploaded image for project: 'Couchbase Lite'
  1. Couchbase Lite
  2. CBL-343

LiteCore tests need to use unique database

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.7.0
    • 2.7.0
    • LiteCore
    • Security Level: Public
    • None
    • CBL Sprint 3
    • 5

    Description

      >>> Push 5000 Changes
      22:17:29.202855| [SQL] ERROR: database is locked (5/5)
      22:17:29.203010| [SQL] ERROR: database is locked (5/5)
      22:17:29.203136| [Sync] WARNING: {Repl#842} Couldn't get remote-DB ID for target <ws://srv/>: error 1/16
      22:17:29.203241| [Sync] ERROR: {Repl#842} Got LiteCore error: LiteCore error 16 "database is locked"
      FATAL: Assertion failed: _gotResponse (/Users/mobile/jenkins/mobile/workspace/eline_couchbase-lite-core_PR-830/couchbase-lite-core/Replicator/tests/ReplicatorLoopbackTest.hh:176, in replicatorStatusChanged)
      

      As seen in the above, this can happen easily if two PRs are being validated at once since they use a hardcoded path to a database. They will both operate on the same database, and thus cause chaos to each other.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          There are no comments yet on this issue.

          People

            jimb Jim Borden
            jimb Jim Borden
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty