#linuxcnc-devel | Logs for 2018-10-19
Back
[00:05:45] -!- ve7it has quit [Remote host closed the connection]
[00:05:50] -!- ikcalB has quit [Quit: WeeChat 2.2]
[01:34:42] -!- KimK has quit [Ping timeout: 252 seconds]
[01:47:12] -!- KimK has joined #linuxcnc-devel
[03:04:09] -!- c-log has quit [Ping timeout: 252 seconds]
[03:06:20] -!- c-log has joined #linuxcnc-devel
[04:17:45] -!- rob_h has joined #linuxcnc-devel
[05:24:51] -!- c-log has quit [Ping timeout: 250 seconds]
[05:27:30] -!- c-log has joined #linuxcnc-devel
[06:01:00] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15c-morley pushed 4 new commits to 06qt5vcp_py2: 02 https://github.com/LinuxCNC/linuxcnc/compare/1db965751e2d...94992d06213a
[06:01:00] -linuxcnc-github:#linuxcnc-devel- 13linuxcnc/06qt5vcp_py2 141840b87 15Chris Morley: qtvcp -fix spelling error with slider widget...
[06:01:00] -linuxcnc-github:#linuxcnc-devel- 13linuxcnc/06qt5vcp_py2 14baaf1cf 15Chris Morley: qtvcp -detect missing handler file and try to help...
[06:01:00] -linuxcnc-github:#linuxcnc-devel- 13linuxcnc/06qt5vcp_py2 148dc6e12 15Chris Morley: qtvcp -layout changes to blender
[06:07:06] <CMorley> andypugh:https://forum.linuxcnc.org/24-hal-components/35391-program-stops-executing-after-spindle-at-speed-reached#119067
[07:02:03] <jthornton> is that the same problem Loetmichal had yesterday on #linuxcnc?
[08:19:51] -!- c-log has quit [Ping timeout: 244 seconds]
[08:22:21] -!- c-log has joined #linuxcnc-devel
[09:15:39] -!- rob_h has quit [Ping timeout: 244 seconds]
[09:46:30] -!- jthornton has quit [Remote host closed the connection]
[10:20:54] -!- jthornton has joined #linuxcnc-devel
[10:21:05] -!- jthornton has quit [Remote host closed the connection]
[10:24:58] -!- jthornton has joined #linuxcnc-devel
[10:30:57] -!- Roguish has joined #linuxcnc-devel
[10:42:08] -!- c-log has quit [Ping timeout: 245 seconds]
[10:43:59] -!- c-log has joined #linuxcnc-devel
[13:32:02] -!- rob_h has joined #linuxcnc-devel
[14:53:35] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15dngarrett 04force-pushed 06dgarr/external_offsets from 14b546cfe to 14784db03: 02 https://github.com/LinuxCNC/linuxcnc/commits/dgarr/external_offsets
[14:53:35] -linuxcnc-github:#linuxcnc-devel- 13linuxcnc/06dgarr/external_offsets 14784db03 15Dewey Garrett: External Offsets: Axis coordinate offset hal pins...
[14:58:15] -!- ve7it has joined #linuxcnc-devel
[15:51:29] -!- ve7it has quit [Remote host closed the connection]
[15:53:04] -!- ve7it has joined #linuxcnc-devel
[16:01:30] -!- rob_h has quit [Ping timeout: 252 seconds]
[16:06:12] -!- rob_h has joined #linuxcnc-devel
[16:07:12] -!- jthornton has quit [Read error: Connection reset by peer]
[16:09:00] -!- JT-Shop has quit [Ping timeout: 252 seconds]
[16:24:03] -!- jthornton has joined #linuxcnc-devel
[16:24:05] -!- JT-Shop has joined #linuxcnc-devel
[16:30:35] -!- andypugh has joined #linuxcnc-devel
[16:49:45] <jepler> forum update, yay/ugh
[16:50:46] <jepler> and we should be back up after that brief interruption
[16:51:21] -!- dgarr has joined #linuxcnc-devel
[16:51:40] <dgarr> linuxcnc-build: force build --branch=dgarr/external_offsets 0000.checkin
[16:52:58] -!- dgarr has parted #linuxcnc-devel
[17:19:46] -!- jthornton has quit [Ping timeout: 244 seconds]
[17:20:00] -!- JT-Shop has quit [Read error: Connection reset by peer]
[17:21:42] -!- jthornton has joined #linuxcnc-devel
[17:21:49] -!- JT-Shop has joined #linuxcnc-devel
[18:10:10] <andypugh> mozmck: What do you think? Merge external_offsets (well tested) and reverse-run (less well tested but harder to activate by accident) and aim to release by new-yea?
[18:11:04] <jthornton> yippie!
[18:11:21] <andypugh> If I knew what the release manager did I would offer to take over :-)
[18:18:01] -!- dgarr has joined #linuxcnc-devel
[18:18:09] <dgarr> linuxcnc-build: force build --branch=master 0000.checkin
[18:20:04] <andypugh> Hi dgarr
[18:20:46] <andypugh> I tried cherry picking that single commit last night, on top of master. Built cleanly and passed all tests.
[18:21:16] <andypugh> I am not sure the actual commit needs much more work, unless you have tweaked it.
[18:22:38] <andypugh> What I haven’t quit managed to do yet is put https://github.com on top of master + ext_off (which a guy on the forum seems to need(
[18:25:26] <dgarr> i don't understand the runtests failure as i cannot replicate, suspect problem using linuxcncrsh on the single buildbot machine: rip-jessie-rtprempt-amd64
[18:25:38] <dgarr> ref: http://buildbot.linuxcnc.org
[18:26:08] <dgarr> so testing latest master build to see if runtests fail repeats on rip-jessie-rtpreempt-amd64
[18:26:44] <andypugh> runtests defintely passes on my local stretch-uspace
[18:27:34] <andypugh> Having read what you said more carefully, I now understand what you are trying to do
[18:28:33] <dgarr> the commit b546cfe01135 passed on all buildbot machines, the commit 784db03355d5 only changed the commit message yet failed on one machine
[18:29:41] <andypugh> Is there a way to see what happened? Locally there is a .failed file (I think) but I don’t know if we can get there on the buldbot
[18:30:37] <dgarr> you can find the log using the buildbot grid: http://buildbot.linuxcnc.org
[18:32:26] <dgarr> the first failure (the log references are now gone) had one odd/unexpected failure, the log above (on the repeat build) has multiple failures with many of them showing timeout using linuxcncrsh -- my guess is there is some "bad" system state due to original linuxcncrsh timeout or related problem
[18:33:04] <dgarr> if failures repeat on the current master branch build, i would suggest rebooting therip-jessie-rtpreempt-amd64 machine
[18:34:58] <dgarr> expected completion (buildbot waterfall) shows 2hrs21minutes or 18:55 mdt
[19:09:04] <dgarr> found log page for the failing machine: http://buildbot.linuxcnc.org It shows rip-jessie-rtpreempt-amd64 runtests fails on last three builds including latest rerun of master at commit 0cab36566e8d -- so i think the problem is with the buildbot machine
[19:10:29] <rene_dev_> andypugh can you confirm that PR 512 works?
[19:16:03] <dgarr> The first failing build (build #2264) for rip-jessie-rtpreempt-amd64 occurred after running 169 tests (out of 224) with messages "USRMOT: ERROR : command timeout" ref: http://buildbot.linuxcnc.org
[19:25:59] <andypugh> rene_dev_: I can’t. I am trying to find a way to create a patch for it on top of master/external_offsets for a guy on the forum running that software with a machine that shows the problem but who is unfamilar with git (but is runing a RIP that Dewey helped him make)
[19:26:35] <rene_dev_> just push everything into master :D
[19:26:48] <rene_dev_> but I guess cherrypicking is what you are looking for
[19:26:49] <andypugh> I got as far as https://patch-diff.githubusercontent.com by manually editing URLs
[19:27:44] <andypugh> But that patch doesn’t take on master (got won’t even try, vanilla patch has a minor issue that I need to margetool)
[19:27:55] <andypugh> (git won’t evem try)
[20:07:31] <hazzy-m> I think something must be wrong with the bot that builds the docs, the python interface docs have not been updated since 2018-10-18 22:49:08 MDT ...
[20:29:54] -!- rob_h has quit [Ping timeout: 252 seconds]
[20:53:48] <andypugh> dgarr: Moses said “if there are no stong objections” and it’s been _hours_ witout any :-)
[20:56:28] <andypugh> The way I see it is that external-offsets has had _no_ error reports for 18 months with at least 6 users that I know of (and the guy complaining about a TP bug was a new one who mafe it seven)
[21:00:10] <andypugh> So given that Multispindle is already merged and raised 3 bugs in a week, I think that running EO in parallel with waiting for MS so settle down makes sense. This is mainly because my incompetence seems to have introduced a “wait and see” period that other changes might as well join in on.
[21:20:55] <rene_dev_> andypugh yeah, why not merge it. I agree
[21:21:42] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[21:23:16] <hazzy-m> it's one of the best tested feature branches. Go for it!
[21:26:27] <hazzy-m> I think maybe it would have been best to have tagged/released 2.8 when it was extremely stable a few weeks ago, but now might as well take advantage to merge what we can before the release
[21:48:54] <dgarr> seb_kuzminsky: when you have a chance, could you look at the buildbot slave: rip-jessie-preemptrt-amd64 -- the runtest failures seem to indicate a problem with it alone -- maybe it needs a reboot . more info in channel logs^^
[22:42:37] -!- Tom_itx has joined #linuxcnc-devel
[22:45:55] -!- Tom_itx has quit [Client Quit]
[22:51:59] -!- Tom_itx has joined #linuxcnc-devel
[22:55:04] -!- Tom_itx has quit [Client Quit]
[23:14:19] -!- dgarr has quit [Quit: Leaving.]
[23:19:24] <mozmck> The only thing that bothers me a little reading the docs for external offsets is that there is no deceleration if external offsets are enabled and you hit a soft limit either while jogging or during a coordinated move.
[23:21:43] <mozmck> But I guess that is probably not much of an issue as long as you know about it and are careful.
[23:21:56] <andypugh> It might not be ideal, but if EO is not enabled (default) then that won’t be seen, and no coordinated move should hit a soft limit anyway?
[23:22:10] <mozmck> true.
[23:22:24] <andypugh> Anyway, 0422 here,,
[23:22:31] -!- andypugh has quit [Quit: andypugh]