Flaky: AbortSignal Support when <command> is given a signal [1]

ExportXMLWordPrintableJSON

    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This was already "fixed" problem, but apparently not all the places were fixed. The pattern is the same - we start measuring before iteration even begins. The fix is the same as in NODE-7028 but mapped to other places.

      const start = performance.now();
const result = await willBeResultBlocked;
const end = performance.now();
expect(end - start).to.be.lessThan(10);

      In particular this test: https://github.com/mongodb/node-mongodb-native/blob/main/test/integration/node-specific/abort_signal.test.ts#L423
      Needs to be changed to something like this:

      let start;
onAbort(() => start = performance.now());
const result = await willBeResultBlocked;
const end = performance.now();
expect(end - start).to.be.lessThan(10);

      (But check for other occurrences)

      https://spruce.corp.mongodb.com/task/mongo_node_driver_next_windows_2022_latest_large_Node22_test_zstd_compression_8819a1db89dbb2e723b171261b95d0080c5c13cc_26_08_26_08_49_20/html-log?execution=0&origin=task

            Assignee:
            Unassigned
            Reporter:
            Sergey Zelenov
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: