Don't create an operation key by default for test commands in the NetworkInterfaceTest

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: Networking
    • Networking & Observability
    • Fully Compatible
    • N&O 2025-07-21
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we send a command through the NetworkInterfaceTL, we schedule a killOperations command if a failure occurs and an operation key exists on the request. This killOperations command has historically caused test failures that were not expecting an extra command to run. We should update NetworkInterfaceTest::makeTestCommand() to not create a request with an operationKey if one is not passed in. That way, only the tests that expect a killOperations will schedule one.

            Assignee:
            Cole Harbeck
            Reporter:
            Joseph Prince
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: