Re: [FFmpeg-devel] [PATCH] fate: unbreak fate with custom binary names

2019-04-02 Thread Gyan
On 03-04-2019 10:03 AM, Gyan wrote: On 02-04-2019 04:57 PM, Gyan wrote: I ran full fate and some tests failed as the ffmpeg binary wasn't found. Suffixes weren't respected. Fixed. I can run fate only occasionally. Maybe one of the regular FATE submitters could set a suffix (and extension)

Re: [FFmpeg-devel] [PATCH] fate: unbreak fate with custom binary names

2019-04-02 Thread Gyan
On 02-04-2019 04:57 PM, Gyan wrote: I ran full fate and some tests failed as the ffmpeg binary wasn't found. Suffixes weren't respected. Fixed. I can run fate only occasionally. Maybe one of the regular FATE submitters could set a suffix (and extension) to keep a check on this. Will push s

Re: [FFmpeg-devel] [PATCH] fate: unbreak fate with custom binary names

2019-04-02 Thread Gyan
On 02-04-2019 05:38 PM, Hendrik Leppkes wrote: On Tue, Apr 2, 2019 at 1:27 PM Gyan wrote: I ran full fate and some tests failed as the ffmpeg binary wasn't found. Suffixes weren't respected. Fixed. I can run fate only occasionally. Maybe one of the regular FATE submitters could set a suffix

Re: [FFmpeg-devel] [PATCH] fate: unbreak fate with custom binary names

2019-04-02 Thread Hendrik Leppkes
On Tue, Apr 2, 2019 at 1:27 PM Gyan wrote: > > I ran full fate and some tests failed as the ffmpeg binary wasn't found. > Suffixes weren't respected. Fixed. > > I can run fate only occasionally. Maybe one of the regular FATE > submitters could set a suffix (and extension) to keep a check on this.

[FFmpeg-devel] [PATCH] fate: unbreak fate with custom binary names

2019-04-02 Thread Gyan
I ran full fate and some tests failed as the ffmpeg binary wasn't found. Suffixes weren't respected. Fixed. I can run fate only occasionally. Maybe one of the regular FATE submitters could set a suffix (and extension) to keep a check on this. Thanks, Gyan From 287c7244ef6370de45771c7979ec6b65