Data mismatch detected in agg_match.js test

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines 2020-03-23
    • 5

      The agg_match.js test in MongoDB is reporting that the amount of data returned doesn't match expectations:

      [jsTest] ----
[jsTest] Workload(s) completed in 18717 ms: jstests/concurrency/fsm_workloads/agg_match.js
 [jsTest] ----

Error: 1 thread with tids [1] threw

        Foreground jstests/concurrency/fsm_workloads/agg_match.js
        Error: [500] != [346] are not equal

        quietlyDoAssert@jstests/concurrency/fsm_libs/assert.js:55:18
        assert.eq@src/mongo/shell/assert.js:179:9
        wrapAssertFn@jstests/concurrency/fsm_libs/assert.js:65:13
        assertWithLevel/</assertWithLevel[fn]@jstests/concurrency/fsm_libs/assert.js:104:13
        query@jstests/concurrency/fsm_workloads/agg_match.js:24:9
        runFSM@jstests/concurrency/fsm_libs/fsm.js:80:17
        @eval:8:9
       main@jstests/concurrency/fsm_libs/worker_thread.js:222:17
        @eval:5:12
         @eval:3:24
        _threadStartWrapper@:26:16

      The command to re-run the test suite is:

      buildscripts/resmoke.py --suites=concurrency_replication_causal_consistency --storageEngine=wiredTiger --continueOnFailure --installDir=dist-test/bin --jobs=1 --mongodSetParameters={enableIndexBuildCommitQuorum: false} --shuffleMode=on --storageEngineCacheSizeGB=1

        1. oplog_based_total_inserts.log
          7 kB

            Assignee:
            Michael Cahill (Inactive)
            Reporter:
            Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: