test(playback): characterize byte-range LL-HLS failure - #267
Closed
MrFr3di wants to merge 1 commit into
Closed
Conversation
This was referenced Sep 1, 2026
MrFr3di
force-pushed
the
test/ll-hls-byte-range-264
branch
from
September 1, 2026 04:11
140575a to
0f01786
Compare
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
This PR carried the fully verified LL-HLS characterization on exact head
0f01786cb66e10f58e5bd5194a00f52d267bd571overmain@37d485aa429f709256cde1ebd388965287f9a24b.All six exact-head lanes were GREEN: Hosted CI contract #261, Media3 lint #58, App TV lint #216, focused API36 #375, API26/API36 matrix #467, Hosted Full #1971.
GitHub's draft-to-ready mutation is currently broken in the connected integration (
Repository.fullDatabaseIdGraphQL schema error), and GitHub refuses merging a draft PR. The branch/head itself is valid and mergeable. This draft PR is therefore closed without changing the branch so the exact same head/base can be integrated through a non-draft replacement PR.No production playback code is changed; the diff remains the characterization test plus scoped Apache-2.0 attribution for AndroidX test-data.