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? > but a > yml file with all possible configurations set up could be a quick way > to check for compilation problems, and the github integration is just > fantastic imho. Agreed! -- regards, Reinhard _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
