I completely agree - bookworm is about to freeze, and while smallish updates can go in for a couple of months (April?), we need this iteration between bookworm and our users that takes time. Once bookworm is released, that is mostly it, and we cannot release what we have in testing atm.
The only concern from my side is that a change motivated by bookworm may interfere with what is perfectly working on the current stable bullseye. Thank you, Sebastian! Steffen > Gesendet: Mittwoch, 04. Januar 2023 um 13:19 Uhr > Von: "Rod Webster" <r...@vehiclemods.net.au> > An: "EMC developers" <emc-developers@lists.sourceforge.net> > Betreff: Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy, > qtvcp, and more! > > It has to be tested on Bookworm because once it becomes the Debian release > version in a few short months, Linuxcnc is deployed with it. Bullseye does > not have the linuxcnc-uspace package the tests use. > > I must say it's great to see some testing on Bullseye. So much of the GUI's > are broken. Hats off to the QTplasmac guys. They always seem to pass my > testing! > > Rod Webster > *1300 896 832* > +61 435 765 611 > Vehicle Modifications Network > www.vehiclemods.net.au > > > On Wed, 4 Jan 2023 at 22:09, Hans Unzner <hansunz...@gmail.com> wrote: > > > Really great, thank you! > > > > However, I have some annotations: > > - You could mention that the tests need to be run as sudo (at least for > > it only worked so) and need Python >= 3.8 > > - The stderr file only shows something like "+ su --pty -c 'linuxcnc > > /usr/share/doc/linuxcnc/examples/sample-configs/sim/gmoccapy/lathe_configs/lathe_C.ini' > > > > testrunner" > > - For the configs which show an error message as window (like the > > gmoccapy config you attached) - is there another way to check if all > > tests have passed except looking at all screenshots or stdout logs? > > > > And I wonder why you chose Bookworm over Bullseye. I think all the > > Gmoccapy configs would pass on Bullseye. > > > > > > Am 04.01.23 um 06:04 schrieb Sebastian Kuzminsky: > > > I wrote a test tool that installs linuxcnc-uspace.deb on a minimal > > > Debian Bookworm system, and launches each of our "sim" sample configs. > > > No big surprise, many of them don't work. > > > > > > The list of broken configs is: > > > * axis/iocontrolv2/owordm6-ui-ns.ini > > > * axis/lathe-fanucy/lathe-fanucy.ini > > > * axis/profile_axis.ini > > > * most of axis/orphans/* > > > * most of axis/remap/* > > > * axis/vismach/3axis-tutorial/3axis-tutorial.ini > > > * axis/vismach/rolfmill/rolfmill.ini > > > * craftsman/* > > > * most of gmoccapy/* > > > * most of qtvcp_screens/* > > > * most of gscreen/* > > > > > > If any of these are near and dear to you, please take a look. > > > > > > I've attached screenshots from a few that made it far enough to > > > display a window (many configs failed before displaying anything). > > > > > > > > > The test tool is here if anyone wants to check it out (at some point i > > > may try to integrate it with the buildbot): > > > > > > https://github.com/SebKuzminsky/linuxcnc-config-test > > > > > > > > > > > > > > > _______________________________________________ > > > Emc-developers mailing list > > > Emc-developers@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > > > _______________________________________________ > > Emc-developers mailing list > > Emc-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
