Test Proxy hangs on final test output

[vincenttran-msft]

Bug Title

Test proxy hanging issue

Crate Name

azure_core_test

Crate Version

0.1.0

Description

This bug has existed awhile but I have mostly been side-stepping it since it didn't really affect my testing workflow, but has become problematic when testing things against a shared resource (i.e. Storage Account).

In short, when you run test proxy, it will always hang on the final tests and won't exit the testrunner. However, I know all tests have completely finished executing as evidenced by the following:

• Fiddler shows that all requests were made as expected
• New test recording generated even for the test omitted in the testrunner output

Note: I am running this against a Windows machine (namely my Windows devbox)

Steps to Reproduce

1. Run any suite of tests (i.e. cargo test --test blob_container_client)
2. This will run all tests, but the output will hang on the last test (although the test has already ran -- observe this behavior through Fiddler and results in a new .json recording)
3. The only way to exit this is to leave the test runner i.e. Ctrl+C

Example stdout:

C:\azure-sdk-for-rust\sdk\storage\azure_storage_blob>cargo test --test blob_container_client
Finished test profile [unoptimized + debuginfo] target(s) in 0.65s
Running tests\blob_container_client.rs (C:\azure-sdk-for-rust\target\debug\deps\blob_container_client-68bb231fd7665c9e.exe)
running 5 tests
test test_create_container ... ok
test test_get_container_properties ... ok
test test_list_blobs ... ok
test test_list_blobs_with_continuation ... ok
test test_set_container_metadata has been running for over 60 seconds
^C

Looking at the changes tab in VSCode for asset recordings:

Similarly, we can see this in a more contrived example (blob_service_client, 2 tests) to observe the Fiddler output:

Here we can see that the tests have already concluded, yet we are still stuck running the tests

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[vincenttran-msft]

This issue is further exacerbated if you pass the optional param -- --test-threads 1. In that case, it will hang on the first test executed 😄

C:\azure-sdk-for-rust\sdk\storage\azure_storage_blob>cargo test --test blob_service_client -- --test-threads 1
Finished test profile [unoptimized + debuginfo] target(s) in 0.66s
Running tests\blob_service_client.rs (C:\azure-sdk-for-rust\target\debug\deps\blob_service_client-de83bddd41592bf5.exe)
running 3 tests
test test_get_service_properties ...