#linuxcnc-devel Logs

Jan 07 2023

01:00 AM linuxcnc-build: build #9575 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9575 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:11 AM linuxcnc-build2: Build [#105](http://buildbot2.highlab.com/buildbot/#builders/2/builds/105) of `50-deb-uspace.debian-12-bookworm-amd64` 4failed.
03:20 AM linuxcnc-build2: Build [#110](http://buildbot2.highlab.com/buildbot/#builders/23/builds/110) of `50-deb-uspace.debian-11-bullseye-amd64` 4failed.
03:25 AM linuxcnc-build2: Build [#116](http://buildbot2.highlab.com/buildbot/#builders/3/builds/116) of `50-deb-uspace.debian-10-buster-amd64` 4failed.
05:29 AM pere: in my hal component python script, linuxcnc.stat().ini_filename is empty while I expect it to have a value. what did I do wrong?
07:20 AM pere: seb_kuzminsky: is there enough man-power to limit direct master push to a select few?
07:22 AM TurBoss: hello pere i tried and this works :... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/a812407d71f240699309fffdca1a801d9d90189f>)
07:23 AM pere: TurBoss: when did you run it?
07:24 AM pere: I suspect I might run into a race, where the value is not yet available.
07:25 AM TurBoss: just booted linuxcnc and ran in as python script not a comp... ops not the same
07:25 AM TurBoss: *it
07:28 AM pere: TurBoss: <URL: https://github.com/LinuxCNC/linuxcnc/compare/master...petterreinholdtsen:linuxcnc:comp-mqtt-client?expand=1 > is the code I am testing.
07:31 AM TurBoss: loading it as comp from hal gives and empty line too
07:33 AM pere: any idea why?
07:33 AM TurBoss: nop
07:36 AM pere: I also ran into a problem with hal pins showing up too late.
07:38 AM pere: the hal file try to connect to the new mqtt-client pins, but they get created after the hal file is parsed.
10:57 AM linuxcnc-build2: Build [#118](http://buildbot2.highlab.com/buildbot/#builders/3/builds/118) of `50-deb-uspace.debian-10-buster-amd64` 8completed with warnings.
12:14 PM linuxcnc-build2: Build [#107](http://buildbot2.highlab.com/buildbot/#builders/2/builds/107) of `50-deb-uspace.debian-12-bookworm-amd64` 8completed with warnings.
12:23 PM linuxcnc-build2: Build [#112](http://buildbot2.highlab.com/buildbot/#builders/23/builds/112) of `50-deb-uspace.debian-11-bullseye-amd64` 8completed with warnings.
01:18 PM linuxcnc-build: build #6167 of 1510.rip-jessie-rtpreempt-i386 is complete: Failure [4failed configure-debian-control] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1510.rip-jessie-rtpreempt-i386/builds/6167 blamelist: Sebastian Kuzminsky <seb@highlab.com>
01:22 PM chris is now known as Guest1270
02:58 PM linuxcnc-build: build #2468 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2468 blamelist: Sebastian Kuzminsky <seb@highlab.com>, CMorley <chrisinnanaimo@hotmail.com>, petterreinholdtsen <pere-github@hungry.com>
04:16 PM linuxcnc-build: build #2361 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/2361 blamelist: Sebastian Kuzminsky <seb@highlab.com>, CMorley <chrisinnanaimo@hotmail.com>, petterreinholdtsen <pere-github@hungry.com>
04:41 PM pere: anyone got time to help me with the mqtt component?
04:45 PM Tom_L: mqtt?
04:48 PM pere: yes.
04:49 PM pere: I'm working on a user space component, and ran into some ordering issues with HAL.
04:49 PM Tom_L: never written a comp file
04:51 PM pere: <URL: https://github.com/LinuxCNC/linuxcnc/compare/master...petterreinholdtsen:linuxcnc:comp-mqtt-client?expand=1 > show the code in question, at least for me.
04:51 PM pere: <URL: https://github.com/LinuxCNC/linuxcnc/commit/0299042bf3d68ff734780d2099e78dd291573e0e > might have a higher chance of showing up for others.
04:52 PM Tom_L: i can see the 1st one
04:52 PM pere: the problem at hand is that the test code fail to work because the mqtt-client code to enable the pins are executed after the hal pins should be connected to the nets/signals. this of course fail as the pins are missing.
04:52 PM pere: how can I use pins created by a user component in the hal file where the user component is loaded?
04:53 PM pere: the problematic lines in the hal file are flagged with FIXME.
04:54 PM linuxcnc-build: build #9579 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9579 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:00 PM pere: my next plan is to create a REST API component to allow extern programs to fetch HAL values using http.
05:00 PM Tom_L: doubt i'd be much help with that
05:02 PM pere: I assume there is some sequencing mechanism I have not discovered yet, to ensure component pins are available before they are used.
05:02 PM Tom_L: http://linuxcnc.org/docs/2.4/html/hal_comp.html#r1_7
05:02 PM Tom_L: old but so far i found that
05:02 PM Tom_L: pin_hame parater_name
05:03 PM Tom_L: from 2.4 docs so it may not be a thing now... i dunno
05:04 PM Tom_L: http://linuxcnc.org/docs/2.5/html/hal/comp.html#_convenience_macros
05:04 PM Tom_L: still in 2.5
05:05 PM pere: suspect <URL: http://linuxcnc.org/docs/devel/html/hal/comp.html > is the latest version.
05:05 PM pere: I wrote my component using python, so it is no .comp file.
05:06 PM Tom_L: wouldn't the end result be a comp file?
05:06 PM Tom_L: whether written in c python etc
05:06 PM Tom_L: just stabbing in the dark here
05:09 PM pere: ah, found it. loadusr need -W for this to work.
05:09 PM pere: Tom_L: nope, the end result is a .py file. a comp file is converted to C and compiled (and to a man page and saved in docs/)
05:10 PM Tom_L: http://linuxcnc.org/docs/2.5/html/hal/halmodule.html
05:10 PM Tom_L: basic useage shows pin creation a bit different
05:14 PM Tom_L: may be the same thing written different, i don't know python
05:14 PM Tom_L: looking at line 68 on yours
05:14 PM Tom_L: and fwd
05:15 PM Tom_L: should those be listed first?
05:18 PM pere: line 68 of which file?
05:27 PM Tom_L: the first i think
05:28 PM Tom_L: https://github.com/LinuxCNC/linuxcnc/compare/master...petterreinholdtsen:linuxcnc:comp-mqtt-client?expand=1
05:29 PM Tom_L: just below the FIXME
05:39 PM pere: you lost me.
05:40 PM Tom_L: i was lost from the start.. carry on
06:46 PM -!- #linuxcnc-devel mode set to +v by ChanServ
08:34 PM linuxcnc-build2: Build [#133](http://buildbot2.highlab.com/buildbot/#builders/19/builds/133) of `10-rip.debian-08-jessie-i386` 4failed.
08:34 PM linuxcnc-build2: Build [#133](http://buildbot2.highlab.com/buildbot/#builders/22/builds/133) of `10-rip.debian-09-stretch-rtpreempt-i386` 4failed.
08:34 PM linuxcnc-build2: Build [#133](http://buildbot2.highlab.com/buildbot/#builders/12/builds/133) of `10-rip.debian-07-wheezy-amd64` 4failed.
08:43 PM linuxcnc-build2: Build [#146](http://buildbot2.highlab.com/buildbot/#builders/13/builds/146) of `00-checkin` 4failed.
08:46 PM linuxcnc-build: build #2469 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2469 blamelist: CMorley <chrisinnanaimo@hotmail.com>, andypugh <andy@bodgesoc.org>
08:46 PM -!- #linuxcnc-devel mode set to +v by ChanServ
10:08 PM linuxcnc-build: build #2362 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/2362 blamelist: CMorley <chrisinnanaimo@hotmail.com>, andypugh <andy@bodgesoc.org>