Path: csiph.com!news.mixmin.net!weretis.net!feeder8.news.weretis.net!news.usenet.ovh!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: PICCA Frederic-Emmanuel Newsgroups: linux.debian.maint.python Subject: Re: pybuild autopkgtest Date: Fri, 14 Mar 2025 13:40:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Mar 14 12:33:10 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-2.896 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 Dkim-Filter: OpenDKIM Filter v2.10.3 zmtaout05.partage.renater.fr 31C02A00F4 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.8.15_GA_4652 (ZimbraWebClient - FF136 (Linux)/8.8.15_GA_4652) Thread-Topic: pybuild autopkgtest Thread-Index: xPaa989hx4BR1RHjA86WHuVSPfhyXg== X-Virus-Status: Clean X-Renater-Ptge-Spamstate: clean X-Renater-Ptge-Spamcause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddufedtkeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecutffgpfetvffgtfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefkjghfufggtgfgofhtsehtjegttdiitdejnecuhfhrohhmpefrkfevveetucfhrhgvuggvrhhitgdqgfhmmhgrnhhuvghluceofhhrvgguvghrihgtqdgvmhhmrghnuhgvlhdrphhitggtrgesshihnhgthhhrohhtrhhonhdqshholhgvihhlrdhfrheqnecuggftrfgrthhtvghrnhepleefkeeujefgjeeigefgffffudegheefgfeffeethfetkedtiedvhfeijeeifefgnecukfhppedutddrvdehgedrvdegtddrudegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpedutddrvdehgedrvdegtddrudeghedphhgvlhhopeiishhtohhrvgdqsgefqddtuddvrdhprghrthgrghgvrdhrvghnrghtvghrrdhfrhdpmhgrihhlfhhrohhmpehfrhgvuggvrhhitgdqvghmmhgrnhhuvghlrdhpihgttggrsehshihntghhrhhothhrohhnqdhsohhlvghilhdrfhhrpdhnsggprhgtphhtthhopedvpdhrtghpthhtohepfihrrghrseguvggsihgrnhdrohhrghdprhgtphhtthhopeguvggsihgrnhdqphihthhhohhnsehlihhsthhsrdguvggsihgrnhdrohhrgh X-Mailing-List: archive/latest/22899 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/1120871038.77351934.1741954644346.JavaMail.zimbra@synchrotron-soleil.fr Approved: robomod@news.nic.it Lines: 25 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Fri, 14 Mar 2025 13:17:24 +0100 (CET) X-Original-Message-ID: <1120871038.77351934.1741954644346.JavaMail.zimbra@synchrotron-soleil.fr> X-Original-References: <8734ff28a2.fsf@page> <608783598.77286970.1741950523683.JavaMail.zimbra@synchrotron-soleil.fr> <974218039.77306937.1741952574790.JavaMail.zimbra@synchrotron-soleil.fr> Xref: csiph.com linux.debian.maint.python:16782 > Making sure the installed code works. I expect the same :) > But also you should understand that what you want to do is very different > from running the test suite, as you explicitly don't want to install deps > needed for running it. I want to run the same test suite (which is most often provided by the upstream in order to test the package), during the build and as installed. but @builddep@ are not the dependency in order to run the test as installed but during the build. I need to check that my python- dependencies and the specific tests dependencies is a working subset of @builddep@ for these tests. Am I clear ? > That doesn't check that the installed code also works, and also it only > runs when the package is built, not later, e.g. when deps are updated. > None of this is specific to Python, both "build-time tests" and > "autopkgtests" exist in other packages, and it's also useful to have > autopkgtests run build-time tests there. I agreed that sometime running the same test during the build and as-installed is our best option. Fred