Skip to content

Address data streams e2e test failure - #749

Merged
1egoman merged 2 commits into
duan/bump-rtc-ffi-bindingsfrom
fix-data-streams-e2e
Oct 19, 2026
Merged

1egoman merged 2 commits into
duan/bump-rtc-ffi-bindingsfrom
fix-data-streams-e2e

Conversation

@1egoman

@1egoman 1egoman commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Due to livekit/rust-sdks#1510 being merged, an e2e test has started breaking:

AssertionError: expected 'Error: stream closed abnormally: Data…' to match /Disconnected while
  receiving/

Previously, if a data stream was in progress and a room disconnected, the e2e tests would assert that the data stream would silently just end and return the buffered text. As of livekit/rust-sdks#1510, this behavior changes to now reject with an explicit Error: stream closed abnormally: Data stream connection closed error in this case. So, update the e2e tests to also check this.

Important

UPDATE: After e9dff31, the e2e tests still failed. I had a LLM investigate it and it seems like the old failure mode that this rust sdks fix was aiming to prevent still seems to occur in high load environments (like github actions) sometimes, for unclear reasons. I was able to reproduce this locally on my laptop as well if the test run happened under a lot of CPU stress. Because of this, I've widened the e2e test criteria to accept both possibilities (stream closing abnormally, or silent termination with a half finished stream) to unblock folks.

I will do some investigation, figure out what is going on here, and push a proper fix which stops this "silent termination" case from happening.

@changeset-bot

changeset-bot Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0bc6d84

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@1egoman
1egoman changed the base branch from main to duan/bump-rtc-ffi-bindings October 19, 2026 19:23
@1egoman
1egoman force-pushed the fix-data-streams-e2e branch from 903442a to e9dff31 Compare October 19, 2026 19:23
CI has seen a clean eos land before disconnect completes, ending the
read with the chunks buffered so far. Accept that outcome again while
the native cause is investigated.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@1egoman
1egoman marked this pull request as ready for review October 19, 2026 19:51
@1egoman
1egoman merged commit 8cb2988 into duan/bump-rtc-ffi-bindings Oct 19, 2026
1 of 2 checks passed
@1egoman
1egoman deleted the fix-data-streams-e2e branch October 19, 2026 19:51

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

cloudwebrtc added a commit that referenced this pull request Oct 21, 2026
* chore: bump rtc-ffi-bindings to 0.12.83.

* update.

* Address data streams e2e test failure (#749)

* fix: address data streams e2e test failure

* test: tolerate a clean end-of-stream when the room disconnects

CI has seen a clean eos land before disconnect completes, ending the
read with the chunks buffered so far. Accept that outcome again while
the native cause is investigated.

* bump to 0.13.0.

* bump to 0.13.1.

* add .changset.

---------

Co-authored-by: Ryan Gaus <ryan.gaus@livekit.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants