mirror of
https://gitee.com/openharmony/third_party_ffmpeg
synced 2024-11-24 11:49:48 +00:00
fate: update checksums for fate-lavf-ffm and fate-lavf-mxf
<@jamrial> durandal_1707: 04aa09c4bc
broke fate-lavf-ffm and fate-lavf-mxf
<@durandal_1707> how so?
<@jamrial> one byte changes
<@durandal_1707> jamrial: just update checksums
<@jamrial> durandal_1707: but why did they change at all? the commit you reverted didn't affect them
<@jamrial> why does reverting it affect these tests?
<@jamrial> i don't think updating the checksum without knowing what changed is a good idea
<@durandal_1707> jamrial: the lavfi core is in weird state after removal of recursive code
<@durandal_1707> jamrial: the change is that older ones would get progressive flag set and new one doesnt
<@jamrial> alright
This commit is contained in:
parent
349446e36f
commit
e5bce8b4ce
@ -1,3 +1,3 @@
|
||||
ca2a450cd0d1e299514a345923b4c82a *./tests/data/lavf/lavf.ffm
|
||||
a0e9616f0d9a8c1029f3220b1b9175f4 *./tests/data/lavf/lavf.ffm
|
||||
376832 ./tests/data/lavf/lavf.ffm
|
||||
./tests/data/lavf/lavf.ffm CRC=0x000e23ae
|
||||
|
@ -1,9 +1,9 @@
|
||||
eaac3125ac1a61fe5f968c7af83fa71e *./tests/data/lavf/lavf.mxf
|
||||
dbdbb7d8677dc29b0d90eedcf418ce13 *./tests/data/lavf/lavf.mxf
|
||||
525369 ./tests/data/lavf/lavf.mxf
|
||||
./tests/data/lavf/lavf.mxf CRC=0x8dddfaab
|
||||
1562530330b13e9e70f522fe20265632 *./tests/data/lavf/lavf.mxf
|
||||
40fcb0a898f8825a17f5754b23762f49 *./tests/data/lavf/lavf.mxf
|
||||
560697 ./tests/data/lavf/lavf.mxf
|
||||
./tests/data/lavf/lavf.mxf CRC=0xf21b1b48
|
||||
e07858715997313ae66a1cdd6fde5f66 *./tests/data/lavf/lavf.mxf
|
||||
9233d192af20fc2a89304f5ae93c21ee *./tests/data/lavf/lavf.mxf
|
||||
525369 ./tests/data/lavf/lavf.mxf
|
||||
./tests/data/lavf/lavf.mxf CRC=0x8dddfaab
|
||||
|
Loading…
Reference in New Issue
Block a user