<div dir="ltr"><div dir="ltr">I suppose we should discuss the use case first and then find the right tool for the purpose.<div><br></div><div>Why not re-use the build bots?</div><div>What do you want to build and test? Only the release branch?</div><div>Is this in addition to the build bots and pre-merge testing?</div><div>On which platforms?</div><div>How often/when to trigger a build?</div><div><br></div><div>--</div><div>Christian</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 13, 2019 at 2:38 PM Valentin Churavy <<a href="mailto:v.churavy@gmail.com">v.churavy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I think my concern is that LLVM could prove to be too big and require too many resources for github's infrastructure. How many patches go into LLVM a day, and how many build and test jobs does GitHub allow users to run concurrently before being throttled?</div></blockquote><div><br></div><div>A big project like LLVM, should almost never rely on the free tier of a CI service. I am neither for nor against Github actions (I personally use them for my project and they work out well, but the caching story needs more work), but Github actions at least allows for self hosted runners that allows us to move the load away from their infrastructure to ours. </div><div><br></div><div><a href="https://help.github.com/en/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners#about-self-hosted-runners" target="_blank">https://help.github.com/en/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners#about-self-hosted-runners</a> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 12, 2019 at 1:53 PM Reid Kleckner via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I think everyone agrees that LLVM needs better CI, automatic pre-commit testing of various platforms, etc. This is not rocket science, it is standard practice for 2019 software engineering.<div><br></div><div>I think my concern is that LLVM could prove to be too big and require too many resources for github's infrastructure. How many patches go into LLVM a day, and how many build and test jobs does GitHub allow users to run concurrently before being throttled?</div><div><br></div><div>You may have seen that Christian Kuhnel has been working on a pre-commit testing bot that integrates with Phab:</div><div><a href="https://reviews.llvm.org/p/merge_guards_bot/" target="_blank">https://reviews.llvm.org/p/merge_guards_bot/</a> </div><div><a href="https://github.com/google/llvm-premerge-checks/blob/master/docs/user_doc.md" target="_blank">https://github.com/google/llvm-premerge-checks/blob/master/docs/user_doc.md</a></div><div>I hope that ends up being the way forward and suits Tom's original release testing goals.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 11, 2019 at 11:43 PM John Byrd via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Please forgive the incorrect threading on this reply to Tom Stellard's RFC.<div><br></div><div>> I would like to start using <span>GitHub</span> <span>Actions</span>[1] for <span>CI</span> testing on the release/*<br>> branches. As far as I know we don't have any buildbots listening to the<br>> release branches, and I think <span>GitHub</span> <span>Actions</span> are a good way for us to<br>> quickly bring-up some <span>CI</span> jobs there. </div><div><br></div><div>Personally, I feel that Tom's proof of concept, is more important than we seem to be giving him credit for.</div><div><br></div><div>As of this writing, the Github actions system permits all comers, six hours of CPU time per build platform. Due to this long CPU allotment, AFAIK, Github is one of the few CIs in town that lets anyone build and smoke llvm for free.</div><div><br></div><div>Consider the workflow of someone who has never worked on llvm before. They will probably fork the monorepo on Github, in order to fix bugs or add a feature or such. At the moment they do this, they get a built-in workflow that will sanity-check their builds on several important targets. Zero braining involved.</div><div><br></div><div>Giving Joe Programmer a CI system that magically smoke tests llvm, out of the box, after he forks the repo, is a compelling reason to make something like Tom's system a standard part of llvm master.</div><div><br></div><div>Concerns might be raised that llvm is "preferring" one CI system over another. Some thoughts about that. First, because the monorepo's on Github, you'll end up going to <a href="http://github.com" target="_blank">github.com</a> anyway to get your first pull. Second, nothing about Github actions precludes supporting other CI systems in the future.</div><div><br></div><div>Thanks for your kind consideration.<br clear="all"><div><br></div>-- <br><div dir="ltr">---<br><br>John Byrd<br>Gigantic Software<br>2321 E 4th Street<br>Suite C #429<br>Santa Ana, CA 92705-3862<br><a href="http://www.giganticsoftware.com" target="_blank">http://www.giganticsoftware.com</a><br>T: <a href="tel:(949)%20892-3526" value="+19498923526" target="_blank">(949) 892-3526</a> F: <a href="tel:(206)%20309-0850" value="+12063090850" target="_blank">(206) 309-0850</a></div></div></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Best,<div>Christian</div></div></div></div>