diff options
| author | Martin Storsjö <martin@martin.st> | 2024-04-03 14:43:14 +0300 |
|---|---|---|
| committer | Martin Storsjö <martin@martin.st> | 2024-04-11 14:08:55 +0300 |
| commit | e4f5c2414bb50df07dce9a8860aaeeaccaed15cf (patch) | |
| tree | 9eb82324333e064ccfd6e496eb9b4e975e19520c /tests | |
| parent | 497a0f839d7d98e182aa27044e0dbeeb89783d4b (diff) | |
| download | ffmpeg-e4f5c2414bb50df07dce9a8860aaeeaccaed15cf.tar.gz | |
tests/movenc: Validate that normal muxer usage doesn't print warnings
We have test to make sure that certain configurations do print
warnings. However, the normal operation of the muxer within this
test always printed a warning, so those tests to check for
extra warnings didn't essentially guard anything.
The warning that always was printed, "track 1: codec frame size is
not set" was not present in the libav fork where this testcase
originated, it was removed in f234e8a32e6c69d7b63f8627f278be7c2c987f43.
Set the frame size for the audio stream to silence the warning,
and use this frame size in a couple later calculations, and check
that one test configuration doesn't print warnings.
Setting the frame size apparently changes the rounding of a timestamp
in the ismv muxing testcase.
Signed-off-by: Martin Storsjö <martin@martin.st>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/ref/fate/movenc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/ref/fate/movenc b/tests/ref/fate/movenc index f6a408aa54..5c12aeb29f 100644 --- a/tests/ref/fate/movenc +++ b/tests/ref/fate/movenc @@ -20,7 +20,7 @@ write_data len 828, time nopts, type unknown atom - write_data len 728, time 999999, type sync atom moof write_data len 812, time nopts, type unknown atom - write_data len 148, time nopts, type trailer atom - -92ce825ff40505ec8676191705adb7e7 4439 ismv +d2df24d323f4a8896441cd91203ac5f8 4439 ismv write_data len 36, time nopts, type header atom ftyp write_data len 1123, time nopts, type header atom - write_data len 796, time 0, type sync atom moof |