test(playback): characterize byte-range LL-HLS failure - #274
Merged
Conversation
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #264
Replacement integration PR for closed draft #267. The GitHub connector cannot transition drafts to Ready for review because its GraphQL selection requests removed field
Repository.fullDatabaseId; GitHub also refuses merging a draft PR.This PR points to the same exact verified head
0f01786cb66e10f58e5bd5194a00f52d267bd571over the same exact basemain@37d485aa429f709256cde1ebd388965287f9a24b.No commit, rebase, or file changed while replacing #267.
Exact-head verification already completed successfully on this tree:
33468901232;33468901242;33468901297;33468901236;33468901231: API26 + API36 + aggregate success;33468901246.Diff remains exactly two test-scope files: deterministic LL-HLS characterization through MuxTV's real HLS construction path and scoped Apache-2.0 attribution for the AndroidX CMAF test-data bytes. No production playback behavior is changed.
A/B attribution from #271 remains: the identical test blob reproduces the same upstream defect on Media3 1.10.1 and 1.11.0, so it is pre-existing and not caused by the dependency update.