Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #17051

Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead

From Otto Kekäläinen <otto@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead
Date 2025-09-09 02:40 +0200
Message-ID <LsUyR-dTZ7-3@gated-at.bofh.it> (permalink)
References <LouMG-aQ1V-19@gated-at.bofh.it> <Lovpo-aQjG-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


> > 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.

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Otto Kekäläinen <otto@debian.org> - 2025-08-27 22:20 +0200
  Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Andrey Rakhmatullin <wrar@debian.org> - 2025-08-27 22:30 +0200
      Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Soren Stoutner <soren@debian.org> - 2025-08-27 22:50 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Carsten Schoenert <c.schoenert@t-online.de> - 2025-08-28 14:20 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Andrey Rakhmatullin <wrar@debian.org> - 2025-08-28 15:30 +0200
      Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Soren Stoutner <soren@debian.org> - 2025-08-27 23:00 +0200
  Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-08-27 23:00 +0200
    Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Otto Kekäläinen <otto@debian.org> - 2025-09-09 02:40 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-09-09 03:20 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-09-09 03:40 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-09-09 15:10 +0200
          Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Soren Stoutner <soren@debian.org> - 2025-09-09 19:20 +0200

csiph-web