Bug#930487: lintian: use GitLab caching of test packages to speed up test suite CI
[changing subject to match updated bug title]
Hi Felix,
> On Mon, Jun 17, 2019 at 4:03 PM Chris Lamb <lamby@debian.org> wrote:
> We used filesystem timestamps for a while, but the standard resolution
> (1 sec) was not granular enough. AFAIR, we now generate everything
> every time.
By "filesystem timestamps" here are you referring to comparing the
timestamp of each generated test package and its source? If so, I am
unclear why one second was not enough to determine whether a *developer*
had changed something under "t/".
> We could probably skip the generation of test packages if they are
> already present and nothing in t/ has changed.
Indeed, but that is (roughly) what this entire bug report is about.
> > But 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
>
> Artifacts may work, but uploading them separately without a dependency
> scheme seems to invite other problems. […]
Hm, I think you may have been accidentally misled about how the Gitlab
CI build stages — there would be no upload whatsoever. I am therefore
unsure how to effectively and productively respond to your remarks,
alas. :(
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org 🍥 chris-lamb.co.uk
`-
Reply to: