Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.nntp4.net!news.hispagatos.org!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Jai kadam Newsgroups: linux.debian.maint.python Subject: Re: Playwright version bump and testing Date: Sat, 06 Dec 2025 22:50:01 +0100 Message-ID: References: X-Original-To: Roland Mas , debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Dec 6 21:45:27 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.199 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=2, LDO_WHITELIST=-5, MONOTONE_WORDS_2_15=1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-pf1-x436.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Forwarded-Encrypted: i=1; AJvYcCVmVUNwhgBR5V2as3hKVmW1f8T0zErwtUJm/dyf+o/FQoisGoAAfvgWfOGyFHYg05OMoJUk8/qiuIrE0GOa@lists.debian.org X-Gm-Message-State: AOJu0YyHwfqU8vHBVmKlyDngrMDkaCtYRBEJ6vKnNkL7UsixI/YNBKPB LrmOLDW8KlP3Bb0pg5F1ciL7QOJQ479ARCw+dnWDYyVG6202vLb/mWl+MXQ1DUeEAuv5p0h0IQ8 FCQWphfknrPG7mDTmN7uIzKuehJROolO92g== X-Gm-Gg: ASbGncs/nZ0zfnP87QeyPEldtAV5pRimhGW1rRt1TqYs8eCc1vd/dh5j41jnTU0ULFf Vrt9hU0tciNhmzOcpFEO/yj5lfEEKj+/rBEqU/OCZ/Up6bYcGRQLb7F2P2dAwv5YcQmmFr5/f0G +Y1JmYY2DcG+bBv+PF5Ts061TZbTsTd9H9QUkONqrCL9MJGH0jYiKSUZ1BRQ90eqMIsYkMmzhwr AzHaUC2PeU2WaIzBbtdKqvrCxFWhlvDCrWYdFu2VTjG48aWwtv4P5XpSAazGxbEuLMNlRJT7Y+m tKGkzq1W/ebiy31d7ynpRtPIJEaY4Q== X-Google-SMTP-Source: AGHT+IFM+IpEgYjxfqMMVJmVxzyYZ0JgYV8HrmoHW8FVDANpTFCduzcrL3GUYsv7KIvZziPI0hb0KA8gkUYqjrDWdDU= X-Received: by 2002:a05:7022:3885:b0:11b:a8e3:847d with SMTP id a92af1059eb24-11e0315ee1bmr1797778c88.10.1765057505831; Sat, 06 Dec 2025 13:45:05 -0800 (PST) MIME-Version: 1.0 X-Gm-Features: AQt7F2qa8N5gYz---eJHM0EUC-BRwZSb1b1fntErzTFyActHMU0Zqekz5kS5kDU Content-Type: multipart/alternative; boundary="000000000000a4ae3e06454f7966" X-Mailing-List: archive/latest/23494 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAJcuXACSAuWUCGU-4iiuLda29FU+hhr=M0QzMKV99J+R2BKXDg@mail.gmail.com Approved: robomod@news.nic.it Lines: 189 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 7 Dec 2025 03:14:54 +0530 X-Original-Message-ID: X-Original-References: <744bafde-3b8d-48d2-bf66-78c2ebea436e@debian.org> Xref: csiph.com linux.debian.maint.python:17258 --000000000000a4ae3e06454f7966 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, 6 Dec, 2025, 11:18=E2=80=AFpm Roland Mas, wrot= e: > Le 06/12/2025 =C3=A0 14:39, Jai kadam a =C3=A9crit : > > > > On Sat, 6 Dec, 2025, 6:49=E2=80=AFpm Roland Mas, wro= te: > >> Le 06/12/2025 =C3=A0 05:46, Jai kadam a =C3=A9crit : >> > 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 t= he > 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/buil= d; > 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 th= e > time for it yet. I use it daily though. > So i tried many things, the latest this i tried was to override the dh auto test command and add -s -vv flags to the command and it didnt work either i thought i you give some more info but nah no luck Can you try to clone https://salsa.debian.org/jvk_here/python-playwright/ and run gbp build not gwh that would tell if there is some problem with my machine :/ Thank you > --000000000000a4ae3e06454f7966 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, 6 Dec, 2025, 11:18=E2=80= =AFpm Roland Mas, <lolando@debian.= org> wrote:
=20 =20 =20
Le 06/12/2025 =C3=A0 14:39, Jai kadam a =C3=A9crit=C2=A0:
=20


On Sat, 6 Dec, 2025, 6:49=E2=80=AFpm Roland Mas, <lolando@debian.org= > wrote:
Le 06/12/2025 =C3=A0 05:46, Jai kadam a =C3=A9crit=C2=A0:
> 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, whic= h is a separate
testsuite).

Noted , so we have to build package everytime ?= =C2=A0
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/gw= h). 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.


So i tried man= y things, the latest this i tried was to override the dh auto test command = and add -s -vv flags to the command and it didnt work either i thought i yo= u give some more info but nah no luck

Can you try to clone https://salsa.debian.org/jvk_here/python-playwrigh= t/
and run gbp build not gwh that would tell if = there is some problem with my machine :/

<= div dir=3D"auto">Thank you
--000000000000a4ae3e06454f7966--