Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27525

collation.js should use test-specific database

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.2, 3.5.2
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
    • Fully Compatible
    • ALL
    • v3.4
    • Query 2017-01-23
    • 0

      As part of collation testing, core/collation.js will convert a non-capped collection to one that is capped via "convertToCapped" command, confirming that the default collation of the original collection is preserved.

      As part of the capped conversion, mongod will confirm that there are no background operations occurring via assertNoBgOpInProgForDb() call, asserting if there is a conflict.

      collation.js uses the "test" database for its operations. As we run collation.js as part of the parallel suite, this raises the possibility that the assertNoBgOpInProgForDb() will fail due active background index build on the same database by another test. We should consider changing collation.js to use a test-specific database to avoid potential conflict.

            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            james.wahlin@mongodb.com James Wahlin
            0 Vote for this issue
            3 Start watching this issue