Re: shortening the git test suite

[Ricardo Wurmus <rekado@elephly.net>]

Hi Mark,

>>> I'm not sure what you mean by "build model", whether you are talking
>>> about the daemon interface or something else, but I think the changes
>>> could be confined to the Guix user interface.  A field could be added to
>>> <package>, somewhat similar to 'replacement', but pointing to a package
>>> object which runs tests, or perhaps a list of package objects.  The guix
>>> client could simply add the test packages to the list of derivations to
>>> build.  This could be inhibited via a "--no-tests" guix build option.
>>
>> A problem that would need solving is that tests often depend on the
>> build directory, which is different from what is installed (and ends up
>> in the store).  The build directory is lost.
>
> I suggested a solution to this problem in my paragraph immediately
> following the one you quoted above.  Did you see it?  Here it is again:
>
>   In typical cases where "make check" expects to be run from a fully built
>   source directory, the main package would typically produce a tarball of
>   the built source directory as an additional output.  The test package
>   would simply unpack this tarball and run "make check" in it.

Yes, I read it, but I misunderstood your suggestion regarding the
tarball.  This build directory output which would be used to continue
the build would likely not be reproducible as it contains files that are
not meant to be installed, such as logs with timestamps.  Is this okay?

--
Ricardo