Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #17255

Re: Playwright version bump and testing

From Roland Mas <lolando@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Playwright version bump and testing
Date 2025-12-06 18:50 +0100
Message-ID <LZ4zU-QjJ-3@gated-at.bofh.it> (permalink)
References <LYSp3-IiN-5@gated-at.bofh.it> <LZ0mB-NBU-5@gated-at.bofh.it> <LZ4zU-QjJ-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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.

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Playwright version bump and testing Jai kadam <jaivkadam@gmail.com> - 2025-12-06 05:50 +0100
  Re: Playwright version bump and testing Carsten Schoenert <c.schoenert@t-online.de> - 2025-12-06 06:50 +0100
  Re: Playwright version bump and testing Roland Mas <lolando@debian.org> - 2025-12-06 14:20 +0100
    Re: Playwright version bump and testing jvk <jaivkadam@gmail.com> - 2025-12-06 15:00 +0100
    Re: Playwright version bump and testing Roland Mas <lolando@debian.org> - 2025-12-06 18:50 +0100
      Re: Playwright version bump and testing Jai kadam <jaivkadam@gmail.com> - 2025-12-06 21:10 +0100
      Re: Playwright version bump and testing Jai kadam <jaivkadam@gmail.com> - 2025-12-06 22:50 +0100
        Re: Playwright version bump and testing Roland Mas <lolando@debian.org> - 2025-12-07 20:00 +0100
          Re: Playwright version bump and testing Jai kadam <jaivkadam@gmail.com> - 2025-12-07 20:00 +0100

csiph-web