#linuxcnc-devel Logs

Jul 28 2017

12:49 AM seb_kuzminsky: i wonder if the buildbot will work building releases from github? probably?
12:51 AM seb_kuzminsky: i'll check back in the morning
02:25 AM linuxcnc-build: build #3218 of 1400.rip-wheezy-i386 is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/3218 blamelist: Sebastian Kuzminsky <seb@highlab.com>
02:37 AM linuxcnc-build: build #5058 of 1200.rip-lucid-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/5058 blamelist: Sebastian Kuzminsky <seb@highlab.com>
02:38 AM linuxcnc-build: build #5060 of 1306.rip-precise-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/5060 blamelist: Sebastian Kuzminsky <seb@highlab.com>
02:38 AM linuxcnc-build: build #2885 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/2885 blamelist: Sebastian Kuzminsky <seb@highlab.com>
02:42 AM linuxcnc-build: build #4269 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/4269 blamelist: Sebastian Kuzminsky <seb@highlab.com>
02:51 AM linuxcnc-build: build #5057 of 1300.rip-precise-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/5057 blamelist: Sebastian Kuzminsky <seb@highlab.com>
02:55 AM linuxcnc-build: build #5058 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/5058 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:01 AM linuxcnc-build: build #3420 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/3420 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:03 AM linuxcnc-build: build #3219 of 1403.rip-wheezy-amd64 is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/3219 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:10 AM linuxcnc-build: build #2734 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/2734 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:15 AM linuxcnc-build: build #3228 of 1405.rip-wheezy-armhf is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/3228 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:16 AM linuxcnc-build: build #5071 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/5071 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:19 AM linuxcnc-build: build #1685 of 1510.rip-jessie-rtpreempt-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1510.rip-jessie-rtpreempt-i386/builds/1685 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:21 AM linuxcnc-build: build #1687 of 1530.rip-jessie-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1530.rip-jessie-rtpreempt-amd64/builds/1687 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:34 AM linuxcnc-build: build #73 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/73 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:35 AM linuxcnc-build: build #1685 of 1500.rip-jessie-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1500.rip-jessie-i386/builds/1685 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:36 AM linuxcnc-build: build #1686 of 1520.rip-jessie-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1520.rip-jessie-amd64/builds/1686 blamelist: Sebastian Kuzminsky <seb@highlab.com>
03:39 AM linuxcnc-build: build #73 of 1630.rip-stretch-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1630.rip-stretch-rtpreempt-amd64/builds/73 blamelist: Sebastian Kuzminsky <seb@highlab.com>
04:03 AM linuxcnc-build: build #262 of 1540.rip-jessie-armhf is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1540.rip-jessie-armhf/builds/262 blamelist: Sebastian Kuzminsky <seb@highlab.com>
04:03 AM linuxcnc-build: build #5078 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5078 blamelist: Sebastian Kuzminsky <seb@highlab.com>
08:43 AM Tom is now known as Guest30590
08:45 AM tomfoolery: Hi - I have a proposed change to glcanon.py and want to make sure i follow the right process - should I start by creating an "issue" first?
09:24 AM tomfoolery: i have cloned master and created a local branch and committed changes with -s, how do i upload this branch in order to make a pull request or get geedback?
09:29 AM jepler: tomfoolery: no need to create an issue. create a pull request.
09:38 AM tomfoolery: ok - so if i create a pull request - how to i reference my patch? i am not sure how to upload the branch/changes i have created locally
09:41 AM jepler: you will create a fork of linuxcnc, make your change on a branch within your fork, push that branch to your fork, and then create the pull request
09:42 AM jepler: https://help.github.com/articles/about-forks/ https://help.github.com/articles/creating-a-pull-request-from-a-fork/
09:45 AM tomfoolery: Got it - ok - so i need to reclone from my fork, recreate the branch, push the branch then issue a pull request?
09:45 AM tomfoolery: thank you
09:45 AM jepler: that is the simplest way for a new user of git.
09:46 AM jepler: there are more complicated things you can do, but it's probably easier for you to do that than for me to talk you through the commandline operations
09:47 AM tomfoolery: i am ok with the command lines - all i am doing is in a terminal window - no worries.
09:48 AM jepler: a git clone can have more than one "remote". You could add your fork as a remote in your existing clone https://help.github.com/articles/adding-a-remote/
09:49 AM jepler: and then you would push your changes to that specific remote https://help.github.com/articles/pushing-to-a-remote/
09:52 AM tomfoolery: whoo hoo - my first pull request
09:53 AM tomfoolery: i am cts1085 in github - in the future i will logon to iirc using the same login name
09:53 AM jepler: congratulations and thank you
10:00 AM jepler: does this specifically affect configurations where there is a "-" in the GEOMETRY?
10:05 AM tomfoolery: no. it keeps the '-' in GEOMETRY but it only impacts when you have more than one rotational axis specified in GEOMETRY for example in my case the GEOMETRY is AXZ-B
10:05 AM tomfoolery: this is not an issue unless you have more than one occurance of A or B or C such as AB, BC, CB, CA, etc.
10:06 AM jepler: configs/sim/axis/axis_9axis.ini has GEOMETRY = XYZABCUVW so it should be affected?
10:06 AM tomfoolery: I found that when axis read the ini file the geometry field was -BZXA
10:06 AM tomfoolery: yes - the sim would be impacted
10:07 AM tomfoolery: i was able to reproduce my problem using the sim axis_9axis when i changed the order to have XZ rotate around A
10:09 AM jepler: here's what I did before applying the patch: start up that sim config, home, move every axis away from the origin (e.g., MDI G0 X1Y1Z1U2V2W2A15C45 / B30), then move W up and down (e.g., G0 W0 / G0 W4 / G0 W2)
10:09 AM jepler: and then I looked whether the W motion was perpendicular to the tool
10:09 AM jepler: .. and this appeared to work fine
10:09 AM jepler: is there some other testing I should perform to see a problem?
10:10 AM tomfoolery: the code only reacts to moves to A B C - so moving W would not do anything
10:10 AM tomfoolery: in the sim - out of the box - B is a locking axis so you cannot jog it
10:10 AM jepler: yes, so I moved it with MDI G0 B30
10:12 AM tomfoolery: right and B should rotate around Y so the tool should tilt left
10:13 AM tomfoolery: issuing a G0 A45 should then rotate around the Z axis counter-clockwise
10:13 AM jepler: In axis_9axis, the kinematics are designed so that UVW move in "the coordinate system of the tool", so if the tool cone is in the right orientation, then the plot of a "W" motion will go through the centerline of the cone
10:14 AM jepler: so if there was a problem with applying the tool rotation I expected to observe it by setting all the rotations to nonzero and then moving "W"
10:14 AM jepler: (for instance, if the tool were pointing wrong by 90 degrees, then the line of motion wouldn't be through the cone at all)
10:15 AM tomfoolery: so - in the sim with XYZ all being specified - i am not sure my scenario will appear - in my case i do not have a "Y" axis - I only have XZAB
10:15 AM tomfoolery: it is a modified mill based on a lathe
10:16 AM tomfoolery: but i am using mill coordinates since the first rotational axis is parallel to the X axis or the bed of the lathe and my spindle is actually mounted on a rotational axis around "Z"
10:17 AM tomfoolery: i do not think my change is going to impact the sim - at least during my testing i did not see a negative side effect.
10:18 AM tomfoolery: I just did a G0 A45 B30 and then a G0 W-2 and the cone moved thru its centerline
10:22 AM jepler: OK, I looked more carefully and without your change my test *DOES* show a problem
10:22 AM jepler: and with your change the problem goes away
10:22 AM jepler: so I understand now and I think your change is right
10:22 AM tomfoolery: Awesome!
10:22 AM jepler: I guess for some choices of angle it is less obvious than others
10:23 AM jepler: (could these angular moves be any more irritatingly slow in axis_9axis!)
10:23 AM jepler: A90 B30 is even more clearly wrong before your change, let me try one last time *WITH* your change
10:28 AM jepler: I bet there's another bug here
10:28 AM tomfoolery: jepler - thank you for your quick response and feedback!
10:28 AM tomfoolery: where?
10:29 AM jepler: in the rotation code
10:29 AM jepler: suppose there's a "-" applied to a linear axis letter
10:29 AM jepler: so that "g" gets e.g., X-ZA
10:29 AM jepler: when the "-" is seen, "sign" is negated
10:29 AM jepler: when "Z" is seen, nothing happens
10:30 AM tomfoolery: in my case there is AXZ-B
10:30 AM jepler: when "A" is seen, the rotation is applied with "sign" of -1
10:30 AM tomfoolery: Ah
10:30 AM tomfoolery: Yes - you are correct - because the while loop does not reset "sign" if a non-rotational letter is found
10:31 AM tomfoolery: need case XYZUVW to reset sign = 1
10:31 AM jepler: yup
10:32 AM tomfoolery: btw - since you merged my pull request - should I "delete" my branch?
10:32 AM jepler: it's fine to delete your branch now
10:34 AM jepler: if you feel like it, can you look into this? I have to go AFK
10:34 AM jepler: thanks again for your first contribution!
10:35 AM seb_kuzminsky: tomfoolery: hi, welcome, and thanks for your patch!
10:35 AM tomfoolery: I will look into this - now that i have completed one round - doing another will help to cement the process
10:36 AM seb_kuzminsky: 2.7.11 is on its way to glo with jepler's gcode error fix and andypugh's carousel fix
10:36 AM seb_kuzminsky: tomfoolery: is this your first time using github? first time contributing to open source software?
10:37 AM seb_kuzminsky: you obviously have experience with programming
10:38 AM tomfoolery: i have a lot of history with programming but have not done anything material in years. Yes - first time with github & open source
10:38 AM seb_kuzminsky: that's great
10:39 AM seb_kuzminsky: i've got to step away for a bit, just wanted to say hi
10:40 AM linuxcnc-build: build #2212 of 1903.clang-wheezy-amd64 is complete: Failure [4failed apt-get-update install-missing-build-dependencies compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1903.clang-wheezy-amd64/builds/2212 blamelist: Tom Schneider <cts@cs2corp.com>, Jeff Epler <jepler@unpythonic.net>
11:29 AM KGB-wlo: push to master branch: http://linuxcnc.org/
11:29 AM ChanServ changed topic of #linuxcnc-devel to: http://linuxcnc.org | Latest release: 2.7.11 | (this channel is logged by the c-log robot)
11:29 AM linuxcnc-build: build #5079 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5079 blamelist: Tom Schneider <cts@cs2corp.com>, Jeff Epler <jepler@unpythonic.net>
11:30 AM jepler: linuxcnc-build: force build --branch=master 0000.checkin
11:30 AM linuxcnc-build: build forced [ETA 1h46m19s]
11:30 AM linuxcnc-build: I'll give a shout when the build finishes
11:30 AM seb_kuzminsky: that failure looks like the buildbot's internet connection blinked out right as one of the slaves was trying to run apt-get update
11:34 AM jepler: seb_kuzminsky: thanks for .11 and sorry for my role in making it necessary
12:03 PM seb_kuzminsky: jepler: it's fine
12:04 PM seb_kuzminsky: your bug pales in comparison to my 2.7.4, .5, .6 fiasco (or whatever the numbers were)
12:05 PM jepler: seb_kuzminsky: long since forgotten, I'm sure
12:08 PM seb_kuzminsky: yes
12:08 PM seb_kuzminsky: i only think about it every time i feel awkward about anything
12:35 PM Tom_L: is this 2.7.11 still wheezy?
12:36 PM seb_kuzminsky: 2.7.11 is available on all the distros that earlier 2.7 releases have been available on
12:36 PM Tom_L: is the iso up yet?
12:36 PM jepler: no
12:36 PM seb_kuzminsky: there's no new iso yet
12:36 PM Tom_L: i'll likely update the debian way...
12:36 PM Tom_L: ok
12:36 PM seb_kuzminsky: but "apt-get update && apt-get dist-upgrade" from an old iso install will upgrade it
12:36 PM Tom_L: just in time for the weekend :D
12:37 PM Tom_L: right
12:44 PM Tom_L: maybe after 300+ package updates...
12:59 PM linuxcnc-build: Hey! build 0000.checkin #5080 is complete: Success [3build successful]
12:59 PM linuxcnc-build: Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5080
01:00 PM Tom_L: yay! sim comes up 2.7.11
01:54 PM Tom_L: and cuts parts as expected...
01:59 PM jepler: Tom_L: thanks for the report
02:05 PM jepler: uploading "-r8" isos new, should be updated with 2.7.11 but I didn't even try them to check :_
02:05 PM jepler: :)
02:06 PM Tom_L: wasn't gonna burn one but i could test it if you like
02:06 PM Tom_L: that's stretch, right?
02:07 PM jepler: they'll take 15-20 minutes to upload
02:07 PM jepler: yes this is the stretch .iso
02:07 PM Tom_L: i can't use it so i may pass
02:10 PM jepler: that's fine, no worries
02:25 PM Tom_L: ok glad that's over
02:25 PM Tom_L: ran ddrescue on the dead hdd for 3 days, harvested some things but got the new ssd up and running 2.7.11 now
02:27 PM Tom_L: backups are awesome :)
02:27 PM jepler: -r8 isos uploaded
02:27 PM Tom_L: link? i misplaced the dev link
02:28 PM Tom_L: nm, found it..
02:39 PM jepler: you weren't going to try it remember?
02:41 PM Tom_L: :)
02:41 PM Tom_L: burning now
02:43 PM Tom_L: loading
02:48 PM Tom_L: servo thread 745183
02:48 PM Tom_L: but the -i386 iso works
02:49 PM jepler: no reason to expect its rt performance to be any different than earlier iterations
02:49 PM jepler: did linuxcnc identify as 2.7.11 ?
02:49 PM Tom_L: yes
02:50 PM Tom_L: just loaded the sim
02:50 PM jepler: great, thanks
02:50 PM Tom_L: least i can do :D
10:19 PM Tom_shop is now known as Tom_shop3
10:21 PM Tom_shop3 is now known as Tom_shop