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

bench_test_crud_commands.js attempts to perform journaled writes against a mongod without journaling enabled

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: 3.3.10
    • Component/s: Write Ops
    • None
    • Fully Compatible
    • ALL
    • Hide
      python buildscripts/resmoke.py --executor=no_passthrough_with_mongod jstests/noPassthroughWithMongod/bench_test_crud_commands.js --nojournal
      
      Output
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 2016-08-06T22:15:11.580-0400 E QUERY    [thread1] Error: 0 is not greater than 0 : undefined :
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 doassert@src/mongo/shell/assert.js:15:14
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 assert.gt@src/mongo/shell/assert.js:314:5
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 testInsert@jstests/noPassthroughWithMongod/bench_test_crud_commands.js:43:1
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 testWriteConcern@jstests/noPassthroughWithMongod/bench_test_crud_commands.js:85:9
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 @jstests/noPassthroughWithMongod/bench_test_crud_commands.js:89:5
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.583-0400 @jstests/noPassthroughWithMongod/bench_test_crud_commands.js:2:2
      [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.583-0400 failed to load: jstests/noPassthroughWithMongod/bench_test_crud_commands.js
      
      Show
      python buildscripts/resmoke.py --executor=no_passthrough_with_mongod jstests/noPassthroughWithMongod/bench_test_crud_commands.js --nojournal Output [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 2016-08-06T22:15:11.580-0400 E QUERY [thread1] Error: 0 is not greater than 0 : undefined : [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 doassert@src/mongo/shell/assert.js:15:14 [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 assert.gt@src/mongo/shell/assert.js:314:5 [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 testInsert@jstests/noPassthroughWithMongod/bench_test_crud_commands.js:43:1 [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 testWriteConcern@jstests/noPassthroughWithMongod/bench_test_crud_commands.js:85:9 [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.582-0400 @jstests/noPassthroughWithMongod/bench_test_crud_commands.js:89:5 [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.583-0400 @jstests/noPassthroughWithMongod/bench_test_crud_commands.js:2:2 [js_test:bench_test_crud_commands] 2016-08-06T22:15:11.583-0400 failed to load: jstests/noPassthroughWithMongod/bench_test_crud_commands.js
    • Query 2016-08-29
    • 0

      The write concern specified in the different test cases of bench_test_crud_commands.js were fixed as part of SERVER-25035. The test consistently fails when run against a mongod started with --nojournal, --storageEngine=ephemeralForTest, or --storageEngine=inMemory now that the intended write concern is being respected because none of the j=true inserts will succeed.

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: