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: Fix duplicate updates in StreamingEngine #4840

Merged
merged 3 commits into from
Dec 14, 2022

Conversation

joeyparrish
Copy link
Member

There were several places where certain StreamingEngine events and timing could result in duplicate update requests for streams. This caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and cancelling updates, to ensure that the proper conditions are maintained.

Closes #4831

There were several places where certain StreamingEngine events and
timing could result in duplicate update requests for streams.  This
caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and
cancelling updates, to ensure that the proper conditions are
maintained.

Closes shaka-project#4831
@joeyparrish
Copy link
Member Author

Fix tested over 50 runs of StreamingEngine tests on Chromecast in our lab. Without the fix, these tests failed roughly 3 out of 10 times. With the fix, these tests never failed in 50 runs.

@avelad avelad added type: bug Something isn't working correctly priority: P1 Big impact or workaround impractical; resolve before feature release labels Dec 14, 2022
@avelad avelad added this to the v4.4 milestone Dec 14, 2022
@github-actions
Copy link
Contributor

Incremental code coverage: 92.31%

@joeyparrish joeyparrish merged commit 224207b into shaka-project:main Dec 14, 2022
@joeyparrish joeyparrish deleted the fix-duplicate-se-updates branch December 14, 2022 21:51
joeyparrish added a commit that referenced this pull request Dec 14, 2022
There were several places where certain StreamingEngine events and
timing could result in duplicate update requests for streams. This
caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and cancelling
updates, to ensure that the proper conditions are maintained.

Closes #4831
joeyparrish added a commit that referenced this pull request Dec 14, 2022
There were several places where certain StreamingEngine events and
timing could result in duplicate update requests for streams. This
caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and cancelling
updates, to ensure that the proper conditions are maintained.

Closes #4831
joeyparrish added a commit that referenced this pull request Dec 14, 2022
There were several places where certain StreamingEngine events and
timing could result in duplicate update requests for streams. This
caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and cancelling
updates, to ensure that the proper conditions are maintained.

Closes #4831
joeyparrish added a commit that referenced this pull request Dec 14, 2022
There were several places where certain StreamingEngine events and
timing could result in duplicate update requests for streams. This
caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and cancelling
updates, to ensure that the proper conditions are maintained.

Closes #4831
Robloche pushed a commit to Robloche/shaka-player that referenced this pull request Feb 8, 2023
There were several places where certain StreamingEngine events and
timing could result in duplicate update requests for streams. This
caused some inconsistent test failures, in particular on Chromecast.

This change adds some additional checks before scheduling and cancelling
updates, to ensure that the proper conditions are maintained.

Closes shaka-project#4831
@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jul 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: P1 Big impact or workaround impractical; resolve before feature release status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Intermittent test failure on Chromecast
3 participants