[FFmpeg-devel] [PATCH] libavcodec/parser.c: re-fetch PTS/DTS if fetch failed

luckliuyuxin luckliuyuxin at 163.com
Mon Apr 27 10:39:47 CEST 2015


Michael ,

This is my first time send path to ffmpeg. I'm not familiar with "make fate".
Could you please told me how the "make fate" report the break error?
The following is my steps to make fate on my computer, but I couldn't find the error of break "make fate".

my steps:
1 make fate-rsync SAMPLES=fate-suite/         
2 cp doc/fate_config.sh.template fate_config
3 vim fate_config   //update content according to my computer enviroment
4 ./tests/fate.sh /home/user/source/ffmpegsrc/ffmpeg_2_6/fate_config


After finished of ./tests/fate.sh, the following files created by ./tests/fate.sh:
version-i7-4770-linux-qemu-ubuntu14.04-gcc-4.4.7-liuyuxin
configure.log
compile.log
test.log 
report

I have read all the above files, but I don't find any error which break the "make fate".


Thanks,
Yuxin

------------my fate_config content  begin---------------------
slot=i7-4770-linux-qemu-ubuntu14.04-gcc-4.4.7-liuyuxin             # some unique identifier
repo=git://source.ffmpeg.org/ffmpeg.git                            # the source repository
samples=/home/user/source/ffmpegsrc/ffmpeg_2_6/fate-suite          # path to samples directory
workdir=/home/user/source/ffmpegsrc/ffmpeg_2_6                     # directory in which to do all the work
#fate_recv="ssh -T fate at fate.ffmpeg.org" # command to submit report
comment="test --cpu=8"                                             # optional description
build_only=     # set to "yes" for a compile-only instance that skips tests

# the following are optional and map to configure options
arch=
cpu=
cross_prefix=
as=
cc=
ld=
target_os=
sysroot=
target_exec=
target_path=
target_samples=
extra_cflags=
extra_ldflags=
extra_libs=
extra_conf=     # extra configure options not covered above

#make=          # name of GNU make if not 'make'
makeopts=       # extra options passed to 'make'
#tar=           # command to create a tar archive from its arguments on stdout,
                # defaults to 'tar c'
------------my fate_config content end-------------------------


At 2015-04-23 01:27:30, "Michael Niedermayer" <michaelni at gmx.at> wrote:
>On Wed, Apr 22, 2015 at 07:17:59PM +0800, luckliuyuxin wrote:
>[...]
>>  parser.c |    5 +++++
>>  1 file changed, 5 insertions(+)
>> f3ed39fd2c44d36a96dbab27a8c810d7479e8d22  0001-re-fetch-PTS-DTS-if-fetch-failed.patch
>> From 00b457adb855b0b25ac7cde4a9cb8c7b53fd0511 Mon Sep 17 00:00:00 2001
>> From: liuyuxin <liuyuxin at xiaomi.com>
>> Date: Wed, 22 Apr 2015 16:56:42 +0800
>> Subject: [PATCH] re-fetch PTS/DTS if fetch failed
>> 
>> IQiYi has special PES packets:
>> |<-------PES#1------->|<-----PES#2--->|
>> | AUD | P frame | PPS | AUD | P frame |
>
>isnt this a violation of the spec ?
>
>anyway, please provide a sample file of such stream
>
>also the patch breaks "make fate"
>
>[...]
>
>-- 
>Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
>The misfortune of the wise is better than the prosperity of the fool.
>-- Epicurus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: version-i7-4770-linux-qemu-ubuntu14.04-gcc-4.4.7-liuyuxin
Type: application/octet-stream
Size: 16 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150427/0e44b8e7/attachment.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: test.log
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150427/0e44b8e7/attachment.log>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: compile.log
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150427/0e44b8e7/attachment-0001.log>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fate_config
Type: application/octet-stream
Size: 1094 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150427/0e44b8e7/attachment-0001.obj>


More information about the ffmpeg-devel mailing list