[Flang-dev] [RFC] Enable CI for flang/f18 on travis-ci.org

Stephen Scalpone sscalpone at nvidia.com
Fri Dec 21 02:11:31 EST 2018

Hey Francesco,

I tried travis ci a while back.  The free tier time limit was exceeded trying to build llvm. I didn’t see an easy way to use a pre-built llvm so I gave up rather quickly.  I think you can do quite a bit without the github api integration.

Let me know how I can help.

- Steve

From: flang-dev <flang-dev-bounces at lists.flang-compiler.org> on behalf of Jeff Hammond <jeff.science at gmail.com>
Date: Thursday, December 20, 2018 at 4:23 PM
To: Francesco Petrogalli <Francesco.Petrogalli at arm.com>
Cc: "flang-dev at lists.flang-compiler.org" <flang-dev at lists.flang-compiler.org>, nd <nd at arm.com>
Subject: Re: [Flang-dev] [RFC] Enable CI for flang/f18 on travis-ci.org

On Thu, Dec 20, 2018 at 1:14 PM Francesco Petrogalli <Francesco.Petrogalli at arm.com<mailto:Francesco.Petrogalli at arm.com>> wrote:

> On Dec 20, 2018, at 8:47 PM, Jeff Hammond <jeff.science at gmail.com<mailto:jeff.science at gmail.com>> wrote:
> Travis CI is fantastic and this is a great idea.

Yes, I agree :)

>  I hope you have experience dealing with very long clones and builds, because those tend to be an issue.

That’s my concern too - I hope to overcome this problem with docker. But first step is to try if a plain build from scratch works.

I don't know enough about Docker in Travis CI to know if this has the potential to hide any problems that should be caught.

> Do you have Travis CI enabled in your fork of the repo?  Seeing it working there makes it a lot easier to get everybody on board with this.

That was my original plan, but it seems that there are some legal concerns in enabling this on a separate for of the repo.

For now, it would be easier if you could enable this on the original flag repo. If you have concerns doing this (for example you don’t want to have to deal with any problem related to having to run it on master), we could enable travis only for a specific branch of the flang repo (see for example https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches). How about you create an experimental branch in flang where I could submit travis-only pull requests? One we are happy with the travis-only branch, we can merge it in master and activate travis for master too.

Let me know if this works for you, and if it does, let me know what is the branch that you want me to use for the experiment.

I don't have the power to do any of this.  I was merely trying to make helpful suggestions, but I don't understand and can't comment on the legal issues you mention.


Kind regards,


> Best,
> Jeff
> On Thu, Dec 20, 2018 at 11:16 AM Francesco Petrogalli <Francesco.Petrogalli at arm.com<mailto:Francesco.Petrogalli at arm.com>> wrote:
> Hi all,
> I would like to propose enabling CI service on travis-ci.org<http://travis-ci.org> for the flang and f18 repository.
> The idea is that any pull request for the repo will be verified by running the unit tests of the projects.
> travis-ci.org<http://travis-ci.org> works by keeping tracks of the changes in the repo and automatically building and running the tests.
> I already have a patch that builds and run clang on x86.
> To test this out, the owner of the flang/f18 GitHub accounts will have to create an account on travis-ci.org<http://travis-ci.org>  (can be done with the GitHub account credentials) and enable tracking of the repositories.
> Kind regards,
> Francesco
> _______________________________________________
> flang-dev mailing list
> flang-dev at lists.flang-compiler.org<mailto:flang-dev at lists.flang-compiler.org>
> http://lists.flang-compiler.org/mailman/listinfo/flang-dev_lists.flang-compiler.org
> --
> Jeff Hammond
> jeff.science at gmail.com<mailto:jeff.science at gmail.com>
> http://jeffhammond.github.io/

Jeff Hammond
jeff.science at gmail.com<mailto:jeff.science at gmail.com>

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flang-compiler.org/pipermail/flang-dev_lists.flang-compiler.org/attachments/20181221/c76af3ba/attachment-0001.html>

More information about the flang-dev mailing list