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

Fix failing TestRealtimePresence_Sync250_RTP4 test #676

Open
lmars opened this issue Dec 4, 2024 · 0 comments
Open

Fix failing TestRealtimePresence_Sync250_RTP4 test #676

lmars opened this issue Dec 4, 2024 · 0 comments
Assignees
Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.

Comments

@lmars
Copy link
Member

lmars commented Dec 4, 2024

The TestRealtimePresence_Sync250_RTP4 is often failing with the following error:

=== RUN   TestRealtimePresence_Sync250_RTP4
    realtime_presence_integration_test.go:91: 
        	Error Trace:	realtime_presence_integration_test.go:91
        	Error:      	Received unexpected error:
        	            	[ErrorInfo :Rate limit exceeded; request rejected (nonfatal); metric = channel.maxRate; interval = 2024-12-02:19:53:6; permitted rate = 250; current rate = 300 code=42910 rate limit exceeded (nonfatal): request rejected (unspecified) statusCode=429] See https://help.ably.io/error/42910
        	Test:       	TestRealtimePresence_Sync250_RTP4
        	Messages:   	rg.Wait()=[ErrorInfo :Rate limit exceeded; request rejected (nonfatal); metric = channel.maxRate; interval = 2024-12-02:19:53:6; permitted rate = 250; current rate = 300 code=42910 rate limit exceeded (nonfatal): request rejected (unspecified) statusCode=429] See https://help.ably.io/error/42910

For example, see this build failure:

https://github.com/ably/ably-go/actions/runs/12126601920/job/33809045541

We should investigate and fix this.

┆Issue is synchronized with this Jira Task by Unito

@sacOO7 sacOO7 self-assigned this Dec 5, 2024
@sacOO7 sacOO7 added the failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug. label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.
Development

No branches or pull requests

2 participants