On Sun, 7 Dec, 2025, 12:13 am Jai kadam, <[email protected]> wrote:
> > > On Sat, 6 Dec, 2025, 11:18 pm Roland Mas, <[email protected]> wrote: > >> Le 06/12/2025 à 14:39, Jai kadam a écrit : >> >> >> >> On Sat, 6 Dec, 2025, 6:49 pm Roland Mas, <[email protected]> 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. >> > The problem is not downloading it just kind of froze for like more that > 20mins after printing the last test line > >> 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). >> > Wow that sounds great (altough it also sounds like the current state of > web devlopment , the abstraction on top of abstractions :) ) > >> 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. >> > Actully the problem is not that it's failing, the problem is that it freezes Thats sounds like a better workflow :) i will try > >> 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. >> > > >
