#linuxcnc-devel Logs

Oct 09 2023

10:33 AM rigid: pere: just sent PR that should fix the segfaulting linuxcncrsh test
10:42 AM pere: great. hard to find?
10:42 AM rigid: pere: no. it's the segfault I found earlier. it's just the missing gcode-output file that confused me.
11:01 AM rigid: hooray! tests passing: https://github.com/LinuxCNC/linuxcnc/actions/runs/6458723586/job/17533015955?pr=2691
11:02 AM rigid: oh, but not the debian linter (of course)
11:46 AM pere: rigid: I noticed in your patch, "If "spindle" is omitted or -1, all spindles are selected.".
11:46 AM pere: In other parts of linuxcnc, I believe the first spindle is selected when no spindle is selected. Perhaps it is best to be consistent?
11:47 AM rigid: pere: I sticked to the original behaviour, didn't touch that.
11:47 AM rigid: but yeah, it should be consistent
11:48 AM Tom_L: starting with 0
11:50 AM rigid: Tom_L: it starts with 0 but -1 is reserved for "all spindles"
11:51 AM Tom_L: default should be 0 though
11:52 AM rigid: andypugh: any objection? otherwise i'd change it
11:53 AM rigid: i guess the main concern is that changing behaviour can affect existing scripts
11:55 AM Tom_L: that happened already when they went to multiple spindles
11:55 AM Tom_L: motion changed
11:55 AM Tom_L: motion.spindle went to spindle.0
11:55 AM Tom_L: etc
11:55 AM Tom_L: i think in 2.8
12:01 PM rigid: done: https://github.com/LinuxCNC/linuxcnc/pull/2691/commits/1256df8c60bf776e0d925cd279c22c4d2765348e
12:12 PM rigid: hm, interestingly "get tool_offset" returns 8 when running the test on my machine and -1 on github
12:57 PM andypugh: I think that there is an argument for M5 always turning off all spindles.
01:16 PM rigid: i'm not sure whats intuitive for the user. I didn't use it a lot, yet.
01:22 PM rigid: andypugh: I got an interesting new bug where "get TOOL_OFFSET" seems to return an unitialized value. It's -1 in rip-and-test and 1303257280 in package-arch (debian:bullseye). https://github.com/LinuxCNC/linuxcnc/actions/runs/6459867877/job/17536468398?pr=2691#step:8:2006
01:22 PM rigid: should I open an issue?
01:22 PM rigid: it seems to be beyond the linuxcncrsh scope
01:40 PM andypugh: Yes, open an issue. Though maybe look at the tool table (with a hex editor?) just to be sure it’s not an issue there.
01:44 PM rigid: linuxcnc currently outputs "emc/task/taskclass.cc 167: can't load tool table." during that test. does it still read a tool table?
02:02 PM pere: do you have a tool table to load?
02:03 PM andypugh: There isn’t one mentioned in the test iNI file, so I don’t think that it does need one.
02:04 PM rene-dev5: That error is sometimes normal, if the test doesn’t have a tooltable
02:04 PM rene-dev5: will look at the pr later, when I get home
05:35 PM andypugh: rigid: I don’t think that https://github.com/LinuxCNC/linuxcnc/pull/2691/commits/e3dd9f8250e24ba6f79cd8a108579d004eb980b1 is likely to be right, that looks like ttying to be specific about a random number.
05:36 PM andypugh: And if there is no tool table, I feel that a random number shouldn’t be “normal”
05:43 PM Tom_L: maybe 0 for current
07:17 PM linuxcnc-build: build #3505 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3505 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
07:21 PM Unterhaus_ is now known as Unterhausen
07:29 PM linuxcnc-build: build #3907 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3907 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
07:45 PM linuxcnc-build: build #3667 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3667 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
07:45 PM linuxcnc-build: build #10325 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10325 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:02 PM linuxcnc-build: build #3668 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3668 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:05 PM linuxcnc-build: build #3908 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3908 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:05 PM linuxcnc-build: build #3506 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3506 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:06 PM linuxcnc-build: build #10326 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10326 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:42 PM linuxcnc-build: build #3669 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3669 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:43 PM linuxcnc-build: build #3909 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3909 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:43 PM linuxcnc-build: build #3507 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3507 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
08:45 PM linuxcnc-build: build #10327 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10327 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
09:22 PM linuxcnc-build: build #3508 of 1660.rip-buster-python3 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3508 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
09:31 PM linuxcnc-build: build #3910 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3910 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
09:51 PM linuxcnc-build: build #3670 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3670 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
09:51 PM linuxcnc-build: build #10328 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10328 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
10:38 PM linuxcnc-build: build #3509 of 1660.rip-buster-python3 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3509 blamelist: Phillip Carter <phillc54@users.noreply.github.com>
11:06 PM linuxcnc-build: build #10329 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10329 blamelist: Phillip Carter <phillc54@users.noreply.github.com>