#linuxcnc-devel Logs

Apr 29 2023

07:55 AM -!- #linuxcnc-devel mode set to +v by ChanServ
09:50 AM -!- #linuxcnc-devel mode set to +v by ChanServ
11:26 AM linuxcnc-build2: Build [#30](http://buildbot2.highlab.com/buildbot/#builders/20/builds/30) of `50-deb-uspace.debian-08-jessie-i386` 8completed with warnings.
11:56 AM linuxcnc-build: build #3519 of 4021.deb-jessie-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4021.deb-jessie-i386/builds/3519 blamelist: Sebastian Kuzminsky <seb@highlab.com>
11:56 AM linuxcnc-build: build #3515 of 4022.deb-jessie-amd64 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4022.deb-jessie-amd64/builds/3515 blamelist: Sebastian Kuzminsky <seb@highlab.com>
11:56 AM linuxcnc-build: build #3405 of 4020.deb-jessie-rtpreempt-amd64 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4020.deb-jessie-rtpreempt-amd64/builds/3405 blamelist: Sebastian Kuzminsky <seb@highlab.com>
11:57 AM linuxcnc-build: build #3406 of 4019.deb-jessie-rtpreempt-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4019.deb-jessie-rtpreempt-i386/builds/3406 blamelist: Sebastian Kuzminsky <seb@highlab.com>
01:54 PM linuxcnc-build2: Build [#716](http://buildbot2.highlab.com/buildbot/#builders/8/builds/716) of `30-dsc-uspace.debian-12-bookworm` 4failed.
01:59 PM linuxcnc-build2: Build [#829](http://buildbot2.highlab.com/buildbot/#builders/13/builds/829) of `00-checkin` 4failed.
02:52 PM seb_kuzm1nsky: ugh
02:53 PM seb_kuzm1nsky is now known as seb_kuzminsky
02:58 PM pere: hi
02:58 PM seb_kuzminsky: hi pere
04:52 PM linuxcnc-build2: Build [#717](http://buildbot2.highlab.com/buildbot/#builders/8/builds/717) of `30-dsc-uspace.debian-12-bookworm` 3completed successfully.
05:00 PM pcw-home: seb_kuzminsky: did you see my note about the busywait branch?
05:08 PM linuxcnc-build2: Build [#830](http://buildbot2.highlab.com/buildbot/#builders/13/builds/830) of `00-checkin` 3completed successfully.
05:14 PM linuxcnc-build: build #4866 of 1610.rip-stretch-rtpreempt-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1610.rip-stretch-rtpreempt-i386/builds/4866 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:17 PM linuxcnc-build: build #7688 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/7688 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:17 PM linuxcnc-build: build #9894 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9894 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:44 PM seb_kuzminsky: pcw-home: no, i missed it... was it here on irc?
06:25 PM pcw-home: I cant find it but basically I noticed the your busywait branch improves network latency but also seem to spread latency over more hal functions
06:27 PM pcw-home: I am still wondering how this happens, for example I have had tmax values of motion.command-handler be more than 250 usec even when motion is completely idle
06:28 PM pcw-home: (it normally takes no more than a fraction of a usec)
06:33 PM pcw-home: This does happen to some extent with the non-busywait branch (maybe up to 60 usec or so for
06:33 PM pcw-home: motion.command-handler)
06:46 PM linuxcnc-build2: Worker `checkin` is missing. It was seen last on Sat Apr 29 16:46:47 2023.
08:37 PM -!- #linuxcnc-devel mode set to +v by ChanServ
08:49 PM seb_kuzminsky: pcw-home: hmm, interesting...
08:50 PM seb_kuzminsky: i wonder if motion.command-handler has a little sleep in it somewhere, sleeping causes terrible latency with the kernel command-line arguments that busywait needs
09:00 PM seb_kuzminsky: cradek and i found a sleep bug in the busywait6 branch, it's fixed in busywait7, can you try that one?
09:30 PM pcw-home: This is with busywait7
09:31 PM pcw-home: I still wonder how motion.command-handler can have such high tmax values
09:32 PM pcw-home: even with the normal LinuxCNC versions
09:33 PM pcw-home: Its like the servo thread is still interruptable by things like video
09:34 PM pcw-home: (and its not just motion.command-handler, its all functions/components)
09:43 PM seb_kuzminsky: hmm
09:43 PM seb_kuzminsky: i'm not sure either, but thanks for the info