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

range_deleter_test:ImmediateDelete is flaky

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.3, 3.3.0
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding E (01/08/16)

      Description

      	
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:32.363+0000 Program build/opt/mongo/db/range_deleter_test started with pid 9396.
      2015-12-16 17:28:34 +0000	
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:34.572+0000 2015-12-16T17:28:34.571+0000 I -        [main] going to run suite: ImmediateDelete
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:34.572+0000 2015-12-16T17:28:34.571+0000 I -        [main] 	 going to run test: ShouldWaitCursor
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:34.572+0000 2015-12-16T17:28:34.572+0000 I SHARDING [thread1] waiting for open cursors before removing range [{ x: 0 }, { x: 10 }) in test.user, cursor ids: []
      2015-12-16 17:28:36 +0000	
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:36.681+0000 2015-12-16T17:28:36.681+0000 I SHARDING [RangeDeleter] stopping range deleter worker
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:37.566+0000 2015-12-16T17:28:37.565+0000 I -        [main] FAIL: ShouldWaitCursor	Expected: stdx::future_status::ready == deleterFuture.wait_for(stdx::chrono::seconds(MAX_IMMEDIATE_DELETE_WAIT_SECS)) @src/mongo/db/range_deleter_test.cpp:204
      [cpp_unit_test:range_deleter_test] 2015-12-16T17:28:37.566+0000 2015-12-16T17:28:37.565+0000 I -        [main] 	 going to run test: StopWhileWaitingCursor
      

      Task:
      https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_lsm_unittests_604d4f65e56b2a619cd71b0be8b41adcb03cd9ed_15_12_16_15_44_02
      Logs:
      https://logkeeper.mongodb.org/build/56719f1d9041306f24e09d12/test/56719f409041306f24e0aa19

      Assigning to acm for triage since he was last to touch this file.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: