On Wed, 07. Oct 09:59, Chris Miceli wrote:
> Hi Andriy,
>
> Thanks for letting me know that there is already something doing this. It
> was something which I thought would exist but I couldn't see it in my
> searching of the ffmpeg documentation.
>
> Something which would be nice is finding a wa
Hi Andriy,
Thanks for letting me know that there is already something doing this. It
was something which I thought would exist but I couldn't see it in my
searching of the ffmpeg documentation.
Something which would be nice is finding a way for us to tie the results
back into the fate system, or
On Tue, 06. Oct 16:07, Nicolas George wrote:
> Andriy Gelman (12020-10-06):
> > I'm not familiar with the setup on fate.ffmpeg.org, but we have something
> > similar running patchwork.ffmpeg.org
> >
> > The site fetches patches from the mailing list. Jenkins server runs
> > make/fate
> > and rep
Andriy Gelman (12020-10-06):
> I'm not familiar with the setup on fate.ffmpeg.org, but we have something
> similar running patchwork.ffmpeg.org
>
> The site fetches patches from the mailing list. Jenkins server runs make/fate
> and reports the results back to patchwork.
That means anybody can r
Hi,
On Tue, 06. Oct 14:16, Chris Miceli wrote:
> Hi all,
>
> I have written a small system called autofate (
> https://github.com/cmiceli/autofate) which is designed to basically run
> fate on every commit in master, ideally capturing and then reporting broken
> builds. It's written in rust so th
Hi all,
I have written a small system called autofate (
https://github.com/cmiceli/autofate) which is designed to basically run
fate on every commit in master, ideally capturing and then reporting broken
builds. It's written in rust so that it can run on a wide variety of
platforms (I am currently
