Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Re: Enabling salsa-ci on all Debian Python Team repos Date: Fri, 23 Sep 2022 04:40:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Sep 23 02:31:37 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-ua1-f41.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: ACrzQf1UWzsr7rdmDxYXP3lyjE+Cp14t50ebnq3HqKlV22tUfMk8frCb 4kmMfjL0vV/jfl0VAbfwDe8pFNfztygBzVwfJLD20rGz X-Google-SMTP-Source: AMsMyM6JycPVKqvwhoQZxLlKEuQAdkc/m2quKI88s0iYqhRfaJvMkVnQ4iQnFVAVmzkQNIFj+jWj83CekX3zeB52j5U= X-Received: by 2002:a05:6130:c13:b0:39f:58bb:d51c with SMTP id cg19-20020a0561300c1300b0039f58bbd51cmr2866042uab.104.1663900274704; Thu, 22 Sep 2022 19:31:14 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/20334 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXx1w+p_0i4WXmqzx1u_Jf5q+Ea=+Ef73wka9OZ-WCV25w@mail.gmail.com Approved: robomod@news.nic.it Lines: 41 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 22 Sep 2022 22:30:48 -0400 X-Original-Message-ID: X-Original-References: <6f483545-27cb-0d05-d813-50c482284e6c@t-online.de> Xref: csiph.com linux.debian.maint.python:14492 > Well but that's the whole point of automated testing. There's no *need* > to do it locally if it's already done by Salsa for you. What is already > automated and working pretty well is: > > - amd64 build > - i386 build > - source build > - autopkgtest > - blhc > - lintian > - piuparts > - reprotest > - arm64 crossbuild > > That's a pretty time consuming list of things to go through for a human! > > The only work left to be done on your machine is a binary build to see > if the packages look good, perhaps some specific manual testing [1], > source build and upload. Isn't that better? sure its better, now let's assume something in those tests fails: how do you debug it and fix it? you still need to repeat it locally = you wasted time. In conclusion, you're no only proposing a technical change (add CI to all our packages), but also a workflow change (push to salsa before an upload). experience dictates that's never a good idea, and in such an heterogeneous team like ours, it's simply not gonna give the fruits you think it will. I still think it's a waste of time, and addition of emails that we're going to simply ignore (or not receive at all, if you're not subscribed to tracker.d.o, wihch is suspect is the vast majority of team members), but if the majority of the core contributors want it, sure go ahead -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi