waitForCurOpByFailPoint shouldn't ignore filter parameter in 4.4

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.1
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • Query 2020-08-10
    • 37
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In master, the waitForCurOpByFailPoint() helper takes an optional filter argument and uses it to wait for a matching operation to hit a fail point. jstests/sharding/kill_pinned_cursor.js uses waitForCurOpByFailPoint() with a filter argument in 4.4 but in 4.4 the helper ignores the filter.

            Assignee:
            Nicholas Zolnierz
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: