llvm dev - Feb 2016 - RFC: Move the test-suite LLVM project to GitHub?

----- Original Message -----
> From: "Mehdi Amini via llvm-dev" <llvm-dev at
lists.llvm.org>
> To: "Joerg Sonnenberger" <joerg at britannica.bec.de>
> Cc: llvm-dev at lists.llvm.org
> Sent: Wednesday, February 24, 2016 4:30:42 PM
> Subject: Re: [llvm-dev] RFC: Move the test-suite LLVM project to GitHub?
> 
> 
> > On Feb 24, 2016, at 1:43 PM, Joerg Sonnenberger via llvm-dev
> > <llvm-dev at lists.llvm.org> wrote:
> > 
> > On Wed, Feb 24, 2016 at 02:20:24PM -0700, Jonathan Roelofs via
> > llvm-dev wrote:
> >> 2) There is the cap on total repository size, which is in the
> >> neighborhood
> >> of 1Gb [3]. A fresh checkout of test-suite clocks in at just over
> >> 3Gb. This
> >> one actually is a problem.
> > 
> > This is not really true. Individual pack files must be below 1GB,
> > but
> > the total repository can be much larger. That's true even for the
> > free
> > tiers. That said, it might be good idea to split the repository
> > into
> > modules to keep it managable.
> > 
> 
> I'm really in favor of a modular test-suite, splitting as much as
> possible the infrastructure with the individual suites, and making
> it super easy and convenient to assemble modular suites together. We
> already have the mechanism for "external" test-suite, it would
just
> need to be first-class.
> i.e. I'd like to clone the test-suite, which would get me only the
> infrastructure but no test to run, and then easily say: "clone these
> test-suite and make them available: llvm, Halide, etc." which would
> clone them from separate repositories. And then list the available
> suite and quick runs over chosen ones.
> 
> Just some thoughts...
As a longer-term goal, this sounds really nice.

 -Hal
> 
> --
> Mehdi
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
-- 
Hal Finkel
Assistant Computational Scientist
Leadership Computing Facility
Argonne National Laboratory

On Fri, Feb 26, 2016 at 7:29 PM, Hal Finkel via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> ----- Original Message -----
> > From: "Mehdi Amini via llvm-dev" <llvm-dev at
lists.llvm.org>
> > To: "Joerg Sonnenberger" <joerg at britannica.bec.de>
> > Cc: llvm-dev at lists.llvm.org
> > Sent: Wednesday, February 24, 2016 4:30:42 PM
> > Subject: Re: [llvm-dev] RFC: Move the test-suite LLVM project to
GitHub?
> >
> >
> > > On Feb 24, 2016, at 1:43 PM, Joerg Sonnenberger via llvm-dev
> > > <llvm-dev at lists.llvm.org> wrote:
> > >
> > > On Wed, Feb 24, 2016 at 02:20:24PM -0700, Jonathan Roelofs via
> > > llvm-dev wrote:
> > >> 2) There is the cap on total repository size, which is in the
> > >> neighborhood
> > >> of 1Gb [3]. A fresh checkout of test-suite clocks in at just
over
> > >> 3Gb. This
> > >> one actually is a problem.
> > >
> > > This is not really true. Individual pack files must be below 1GB,
> > > but
> > > the total repository can be much larger. That's true even for
the
> > > free
> > > tiers. That said, it might be good idea to split the repository
> > > into
> > > modules to keep it managable.
> > >
> >
> > I'm really in favor of a modular test-suite, splitting as much as
> > possible the infrastructure with the individual suites, and making
> > it super easy and convenient to assemble modular suites together. We
> > already have the mechanism for "external" test-suite, it
would just
> > need to be first-class.
> > i.e. I'd like to clone the test-suite, which would get me only the
> > infrastructure but no test to run, and then easily say: "clone
these
> > test-suite and make them available: llvm, Halide, etc." which
would
> > clone them from separate repositories. And then list the available
> > suite and quick runs over chosen ones.
> >
> > Just some thoughts...
>
> As a longer-term goal, this sounds really nice.
>
Sounds a lot like a package manager.

-- Sean Silva

>
>  -Hal
>
> >
> > --
> > Mehdi
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
>
> --
> Hal Finkel
> Assistant Computational Scientist
> Leadership Computing Facility
> Argonne National Laboratory
> _______________________________________________
> 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/20160226/f6ed45f6/attachment.html>

Am 27.02.2016 um 05:32 schrieb Sean Silva via llvm-dev:
>>> i.e. I'd like to clone the test-suite, which would get me only
the
>>> infrastructure but no test to run, and then easily say: "clone
these
>>> test-suite and make them available: llvm, Halide, etc." which
would
>>> clone them from separate repositories. And then list the available
>>> suite and quick runs over chosen ones.
>>>
>>> Just some thoughts...
>>
>> As a longer-term goal, this sounds really nice.
>
> Sounds a lot like a package manager.
That's just a small part of a package manager, namely the dependency and 
the download aspects.

Package managers also do indirect dependencies, dependencies that vary 
from version to version, and the ability to validate some downloaded 
blob against a given dependency requirement, i.e. they require a 
reliable download infrastructure, or at least a general convention how 
to find libraries and how to calculate a hash to verify that they are 
what they claim to be.