Skip to content

Cancellation Leak Tests (Any and All) #148

@bahmanm

Description

@bahmanm

The current test-suites assert the behaviour with a small number of concurrent Flows.

To ensure there are no surprises for fellow engineers, this behaviour should be tested under much higher loads, i.e. 50 Flows:

  • Flows, if created using CancellableAsync flavours, should be cancelled
  • Tasks should be terminated.
  • Any resources acquired by them, should be disposed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions