Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= 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: Tue, 09 Sep 2025 02:40:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Sep 9 00:37:31 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-109.51 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no X-Gm-Message-State: AOJu0YxF6tS+qUqz2bc00EaIR1R0G+M0UTD0c5VhqZBNqB2WS9gbyvNg vBe3dwcHMLM+2cBqjcSCYVEmv3w2xIKt0VhDOKHo2t5Djh29wnYA135uyA6iLEwurNjNOHWXgnC wYximrbrmv+n60Z8ottPXtNRXEgtXqME= X-Google-SMTP-Source: AGHT+IHtYtCQFskBJpvmFgihCVA5GA4N43wttEMk3EZX/G05VPMeguVQ5zIQsuM5GNdY6c/1A9OilTS7r+L3NwYmCNM= X-Received: by 2002:a05:6102:4b85:b0:519:534a:6c4f with SMTP id ada2fe7eead31-53d2434aadbmr3335833137.33.1757378232300; Mon, 08 Sep 2025 17:37:12 -0700 (PDT) MIME-Version: 1.0 X-Gmail-Original-Message-ID: X-Gm-Features: AS18NWCpxWZ1x09I2doa3CAy_EZmg959z6aAtPAKpoR36dFxz_C_7NE44QPiNzY Content-Type: text/plain; charset="UTF-8" X-Debian-User: otto X-Mailing-List: archive/latest/23231 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAOU6tADMqDE=tUYdktZ+55J8QpwaoicgKJnRPZB7Q5vr_izaFQ@mail.gmail.com Approved: robomod@news.nic.it Lines: 25 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, Aayush Raj , Jerome Benoit X-Original-Date: Mon, 8 Sep 2025 17:36:35 -0700 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:17051 > > 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.