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

WebSocket release acceptance tests are flaky #3204

Open
ebadiere opened this issue Nov 1, 2024 · 1 comment · May be fixed by #3242
Open

WebSocket release acceptance tests are flaky #3204

ebadiere opened this issue Nov 1, 2024 · 1 comment · May be fixed by #3242
Assignees
Labels
bug Something isn't working
Milestone

Comments

@ebadiere
Copy link
Collaborator

ebadiere commented Nov 1, 2024

Description

The websocket release tests are run as part of the release process. This last release many failed, but when they were run in isolation they passed. Also, running them in the debugger allowed them to pass. The failing tests were running against testnet.

Steps to reproduce

Run the release-ws tests against testnet.

Additional context

No response

Hedera network

testnet

Version

v0.59.0

Operating system

macOS

@ebadiere ebadiere added the bug Something isn't working label Nov 1, 2024
@ebadiere ebadiere self-assigned this Nov 4, 2024
@ebadiere ebadiere added this to the 0.60.0 milestone Nov 4, 2024
@ebadiere
Copy link
Collaborator Author

ebadiere commented Nov 4, 2024

This is happening on testnet. It appears as if one of the pods on testnet is having issues with the mirror node:

Error: timeout of 10000ms exceeded at MirrorNodeClient.handleError (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:249:29) at MirrorNodeClient...

statusCode": 504

@ebadiere ebadiere linked a pull request Nov 10, 2024 that will close this issue
@quiet-node quiet-node modified the milestones: 0.60.0, 0.61.0 Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants