Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead
> > I was looking at which of the Salsa CI jobs take longest and consume
> > most resources and stumbled across
> > https://salsa.debian.org/python-team/packages/graph-tool
> >
> > The build uses more memory than available on a Salsa CI runner, and it
> > has never, and will never build.
>
> I don't think that's an accurate way to describe the status of graph-tool.
>
> The problem with graph-tool is that it needs a lot of memory per CPU.
>
> But I managed to make it work in most cases (see the commits and the
> uploads I did) by making some calculations in debian/rules which
> adjust the parallelism according to available memory. If those
> calculations do not work in Salsa CI, we might better figure out why,
> instead of saying "will never build".
Thanks Santiago for the additional information. I updated the MR
description now at
https://salsa.debian.org/python-team/packages/graph-tool/-/merge_requests/1,
and I suggest we merge it now to stop CI failures, and re-enable it
later if/when the CI is fixed.
Having a regression testing system that is not passing and cannot
detect any regressions is not productive and wastes resources.
Reply to: