On Sun, Nov 24, 2024 at 7:42 AM Shengjing Zhu <[email protected]> wrote:
> On Sun, Nov 24, 2024 at 8:31 PM Simon Josefsson <[email protected]> > wrote: > > > > Hi. > > > > I never understood what > > the 'test_the_archive' job does or what it helps with. All failures I > > have ever encountered are cought by the standard Salsa pipeline (and it > > catches many other mistakes). Does 'test_the_archive' test for anything > > that the normal Salsa pipeline would not catch? I never understood > > that. > > The normal salsa CI is for QA for the package itself. > 'test_the_archive' is something like ratt, but designed with cache and > efficiency (well, currently broken and half implemented). But they are > two different things. > > The normal salsa CI is good for "go programs", but I'm not convinced > it's good for the large amount of "go libraries", which are just based > on the standard template from dh-make-golang. > We have a significant amount of packages that build both a library as well as a program. I think running both both provides significant value for a large number of packages! -- regards, Reinhard
