[llvm-dev] RFC: Move the test-suite LLVM project to GitHub?

Kristof Beyls via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 25 00:48:15 PST 2016

My biggest concerns and care-abouts are largely what Matthias expressed 
Most of them have been addressed already further down the thread.

I hope that the move to github in practice would mean that the only 
difference is that I 'git clone https://github...' instead of 'git clone 
http://llvm.org/git/test-suite.git' ?



On 24/02/2016 22:25, Matthias Braun via llvm-dev wrote:
> I don't really care where the repository is located, but I do have 
> some comments on the future test-suite directions:
>> On Feb 24, 2016, at 12:57 PM, Chandler Carruth via llvm-dev 
>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>> Subject kinda says it all. Here is my rationale:
>> The test-suite is really weird relative to the rest of the LLVM project:
>> 1) It contains all manner of crazily licensed code.
> That's indeed a good reason to move the repository away.
>> 2) We don't really care about the history at all. Any concerns around 
>> linear history or bisection are pretty much irrelevant.
> We do care about the history. Sometimes benchmarks get fixed or 
> tweaked which may change the results, we should be able to dig into 
> the history to see what happened when. In any way retaining the 
> history wouldn't be a problem, would it?
>> 3) We don't ever plan to have LLVM code move into or out from the 
>> test-suite
> I could actually see moving llvm code into the test-suite (we already 
> use lit code from llvm) but indeed move code out of the testsuite into 
> llvm I don't foresee happening.
>> 4) Its already big, and really should be much bigger. We shouldn't 
>> have incentives to keep stuff out of the test suite because of size, 
>> hosting cost, or anything else.
> I agree with the goal of having a big test-suite. However I think 
> there is a point where we should rather strive to have a stable base 
> system for building and running tests, etc. and then have the actual 
> benchmarks/tests being modules on top of that. We already have that 
> situation today with External/SPEC* and I think it would be a good 
> idea to have a mode where you just checkout more benchmarks into a 
> test-suite subdirectory and they are automatically recognized and used 
> (in fact that is something on my TODO list though at a very low position).
> - Matthias
>> For all of these reasons, and also because I'd like to see how well 
>> (or rather, how poorly) a service like GitHub actually works for the 
>> project, it seems like splitting the test-suite out of the current 
>> subversion repository and moving it there is the right call.
>> When I chatted with folks on the board, this made sense to them as 
>> well, and I've made sure we have a reasonable LLVM organization set 
>> up on GitHub and all the board members are on it: 
>> https://github.com/llvm (I think only my membership is public at the 
>> moment).
>> There is still plenty to figure out about how to manage this on 
>> github, but before doing anything else I just wanted to shoot an 
>> email and see if folks like this idea.
>> Thanks!
>> -Chandler
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160225/38d2e450/attachment.html>

More information about the llvm-dev mailing list