Bug#930487: lintian: speed up test suite CI

["Chris Lamb" <lamby@debian.org>]

Chris Lamb wrote:

> > Gitlab has a support for saving various parts of a successful build
> > for the next one. I believe the idea is that we would build the test
> > packages and then push them to this cache re-using them on any subsequent
> > test runs.
[..]

The naïve solution here might be to save & restore debian/test-out
between runs. However, I'm not sure whether this would result in
changes to the testsuite itself resulting in the changed versions
being tested, resulting in all manner of false positive and false
negatives.

Felix, any insight here? There's currently no magical command in the
fancy test runner of yours that will rebuild any missing or otherwise
changed test packages is there…?

Or, before we implement that, am I asking an XY question? In other
words, are we barking up the wrong tree here and what we need to do is
use different GitLab CI stage altogether and pass "artifacts" around
instead?

  https://docs.gitlab.com/ee/ci/caching/index.html#cache-vs-artifacts

I'm not entirely sure, alas. (Although that magical command might be
useful locally...)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-