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.

Sign up for GitHub

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

Jump to bottom

[Service Bus] Batching updateSubscription() using different variations failing in nightly runs #17736

Closed
v-jiaodi opened this issue Sep 18, 2021 · 3 comments
Closed

[Service Bus] Batching updateSubscription() using different variations failing in nightly runs #17736

v-jiaodi opened this issue Sep 18, 2021 · 3 comments
Assignees
@jeremymeng
Labels
Client This issue points to a problem in the data-plane of the library. Service Bus test-reliability Issue that causes tests to be unreliable

Comments

@v-jiaodi
Copy link
Member

Service Bus nightly test runs are failing with:

Error message:
request to https://t91c2799274be48cc.servicebus.windows.net/management-queue-1?api-version=2017-04 failed, reason: write EPIPE

Stack trace:
FetchError: request to https://t91c2799274be48cc.servicebus.windows.net/management-queue-1?api-version=2017-04 failed, reason: write EPIPE
at ClientRequest. (/Users/runner/work/1/s/common/temp/node_modules/.pnpm/node-fetch@2.6.2/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:400:28)
at ClientRequest.emit (domain.js:470:12)
at TLSSocket.socketErrorListener (_http_client.js:475:9)
at TLSSocket.emit (events.js:400:28)
at TLSSocket.emit (domain.js:470:12)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:82:21)

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 Sep 18, 2021
@v-xuto v-xuto added Client This issue points to a problem in the data-plane of the library. Service Bus 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 Sep 18, 2021
@maorleger
Copy link
Member

@chradek also on OS X! Seems to have passed on subsequent runs...

@maorleger maorleger assigned chradek and unassigned maorleger Sep 20, 2021
@chradek
Copy link
Contributor

chradek commented Sep 20, 2021

I'm noticing a pattern...

@jeremymeng jeremymeng assigned jeremymeng and unassigned chradek Oct 15, 2021
@jeremymeng
Copy link
Contributor

Not seeing this in the past 30 days. Closing for now.

@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.
Assignees

@jeremymeng jeremymeng

Labels
Client This issue points to a problem in the data-plane of the library. Service Bus test-reliability Issue that causes tests to be unreliable
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@maorleger @jeremymeng @chradek @v-xuto @v-jiaodi