WebmMuxer: fix bug shadowed by broken unit test.
While cleaning up to act on actually observed buffers in the WebM stream parser stream, I discovered that this test expectation isn't working: https://source.chromium.org/chromium/chromium/src/+/master:media/muxers/webm_muxer_unittest.cc;l=645-658?q=webm_muxer_unittest.cc&ss=chromium%2Fchromium%2Fsrc. After acting on actually passed buffers, it was found that the test fails. The reason is that in https://source.chromium.org/chromium/chromium/src/+/master:media/muxers/webm_muxer.h;l=155-157;bpv=1;bpt=1, last_xxx_ attributes are unset on first incoming buffers, leading the code to believe it's receiving non-monotonically increasing buffer timestamps. Bug: chromium:1124735 Change-Id: Icf093fb94eef637ab17b8d38edd066313b5f7b48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390634 Commit-Queue: Markus Handell <handellm@google.com> Reviewed-by:Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#804636}
Showing
Please register or sign in to comment