Chiebot-Mirror
/
FFmpeg
mirror of https://github.com/FFmpeg/FFmpeg.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
78425 Commits
37 Branches
400 Tags
465 MiB
Tag: Branch: Tree: 35890aaa65
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '35890aaa65'
${ noResults }
FFmpeg/tests/ref/fate/parseutils

83 lines
2.5 KiB
Raw Normal View History Unescape

parseutils: add FATE test.
13 years ago
Testing av_parse_video_rate()
parseutils-test: do not print numerical error codes The error codes differ between systems so printing the value makes the fate test fail on some systems. Signed-off-by: Mans Rullgard <mans@mansr.com>
12 years ago
'-inf' -> -1/0 ERROR
'inf' -> 1/0 ERROR
'nan' -> 0/0 ERROR
'123/0' -> 1/0 ERROR
'-123 / 0' -> -1/0 ERROR
'' -> 0/0 ERROR
'/' -> 0/0 ERROR
' 123 / 321' -> 41/107 OK
'foo/foo' -> 0/0 ERROR
'foo/1' -> 0/0 ERROR
Merge commit 'b522000e9b2ca36fe5b2751096b9a5f5ed8f87e6' * commit 'b522000e9b2ca36fe5b2751096b9a5f5ed8f87e6': avio: introduce avio_closep mpegtsenc: set muxing type notification to verbose vc1dec: Use correct spelling of "opposite" a64multienc: change mc_frame_counter to unsigned arm: call arm-specific rv34dsp init functions under if (ARCH_ARM) svq1: Drop a bunch of useless parentheses parseutils-test: do not print numerical error codes svq1: K&R formatting cosmetics Conflicts: doc/APIchanges libavcodec/svq1dec.c libavcodec/svq1enc.c libavformat/version.h libavutil/parseutils.c tests/ref/fate/parseutils Merged-by: Michael Niedermayer <michaelni@gmx.at>
12 years ago
'1/foo' -> 1/0 ERROR
parseutils-test: do not print numerical error codes The error codes differ between systems so printing the value makes the fate test fail on some systems. Signed-off-by: Mans Rullgard <mans@mansr.com>
12 years ago
'0/0' -> 0/0 ERROR
'/0' -> 0/0 ERROR
Merge commit 'b522000e9b2ca36fe5b2751096b9a5f5ed8f87e6' * commit 'b522000e9b2ca36fe5b2751096b9a5f5ed8f87e6': avio: introduce avio_closep mpegtsenc: set muxing type notification to verbose vc1dec: Use correct spelling of "opposite" a64multienc: change mc_frame_counter to unsigned arm: call arm-specific rv34dsp init functions under if (ARCH_ARM) svq1: Drop a bunch of useless parentheses parseutils-test: do not print numerical error codes svq1: K&R formatting cosmetics Conflicts: doc/APIchanges libavcodec/svq1dec.c libavcodec/svq1enc.c libavformat/version.h libavutil/parseutils.c tests/ref/fate/parseutils Merged-by: Michael Niedermayer <michaelni@gmx.at>
12 years ago
'1/' -> 1/0 ERROR
parseutils-test: do not print numerical error codes The error codes differ between systems so printing the value makes the fate test fail on some systems. Signed-off-by: Mans Rullgard <mans@mansr.com>
12 years ago
'1' -> 1/1 OK
'0' -> 0/1 ERROR
'-123/123' -> -1/1 ERROR
'-foo' -> 0/0 ERROR
'123.23' -> 12323/100 OK
'.23' -> 23/100 OK
'-.23' -> -23/100 ERROR
'-0.234' -> -117/500 ERROR
av_d2q: Add a special case for |value| > MAX and |value| < 1/MAX Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
12 years ago
'-0.0000001' -> -1/10000000 ERROR
parseutils-test: do not print numerical error codes The error codes differ between systems so printing the value makes the fate test fail on some systems. Signed-off-by: Mans Rullgard <mans@mansr.com>
12 years ago
' 21332.2324 ' -> 917286/43 OK
' -21332.2324 ' -> -917286/43 ERROR
parseutils: add FATE test.
13 years ago
Testing av_parse_color()
bikeshed -> R(80) G(64) B(140) A(59)
RaNdOm -> R(185) G(88) B(148) A(94)
foo -> error
red -> R(255) G(0) B(0) A(255)
Red -> error
RED -> R(255) G(0) B(0) A(255)
Violet -> R(238) G(130) B(238) A(255)
Yellow -> R(255) G(255) B(0) A(255)
Red -> R(255) G(0) B(0) A(255)
0x000000 -> R(0) G(0) B(0) A(255)
0x0000000 -> error
0xff000000 -> R(255) G(0) B(0) A(0)
0x3e34ff -> R(62) G(52) B(255) A(255)
0x3e34ffaa -> R(62) G(52) B(255) A(170)
0xffXXee -> error
0xfoobar -> error
0xffffeeeeeeee -> error
#ff0000 -> R(255) G(0) B(0) A(255)
#ffXX00 -> error
ff0000 -> R(255) G(0) B(0) A(255)
ffXX00 -> error
red@foo -> error
random@10 -> error
0xff0000@1.0 -> R(255) G(0) B(0) A(255)
red@ -> error
red@0xfff -> error
red@0xf -> R(255) G(0) B(0) A(15)
red@2 -> error
red@0.1 -> R(255) G(0) B(0) A(25)
red@-1 -> error
red@0.5 -> R(255) G(0) B(0) A(127)
red@1.0 -> R(255) G(0) B(0) A(255)
red@256 -> error
red@10foo -> error
red@-1.0 -> error
red@-0.0 -> R(255) G(0) B(0) A(0)
parseutils: add av_parse_time() test.
13 years ago
fate: add av_small_strptime() test to fate-parseutils
12 years ago
Testing av_small_strptime()
fmt:'%Y-%m-%d' spec:'2012-12-21' -> 2012-12-21 00:00:00
fmt:'%Y - %m - %d' spec:'2012-12-21' -> 2012-12-21 00:00:00
fmt:'%Y-%m-%d %H:%M:%S' spec:'2012-12-21 20:12:21' -> 2012-12-21 20:12:21
fmt:' %Y - %m - %d %H : %M : %S' spec:' 2012 - 12 - 21 20 : 12 : 21' -> 2012-12-21 20:12:21
parseutils: add av_parse_time() test.
13 years ago
Testing av_parse_time()
(now is 2012-03-17 09:14:13 +0100, local time is UTC+1)
now -> 1331972053.000000 = 2012-03-17T08:14:13Z
12:35:46 -> 1331984146.000000 = 2012-03-17T11:35:46Z
2000-12-20 0:02:47.5z -> 977270567.500000 = 2000-12-20T00:02:47Z
2000-12-20T010247.6 -> 977270567.600000 = 2000-12-20T00:02:47Z
2:34:56.79 -> +9296790000
-1:23:45.67 -> -5025670000
42.1729 -> +42172900
-1729.42 -> -1729420000
tests: fix parseutils test after 12a269a5229d3a37be0743fc9655f743ebc44b6e "12:34" is now valid syntax.
12 years ago
12:34 -> +754000000