Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Communication - Network Traversal] test failing in nightly runs #16616

Closed
v-jiaodi opened this issue Jul 28, 2021 · 1 comment
Closed

[Communication - Network Traversal] test failing in nightly runs #16616

v-jiaodi opened this issue Jul 28, 2021 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Communication test-reliability Issue that causes tests to be unreliable

Comments

@v-jiaodi
Copy link
Member

Communication - Network Traversal nightly test runs are failing with:

Error message:
Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/1/s/sdk/communication/communication-network-traversal/dist-esm/test/public/communicationNetworkTraversalClient.spec.js)

Stack trace:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/1/s/sdk/communication/communication-network-traversal/dist-esm/test/public/communicationNetworkTraversalClient.spec.js)
at Test.Runnable._timeoutError (/Users/runner/work/1/s/common/temp/node_modules/.pnpm/mocha@7.2.0/node_modules/mocha/lib/runnable.js:442:10)
at Timeout. (/Users/runner/work/1/s/common/temp/node_modules/.pnpm/mocha@7.2.0/node_modules/mocha/lib/runnable.js:252:24)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)

For more details check here:

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 28, 2021
@v-xuto v-xuto added Client This issue points to a problem in the data-plane of the library. Communication test-reliability Issue that causes tests to be unreliable and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Jul 28, 2021
@maorleger
Copy link
Member

Latest runs consistently passing, closing this

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this issue Nov 2, 2021
[Synapse] Decouple dependencies among Swagger specs  (Azure#16616)

* extract workspaceNameParameter to common

* move some definitions to common folder

* workspaceNameParameter

* fix

* fix

* revert for libraryInfo

* fix for breaking change

* test for breaking change

* test for breaking change
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Communication test-reliability Issue that causes tests to be unreliable
Projects
None yet
Development

No branches or pull requests

3 participants