Path: csiph.com!pasdenom.info!usenet.goja.nl.eu.org!2.eu.feeder.erje.net!feeder.erje.net!news.szaf.org!fu-berlin.de!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: Roland Mas Newsgroups: linux.debian.maint.python Subject: Re: Playwright version bump and testing Date: Sat, 06 Dec 2025 18:50:02 +0100 Message-ID: References: X-Original-To: Jai kadam , debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Dec 6 17:48:13 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-1.599 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HTML_MESSAGE=2, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, REMOVEDOT=3] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 Content-Type: multipart/alternative; boundary="------------G7ka09VVyidBMgBu916md2d6" MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr X-Mailing-List: archive/latest/23491 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/c1929e3a-71be-483f-8c4a-65e29c2245a8@debian.org Approved: robomod@news.nic.it Lines: 157 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 6 Dec 2025 18:47:53 +0100 X-Original-Message-ID: X-Original-References: <744bafde-3b8d-48d2-bf66-78c2ebea436e@debian.org> Xref: csiph.com linux.debian.maint.python:17255 This is a multi-part message in MIME format. --------------G7ka09VVyidBMgBu916md2d6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Le 06/12/2025 à 14:39, Jai kadam a écrit : > > > On Sat, 6 Dec, 2025, 6:49 pm Roland Mas, wrote: > > Le 06/12/2025 à 05:46, Jai kadam a écrit : > > Hello, > > I have bumped the playwright version from 1.55.0 to 1.56.0 the > build > > was successful. > > https://salsa.debian.org/jvk_here/python-playwright/ > > > > How should i test the package cause there is no debian/tests/ > > Hi Jai, > > Hello! > > > > The first step would be to remove the "override_dh_auto_test:" > line in > debian/rules. I inserted it so that the package would skip its > testsuite > as a preliminaly packaging effort, but it needs to be fixed. So > remove > that line, re-run the build, see what breaks and fix that until > nothing > breaks at all (and then we'll go on to debian/tests, which is a > separate > testsuite). > > > Noted , so we have to build package everytime ? > I mean it will be very time consuming . > There is no other option? :) pbuilder caches the downloads, so builds are not that long. On my 5-year-old workstation, it took some time on the initial try because of the downloading of build-depends, but it now takes less than a minute on subsequent runs. If it's still too long: I've been working on an abstraction layer to gbp called gwh (see https://salsa.debian.org/lolando/gwh). It automates many of the tasks for users of the gbp workflow, and adds some others. In this case, what I'd do is run gwh --shell-on-failure, which would set up the build then try it; once the build has failed you'll have a shell open inside the chroot, and you can then iterate running commands without the full build. For instance, you'd run "cd /build/python-playwright-1.55.0+ds/.pybuild/cpython3_3.14_playwright/build; python3.14 -m pytest tests", see where it breaks, fix it, and iterate. Roland. PS: I intend to push gwh to Debian proper sometime, just haven't found the time for it yet. I use it daily though. --------------G7ka09VVyidBMgBu916md2d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Le 06/12/2025 à 14:39, Jai kadam a écrit :


On Sat, 6 Dec, 2025, 6:49 pm Roland Mas, <lolando@debian.org> wrote:
Le 06/12/2025 à 05:46, Jai kadam a écrit :
> Hello,
> I have bumped the playwright version from 1.55.0 to 1.56.0 the build
> was successful.
> https://salsa.debian.org/jvk_here/python-playwright/
>
> How should i test the package cause there is no debian/tests/

Hi Jai,
Hello!


The first step would be to remove the "override_dh_auto_test:" line in
debian/rules. I inserted it so that the package would skip its testsuite
as a preliminaly packaging effort, but it needs to be fixed. So remove
that line, re-run the build, see what breaks and fix that until nothing
breaks at all (and then we'll go on to debian/tests, which is a separate
testsuite).

Noted , so we have to build package everytime ? 
I mean it will be very time consuming .
There is no other option? :)

pbuilder caches the downloads, so builds are not that long. On my 5-year-old workstation, it took some time on the initial try because of the downloading of build-depends, but it now takes less than a minute on subsequent runs.

If it's still too long: I've been working on an abstraction layer to gbp called gwh (see https://salsa.debian.org/lolando/gwh). It automates many of the tasks for users of the gbp workflow, and adds some others. In this case, what I'd do is run gwh --shell-on-failure, which would set up the build then try it; once the build has failed you'll have a shell open inside the chroot, and you can then iterate running commands without the full build. For instance, you'd run "cd /build/python-playwright-1.55.0+ds/.pybuild/cpython3_3.14_playwright/build; python3.14 -m pytest tests", see where it breaks, fix it, and iterate.

Roland.

PS: I intend to push gwh to Debian proper sometime, just haven't found the time for it yet. I use it daily though.

--------------G7ka09VVyidBMgBu916md2d6--