[Event Hubs] Time out on UsGov and China clouds.

We are running live Tests against other clouds like US Gov and Azure China Cloud. The goal is to check whether new azure sdk package work with other clouds or not.

Error Description: The latest result in pipeline at here: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1469381&view=results.

Test should support start after stopping was blocked until time out in pipeline on UsGov and China clouds.

In pipeline it always fails in the following environments:

• windows2019_12x_node

• ubuntu2004_14x_node

• macOS1015_16x_node

• windows2019_17x_node

• windows2019_coverage_12x

For more details, please click here. After investigation, after the asynchronous operation const partitionIds = await producerClient.getPartitionIds();, the program no longer executes downwards.

Expected behavior: Test should support start after stopping can be successfully passed.

@benbp , @xirzec , @lilyjma , @jsquire , @deyaaeldeen for notification.

[jeremymeng]

It looks like a previous issue. I opened PR# https://github.com/Azure/azure-sdk-for-js/pull/21850 for this.

[zedy-wj]

@jeremymeng , @benbp - It’s a great idea to configure different timeouts for different clouds.

But the current timeout on UsGov and China is not caused by performance issues and insufficient time allocated. We set a longer time (eg: 150 minutes) to test in the pipeline, and it still fails. Our research found that after the asynchronous operation const partitionIds = await producerClient.getPartitionIds();, the program no longer executes downwards. The whole pipeline is stuck in the should support start after stopping test, causing the final timeout.

The latest result in weekly pipeline at here : https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1523348&view=results.

Do you have any thoughts on this test timeout issue?

Notes: We also tested the test should support start after stopping locally, the result of this test is pass on UsGov and China clouds.