[opam-devel] Travis CI failures

Anil Madhavapeddy anil at recoil.org
Mon Sep 29 14:24:26 BST 2014

None of the time is spent installing OCaml on the basic Linux install, since I've been compiling up a set of binary Debs/RPMs of the matrix of OCaml and OPAM versions (e.g. see https://launchpad.net/~avsm).  We only compile from source on the Mac, which is optional.

If someone is interested in proposing official OCaml support, a good template for anyone wishing to OCaml support in Travis is the pull request to add Rust support here:


On 29 Sep 2014, at 14:20, Ashish Agarwal <agarwal1975 at gmail.com> wrote:

> About 10 - 20 minutes out of the 50 get used up installing OCaml and basic libraries every time. Has anyone looked into getting OCaml as one of the natively supported languages by Travis? I'm not sure how it works, but ideally we could have preinstalled images with various versions of OCaml, opam, and several of the main libraries pre-installed.
> On Sun, Sep 28, 2014 at 4:03 PM, Anil Madhavapeddy <anil at recoil.org> wrote:
> On 28 Sep 2014, at 16:38, Thomas Gazagnaire <thomas at gazagnaire.org> wrote:
> > Hi all,
> >
> > Recently I saw Travis CI to be quite unreliable. It took sometimes hours to start and very often I need to manually re-lauch some tests because of connectivity errors. I don't complain too loudly because it's a free (and very useful) service, but I am wondering if we should not upgrade to something a bit more reliable.
> >
> > Looking at https://travis-ci.com/plans they seem to have few paying offer which might be interesting, although I am not sure to understand if this will solve the current issues. And it looks a little bit expensive, but we rely on the free service a lot already.
> >
> > Also, ideally we should use Travis CI to only coordinate the build on the Rackspace VMs but we don't have that infrastructure in place yet, so  maybe we should switch to a paying service for few months.
> My understanding is that the paid Travis service doesn't entirely help with the existing issues, which are infrastructure overload on their part.  The paid service increases the number of parallel builds, but still (e.g.) enforces the per-job 50 minute limit.
> I'll prioritise the Rackspace VM work to let us unlock more builds.  We're seeing an increasing number of repository failures due to the lack of reverse-transitive checking of builds, and that should be very easy to do in parallel on VM infrastructure.
> (I may be wrong about the latest in paid Travis -- if anyone wants to enquire with them, please do let me know.  I'm happy to pay for the service if it would solve any problems.)
> -anil
> _______________________________________________
> opam-devel mailing list
> opam-devel at lists.ocaml.org
> http://lists.ocaml.org/listinfo/opam-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/opam-devel/attachments/20140929/077e1bae/attachment.html>

More information about the opam-devel mailing list