It's the free service, and so it's rate throttled by "reasonable use". In general we should avoid spamming the repository with a ton of requests to avoid causing Travis a surge.
However, the model that you used is the right one, since it triggers an individual installation of each package rather than failing on the first error (as a big unified PR would). I don't have an easy answer to how to rate limit pull requests -- hopefully this will just become easier as we run these sort of distfile checks on an ongoing basis and so do not let a big backlog build up. Thanks for taking all the trouble to file the PRs! Anil > On 22 Feb 2016, at 18:05, Fabrice Le Fessant > <fabrice.le_fess...@ocamlpro.com> wrote: > > Do we have a limited number of jobs on Travis ? jobs per jour, jobs per day, > jobs per month ? > --Fabrice > > On Mon, Feb 22, 2016 at 6:25 PM David Sheets <she...@alum.mit.edu > <mailto:she...@alum.mit.edu>> wrote: > Dear Fabrice, > > Please slow your submission of pull requests to ocaml/opam-repository. > > Your PRs solve long-standing and unreported issues (good!) but do so > in a way that is anti-social to the other members of the community. > > Specifically, you have now queued an enormous number of jobs on Travis > CI which will slow package publication and testing for emergent > issues. > > Respectfully, > > David Sheets > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-devel
_______________________________________________ opam-devel mailing list opam-devel@lists.ocaml.org http://lists.ocaml.org/listinfo/opam-devel
