On Sat, Jul 19, 2014 at 1:28 PM, Reinhard Tartler <[email protected]> wrote: > On Sat, Jul 19, 2014 at 12:35 PM, Vittorio Giovara > <[email protected]> wrote: >> On Sat, Jul 19, 2014 at 12:33 PM, Marc-Antoine ARNAUD >> <[email protected]> wrote: >>> Yes It can be redundant with the FATE Farm. >>> And the intergation is very usefull with github, each pull request can be >>> build with an auto-detection. >>> >>> It can be an usefull tool for contributions and code review/validation. >>> But I understood the FATE will be better for LibAV project in fact. >>> >> >> It might be a little redundant to run a fate test every time, > > Why is that redundant? We require folks to not break fate, and we > actually do expect folks to only submit patches that pass it. TBH, I > find it limiting that we don't have infrastructure that allows to > check a patch with fate before it hits master. > > Oracle http://oracle.libav.org/ tries to achieve exactly that. > However, it is only available to a limited set of people, and does not > support concurrent developments. I'm curious if travis could provide > that to us. > > Can we run fate on travis? Or at least a limited set of our fate tests?
We could and as long as everyone sends the patches to his own github repo travis will automatically run whatever test we instruct him to. The only limitations I see is that travis only runs linux x86_64 (and perhaps ios?) and destroys the virtual machine at every changeset, so we'd have to download the whole fate suite at every commit for every repository/pullrequest. I only tried travis on github I don't know if an in-house solution will offer a different setup (eg a vm image with the suite already in it) Cheers, -- Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
