#linuxcnc-devel | Logs for 2016-06-20

Back
[00:01:21] <linuxcnc-build> build #4242 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/4242 blamelist: Jeff Epler <jepler@unpythonic.net>
[00:01:21] <linuxcnc-build> build #4254 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4254 blamelist: Jeff Epler <jepler@unpythonic.net>
[00:19:03] <linuxcnc-build> build #4243 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/4243 blamelist: Andrew Kyrychenko <amkyrychenko@gmail.com>
[00:35:17] <linuxcnc-build> build #4255 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4255 blamelist: Andrew Kyrychenko <amkyrychenko@gmail.com>
[00:57:47] <linuxcnc-build> build #4244 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/4244 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[01:21:03] <linuxcnc-build> build #4256 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4256 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[07:13:05] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15lacquer opened pull request #81: sampler: Update fifo-depth and fifo-full pins even when sampler is not enabled (06master...06master) 02https://github.com/LinuxCNC/linuxcnc/pull/81
[07:23:51] <jepler> trasz_: not that I'm aware of
[07:26:32] <jepler> seb_kuzminsky: looks like the precise-amd64 buildbot needs to be bounced...?
[07:37:52] <KGB-linuxcnc> 03Rushabh Loladia 05master 53cde63 06linuxcnc 10src/hal/components/sampler.c sampler: Update fifo-depth and fifo-full even if sampler (RTAPI) is not-enabled. * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=53cde63
[07:37:52] <KGB-linuxcnc> 03Jeff Epler 05master 086abd9 06linuxcnc 10src/hal/components/sampler.c sampler: fix indentation, remove redundant comments * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=086abd9
[07:39:07] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15cradek closed pull request #81: sampler: Update fifo-depth and fifo-full pins even when sampler is not enabled (06master...06master) 02https://github.com/LinuxCNC/linuxcnc/pull/81
[07:59:19] <linuxcnc-build> build #4245 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/4245 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:04:51] <linuxcnc-build> build #2404 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/2404 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:05:07] <linuxcnc-build> build #4243 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/4243 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:05:28] <linuxcnc-build> build #2404 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/2404 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:06:08] <linuxcnc-build> build #2603 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/2603 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:06:11] <linuxcnc-build> build #1914 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/1914 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:07:04] <linuxcnc-build> build #3454 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/3454 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:10:27] <linuxcnc-build> build #872 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/872 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:10:37] <linuxcnc-build> build #872 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/872 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:10:39] <linuxcnc-build> build #2070 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/2070 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:10:56] <linuxcnc-build> build #872 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/872 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:11:33] <linuxcnc-build> build #872 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/872 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:11:42] <jepler> *egg on face*
[08:12:55] <linuxcnc-build> build #2438 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/2438 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:12:55] <linuxcnc-build> build #4257 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4257 blamelist: Rushabh Loladia <rushabh.loladia@gmail.com>, Jeff Epler <jepler@unpythonic.net>
[08:15:15] <KGB-linuxcnc> 03Jeff Epler 05master 19aaa6f 06linuxcnc 10src/hal/hal_lib.c hal: export hal_stream_writable * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=19aaa6f
[08:23:08] <rushabh> Thank you Jeff; It was my negligence. Will be more careful next time.
[08:24:55] <jepler> rushabh: in any case, congratulations on your first contribution to the project!
[08:25:56] <rushabh> Thank you ! :)
[08:27:01] <jepler> do you know about how to run our testsuite? After you ". scripts/rip-environment", just run "runtests" .. it takes several minutes to complete
[08:27:46] <jepler> you can also specify a list of tests to run by path, so that when you're working on a particular test failure you don't have to wait for all of them to run every time
[08:29:42] <rushabh> Ok, I'll try that out next time without fail.
[08:30:34] <jepler> You can see I didn't take my own advice in this case
[08:33:32] <linuxcnc-build> build #4246 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/4246 blamelist: Jeff Epler <jepler@unpythonic.net>
[08:48:03] <linuxcnc-build> build #4258 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4258 blamelist: Jeff Epler <jepler@unpythonic.net>
[09:38:16] <seb_kuzminsky> jepler: i bounced precise-amd64, thanks
[09:38:54] <jepler> seb_kuzminsky: thank you
[09:39:35] <seb_kuzminsky> it seems like github has really reduced the activation energy for new contributors
[09:39:45] <jepler> it is increasing my energy, though.
[09:39:52] <jepler> or, using my energy
[09:40:41] <jepler> signed-off-by requirement + unfamiliarity with git + initial pull request of 10 commits without SOB = hell for the potential contributor and for me when I try to help
[09:40:47] <jepler> (#33)
[09:41:17] <seb_kuzminsky> yeah :-
[09:41:30] <seb_kuzminsky> :-/
[09:42:08] <cradek> I think the existence of github helps us because contributors think it's not *our* fault they have to figure out git
[09:42:31] <seb_kuzminsky> good point
[09:42:39] <cradek> I think it normalizes that particular hell for new contributors
[09:43:15] <cradek> so that's a win for everyone (?)
[09:43:21] <seb_kuzminsky> and github has some pretty good git docs, https://help.github.com/
[09:43:39] <jepler> yes and no, signed-off-by is a weird requirement and the github UI will tell them that their commit can be merged even when it doesn't have SOB
[09:44:01] <jepler> "you have to rebase in a weird way and then ignore git's own advice that you probably should pull before pushing"
[09:44:40] <cradek> I like the way you handle that, by offering to do it and then asking them to ok your work
[09:44:56] <jepler> it seems like a good compromise.
[09:45:01] <jepler> as long as I maintain the energy to do it
[09:45:31] <seb_kuzminsky> does that weaken the legal mumbo jumbo behind it?
[09:45:38] <cradek> but yeah, editing your unpushed commit messages is a terrible task in git
[09:45:58] <cradek> seb_kuzminsky: we can't know that
[09:46:08] <jepler> editing your already-pushed commit messages is even worse, because even if you get the rebase right, git advises you to pull before pushing
[09:46:41] <cradek> and following that advice that would be a disaster
[09:48:22] <cradek> maybe we're wrong to require SOB, if it trades a potential future problem for real and serious ongoing irritations
[09:49:21] <seb_kuzminsky> that could be
[09:49:23] <jepler> creating a pull request is also good evidence of intent that their changes be included in the open source project under its license.
[09:49:44] <jepler> (I didn't start this conversation with the idea of relaxing or removing the SOB requirement)
[09:50:15] <seb_kuzminsky> could we formalize the PR part to do the work of the SOB part?
[09:50:38] <seb_kuzminsky> maybe by modifying CONTIRBUTING.md?
[09:50:48] <seb_kuzminsky> (and if so should we?)
[09:50:57] <jepler> you mean, the requirement becomes that *everything* goes through github PR?
[09:51:10] <seb_kuzminsky> no, i didnt intend that
[09:51:28] <seb_kuzminsky> just that things the come through github are assumed to be offered in good faith and with a proper license
[09:51:31] <cradek> let's back up - in what situations can I SOB someone else's commit?
[09:52:07] <cradek> "... or otherwise have the right to pass it on as an open-source patch"
[09:52:42] <cradek> so I think jepler could SOB a contributor's change (especially a first-time contributor) after simply asking
[09:53:00] <jepler> there are two questions here. One is "when do I have the right to add *my* SOB to someone else's patch" and "when do I have the right to add *someone else's* sob to their patch"
[09:53:00] <seb_kuzminsky> right, as himself, not as the author
[09:53:05] <cradek> yes
[09:53:21] <jepler> yes, I have been doing the latter, and that is probably not right
[09:53:23] <cradek> jepler: after asking; never
[09:53:50] <cradek> (IMO)
[09:53:55] <seb_kuzminsky> makes sense
[09:54:27] <jepler> you're right, I shouldn't have added someone else's SOB to a patch, just in order that the author and sob match
[09:54:39] <cradek> the DCOO part (c) is pretty explicit about this
[09:55:02] <jepler> but my intentions are good
[09:55:08] <cradek> is a pull request "provided directly to me"? probably, I guess
[09:55:24] <seb_kuzminsky> maybe take the new contributor's branch, add "SOB: Seb" and a brief comment saying "i got permission from the author in the comments of PR #123" or "i got permission verbally in IRC (http://zlog)"
[09:55:35] <cradek> jepler: oh of course
[09:57:56] <cradek> everything is fine, nothing is ruined, everyone continue operating in good faith
[09:58:39] <jepler> I wonder if, from a technical standpoint, we could write the hook that checks "SOB *or* PR"
[09:58:43] <jepler> we risk having a git that breaks when github does
[09:58:54] <jepler> if it were to go live to the internet to answer that question
[09:58:57] <jepler> so that's not a great idea
[10:00:33] <jepler> I'll modify my workflow so that I add my own SOB and we can revisit this later if needed.
[10:00:51] <cradek> that sounds perfect
[10:00:52] <seb_kuzminsky> thanks for helping all the new people, it really makes things feel vibrant in here
[10:01:02] <cradek> it sure does
[10:01:03] <jepler> Please help if you have the time and inclination
[10:01:21] <seb_kuzminsky> yes, i'll try to do better about that
[10:12:50] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #80: As pointed out by @cradek this was also reported on the old bug tracker: https://sourceforge.net/p/emc/bugs/130/... 02https://github.com/LinuxCNC/linuxcnc/issues/80#issuecomment-227163653
[10:15:05] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky commented on issue #80: ... Except for `G10 L2 R`. 02https://github.com/LinuxCNC/linuxcnc/issues/80#issuecomment-227164348
[10:15:55] <cradek> heh I had exactly the same thought
[10:16:08] <jepler> :-/ shatter my dreams of an easy solution
[10:16:15] <jepler> I appoint one of you two to write the test cases
[10:16:23] <lair82> Just curious, where do you guys find the time to do all this work on signing off and all the code work, all while maintaining your day to day stuff in life?
[10:16:27] <cradek> well the solution is still the same, you just have to find the quadrants correctly
[10:16:59] <cradek> lair82: who told you we maintain our day-to-day stuff in life?
[10:17:42] <lair82> Oooohhhhh, now I see, you guys eat, sleep, and breath Linuxcnc!
[10:17:43] <cradek> (the real answer for me is sometimes I have more time/energy and sometimes I have less time/energy and I just do my best)
[10:18:10] <cradek> lately I've had less, and these other guys are doing the hard work
[10:18:15] <jepler> yes, I agree with cradek's real answer. Right now is one of those times I have more energy to put into the project
[10:20:14] <lair82> We'll, I'd surely raise a cold beer, and give all you guys a firm pat on the back for all the work you guys put into this project, most times it just blows my mind how dedicated you guys are to this, that to most, is just a hobby
[10:20:19] <jepler> I've recently read some articles calling out "crusty old developers" like me for not being welcoming to new contributors, and so I'm also very consciously trying to turn over a new leaf about that.
[10:21:06] <jepler> thanks! the praise is always welcome. now if we could just open a separate area on github where you can write about something that worked correctly in the software and let you accomplish something meaningful to you..
[10:23:45] <lair82> I will honestly say, all 5 machines we have running now, have pushed almost every envelope in regards to linuxcnc, and you guys have come through with a solution for pretty much everything, Thank You, especially for dealing with my pain in the ^&* all this time. It truly is an amazing software, and the fact that it is all free, makes it even crazier.
[10:49:58] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 92b991a 06linuxcnc 10scripts/platform-is-supported Merge remote-tracking branch 'origin/2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=92b991a
[11:06:27] <jepler> cradek: with 5axiskins didn't we discover that trying to do the tool length offset in kinematics was not an ideal solution? http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a8baf11
[11:06:36] <jepler> "kins.9 document new pin: genhexkins.tool-offset JA"
[11:27:31] <cradek> yes because you want changing the tool length to give you new axis position(s) (no motion) and you can't do that at the kins layer. The comment about "to avoid joints jump change" makes it seem like there's a certain machine position where it's possible to change it, but I don't understand that part without more information (and I don't know what RTCP is)
[11:28:35] <cradek> (using W axis for tool length seems to be a good solution that works with our layering, in the cases I've studied)
[11:28:39] <jepler> http://www.coe.org/p/fo/et/thread=23400
[11:28:47] <jepler> > Rotary tool control point (RTCP) is the sum of pivot length (mechanical rotation axis to spindle face) and gage length (spindle face to tool control point)
[11:30:39] <cradek> ok so with RTCP the controlled point moves to stay on the tool tip, the setup we have with W tool lengths in many of our kinses
[11:31:00] <jepler> that is my superficial understanding
[11:32:01] <cradek> I don't understand how you could do that at the kins level (and change it during a program or with machine on)
[11:42:16] <cradek> ... because it seems like changing the tool length must change at least one world coordinate or at least one joint coordinate
[15:04:32] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15jepler created 06showcase (+1 new commit): 02https://github.com/LinuxCNC/wlo/commit/46c0f16ff420
[15:04:32] -linuxcnc-github:#linuxcnc-devel- 13wlo/06showcase 1446c0f16 15Jeff Epler: let's showcase users projects with linuxcnc...
[15:04:33] <KGB-wlo> push to showcase branch: http://wlo-test.highlab.com/showcase
[15:05:09] <jepler> I've been feeling that what's missing from our front page is some info about what people actually do with linuxcnc. take a look at this branch of the wiki and tell me if you think this is a good idea...
[15:06:35] <cradek> I love it
[15:08:14] <jepler> all we need is to be resolved to add new posts to it on a weekly-or-so basis
[15:09:28] <jepler> I'm not sure about positioning on the page. On a standard laptop screen (1280x600 browser area) news and showcase are both below the fold..
[15:10:53] <seb_kuzminsky> i like it too
[15:12:48] <jepler> afk
[15:12:59] <jepler> it crosses my mind that we should add community to the already-full nav bar at the top too
[15:13:14] <seb_kuzminsky> there should be a persistent and easy-to-find blurb (so not a post) telling people how to submit their machines (and projects?) to the showcase
[15:13:33] <cradek> community is already there
[15:13:35] <seb_kuzminsky> jepler: community is aleady in the navbar, no?
[15:13:41] <jepler> er oops
[15:13:43] <jepler> I mean, add showcase
[15:13:50] <jepler> but afk, it's coffe time!
[15:14:02] <seb_kuzminsky> if it's on the front page i dont think we need another link to it
[15:14:06] <seb_kuzminsky> ooh coffee
[15:14:28] <jepler> seb_kuzminsky: join us, I'll make everyone aeropress
[15:28:35] <seb_kuzminsky> jepler: just like with the posts, the links to old showcase posts is at the bottom of the "recent" list on the front page, i think that's enough
[15:35:16] <jepler> OK I'll stop sweating that
[15:41:03] <jepler> do you think "create an issue on our website's github" is a good (good enough) submission method?
[15:41:19] <cradek> well it's a super high bar
[15:41:33] <cradek> depends on whether you want a high bar
[15:41:58] <jepler> I don't know!
[15:43:47] <jepler> >>
[15:43:48] <jepler> Do you have a machine or project you'd like to see featured on the showcase?
[15:43:51] <jepler> Post it in the [forum's "show your stuff" section][forum] or create an issue on
[15:43:54] <jepler> our [website's github repository][github]. Submissions should consist of at
[15:43:57] <jepler> least one photo or video, a short explanation, and include a link to the forum
[15:44:00] <jepler> or a personal blog with more information.
[15:44:02] <jepler> (rather, "in" the showcase)
[16:25:13] <seb_kuzminsky> jepler: that's easier for submitters and more work for us (people who'd update the showcase blog), so it's probably good
[16:33:23] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master f4cdfa1 06linuxcnc 10scripts/platform-is-supported Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f4cdfa1
[18:05:11] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15nicokid commented on issue #33: Sorry but I I'm always confused with git. I looked at this link, here there is the old version:... 02https://github.com/LinuxCNC/linuxcnc/pull/33#issuecomment-227291215
[18:11:34] <KGB-linuxcnc> 03andypugh 05andypugh/JA14_multispindle 4c95e18 06linuxcnc 10(54 files in 14 dirs) Add support for multiple spindles * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4c95e18
[18:21:23] <seb_kuzminsky> hi andypugh
[18:23:32] <andypugh> Hi
[18:23:58] <andypugh> I like to pop in just before a push to see if it worked as expected
[18:24:13] <andypugh> Though I was too late today.
[18:30:35] <andypugh> I just made a minor change in my branch called “multispindle” What’s the command to push that change to andypugh/JA14_multispindle?
[18:31:56] <linuxcnc-build> build #2408 of 1403.rip-wheezy-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/2408 blamelist: andypugh <andy@bodgesoc.org>
[18:33:07] <linuxcnc-build> build #2408 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/2408 blamelist: andypugh <andy@bodgesoc.org>
[18:33:28] <linuxcnc-build> build #1918 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/1918 blamelist: andypugh <andy@bodgesoc.org>
[18:33:37] <andypugh> Oh Dear.
[18:34:17] <linuxcnc-build> build #4247 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/4247 blamelist: andypugh <andy@bodgesoc.org>
[18:34:53] <linuxcnc-build> build #4249 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/4249 blamelist: andypugh <andy@bodgesoc.org>
[18:35:28] <andypugh> It’s in a branch because it _will_ fail any tests with spindle pins in….
[18:36:08] <linuxcnc-build> build #3458 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/3458 blamelist: andypugh <andy@bodgesoc.org>
[18:38:41] <andypugh> How many compilation targets are there?
[18:46:13] <linuxcnc-build> build #2607 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/2607 blamelist: andypugh <andy@bodgesoc.org>
[18:46:55] <skunkworks> enough to give you a complex...
[18:55:57] <linuxcnc-build> build #2442 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/2442 blamelist: andypugh <andy@bodgesoc.org>
[18:55:59] <linuxcnc-build> build #876 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/876 blamelist: andypugh <andy@bodgesoc.org>
[19:01:53] <linuxcnc-build> build #876 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/876 blamelist: andypugh <andy@bodgesoc.org>
[19:02:02] <linuxcnc-build> build #2074 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/2074 blamelist: andypugh <andy@bodgesoc.org>
[19:06:13] <linuxcnc-build> build #876 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/876 blamelist: andypugh <andy@bodgesoc.org>
[19:07:16] <linuxcnc-build> build #876 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/876 blamelist: andypugh <andy@bodgesoc.org>
[19:07:16] <linuxcnc-build> build #4261 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4261 blamelist: andypugh <andy@bodgesoc.org>
[19:17:20] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15pippin88 commented on issue #79: Jeff,... 02https://github.com/LinuxCNC/linuxcnc/pull/79#issuecomment-227303373
[21:13:40] <jepler> hm, anyone here know how to use gmoccapy? In master branch, configs/sim/gmoccapy/gmoccapy.ini, the "max velocity" slider is stuck at 0.0 and won't budge...
[21:14:07] <jepler> 2.7 is OK, the slider goes up to 30 or maybe 552.756 (it shows two numbers)
[21:14:37] <jepler> I was trying to test gmoccapy a tiny bit before pushing pippin's change, but it just doesn't work for me to actually run a program :-/ but it's the same before his changes afaict
[21:15:22] <KGB-linuxcnc> 03Jeff Epler 05master 1910422 06linuxcnc Merge branch 'jepler/for-master/pippin88' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1910422
[21:15:45] <seb_kuzminsky> i've run gmoccapy once or twice, but it was a long time ago
[21:15:53] <seb_kuzminsky> and i only ran it a little bit
[21:16:49] <jepler> I did figure out how to touch off and edit offsets, so that is good
[21:17:04] <jepler> but I did a lot of "hover mouse and hope for tool tips" which is not so good for touchscreen users...
[21:17:31] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #33: Thanks for double checking. git can be tough for new users, and some of the ways we ask contributors to use git require even more knowledge. 02https://github.com/LinuxCNC/linuxcnc/pull/33#issuecomment-227319483
[21:21:21] <seb_kuzminsky> i just got this during "make -j20" in master: http://paste.debian.net/740452/
[21:21:24] <seb_kuzminsky> anyone seen it?
[21:25:02] <jepler> (what's pyui?)
[21:25:19] <seb_kuzminsky> i'd never heard of it until now
[21:25:31] <seb_kuzminsky> the directory's got 2 commits from cmorley
[21:25:50] <seb_kuzminsky> from about 6 months ago
[21:25:53] <jepler> seb_kuzminsky: I'm pretty sure that if I go looking for it I can find it :) try starting with a clean source directory and just invoke make with ../lib/python/pyui/panelui_spec.ini or ../lib/python/pyui/_panelui.ini
[21:26:38] <jepler> normally I am guessing the target for installing python files just above it in its submakefile gets invoked first by good fortune
[21:26:39] <seb_kuzminsky> yeah, don't spend your time on it, i'll look into it
[21:26:53] <jepler> the $(Q)mkdir just needs to be copied down into all the rules that copy files into that directory
[21:27:01] <jepler> and/or somebody could ream out our whole build system and we'd thank them
[21:27:04] <seb_kuzminsky> heh ok
[21:27:06] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15cradek closed pull request #77: Corrected gmoccapy typos (06master...06LCNCScreen) 02https://github.com/LinuxCNC/linuxcnc/pull/77
[21:27:18] <cradek> I did?
[21:27:29] <cradek> how on earth did I do that
[21:27:33] <KGB-linuxcnc> 03Jeff Epler 05master 68d7d86 06linuxcnc Merge remote-tracking branch 'origin/jepler/master/nicokid-stepconf' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=68d7d86
[21:27:33] <jepler> cradek: it's always you, because you do the pushes to githib
[21:27:33] <KGB-linuxcnc> 03Jeff Epler 05master a2b7244 06linuxcnc 10src/emc/usr_intf/stepconf/build_HAL.py stepconf: Always write postgui_call_list.hal * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a2b7244
[21:27:43] <cradek> oh
[21:27:51] <jepler> cradek: .. it looks at whose ssh key is used to perform the push that closes a bug or PR
[21:28:27] <cradek> magic comments say what to close?
[21:29:06] <seb_kuzminsky> yeah
[21:29:25] <seb_kuzminsky> err, in that case it was probably because the commits matched the commits in the PR
[21:29:47] <seb_kuzminsky> you can close issuses by saying "Closes #xxx" or "Fixes" or some variants of that
[21:30:30] <seb_kuzminsky> https://help.github.com/articles/closing-issues-via-commit-messages/
[21:32:36] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #77: Thank you for your contribution. Your improvements will be part of a future version of LinuxCNC. 02https://github.com/LinuxCNC/linuxcnc/pull/77#issuecomment-227321440
[21:33:19] <jepler> wow we have 41 closed pull requests over all time
[21:33:53] <seb_kuzminsky> what percentage of them were closed by you?
[21:34:18] <jepler> wellll
[21:34:23] <jepler> some were closed by cradek :)
[21:34:39] <cradek> bah
[21:38:19] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 9472866 06linuxcnc 10src/emc/usr_intf/pyui/Submakefile fix a parallel build problem with pyui * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9472866
[21:39:04] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15cradek closed pull request #71: Jepler/master/nicokid stepconf (06master...06jepler/master/nicokid-stepconf) 02https://github.com/LinuxCNC/linuxcnc/pull/71
[21:44:03] <KGB-wlo> push to showcase branch: http://wlo-test.highlab.com/showcase
[21:44:08] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15jepler 04force-pushed 06showcase from 1446c0f16 to 1494e8b97: 02https://github.com/LinuxCNC/wlo/commits/showcase
[21:44:09] -linuxcnc-github:#linuxcnc-devel- 13wlo/06showcase 141030259 15Jeff Epler: Add a github link in the footer
[21:44:09] -linuxcnc-github:#linuxcnc-devel- 13wlo/06showcase 14f04eb84 15Jeff Epler: tweak heading sizes...
[21:44:09] -linuxcnc-github:#linuxcnc-devel- 13wlo/06showcase 14999401f 15Jeff Epler: remove padding...
[21:44:41] <linuxcnc-build> build #2409 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/2409 blamelist: Jeff Epler <jepler@unpythonic.net>, pippin88 <pippin88@imagineant.com>
[21:45:26] <jepler> Running test: /home/buildslave/emc2-buildbot/wheezy-amd64/rip-wheezy-amd64/build/tests/halmodule.1
[21:45:29] <jepler> Note: Using POSIX non-realtime
[21:45:31] <jepler> hum I wonder what happened here
[21:45:34] <jepler> pass
[21:45:37] <jepler> *** /home/buildslave/emc2-buildbot/wheezy-amd64/rip-wheezy-amd64/build/tests/halmodule.1: FAIL: test run exited with 1
[21:45:40] <jepler> doesn't seem like the test is relevant to anything in those commits!
[21:48:41] <linuxcnc-build> build #4262 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4262 blamelist: Jeff Epler <jepler@unpythonic.net>, pippin88 <pippin88@imagineant.com>
[21:49:40] <jepler> any last thoughts before I make the showcase branch live?
[21:50:05] <seb_kuzminsky> i say go!
[21:51:51] <jepler> balms away
[21:52:00] <KGB-wlo> push to master branch: http://linuxcnc.org/
[21:52:02] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15jepler pushed 1 new commit to 06master: 02https://github.com/LinuxCNC/wlo/commit/1efb1a2a9d847beab5387c8734410b6314089196
[21:52:02] -linuxcnc-github:#linuxcnc-devel- 13wlo/06master 141efb1a2 15Jeff Epler: Merge branch 'showcase'
[21:52:12] <seb_kuzminsky> jepler: Jun 20 20:08:26 wheezy-amd64 kernel: [5966699.203276] hrtimer: interrupt took 12777005 ns
[21:52:17] <jepler> oh whoops, that turns out to be a trademarked mascara removal product
[21:52:40] <seb_kuzminsky> imma chalk it up to a VM timewarp glitch
[21:53:22] <jepler> oh whoops, missed some of the explanatory text
[21:53:26] <seb_kuzminsky> jepler: aww, you didnt make it say "fork us on github", like the cool kids do
[21:56:00] <KGB-wlo> push to master branch: http://linuxcnc.org/
[21:56:08] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15jepler pushed 1 new commit to 06master: 02https://github.com/LinuxCNC/wlo/commit/5a412cf505d05947d8e3acb71244b0e28c9f577f
[21:56:08] -linuxcnc-github:#linuxcnc-devel- 13wlo/06master 145a412cf 15Jeff Epler: fix the submitting-to-showcase text, as workshopped on IRC
[21:56:17] <Roguish> seb_kuziminsky and jepler. I briefly saw a note that the build server ran out of disc space. Does it need additional discs? Tell me where and to whom to send my donation $$$
[21:56:44] <seb_kuzminsky> i appreciate the offer
[21:56:53] <seb_kuzminsky> but i just took care of it
[21:57:31] <Roguish> Ok, thanks. just remember if you need $$ help, just speak up.
[21:57:33] <seb_kuzminsky> turns out i had some old VMs lying around on the buildserver that were no longer useful, i removed them and gave the space to the buildmaster and we're goog agin :-)
[21:57:48] <seb_kuzminsky> thanks Roguish, i very much appreciate it
[22:02:20] <seb_kuzminsky> jepler: it looks funny that Showcase is singular
[22:02:33] <seb_kuzminsky> http://linuxcnc.org/showcase/ says "All Showcase"
[22:02:41] <seb_kuzminsky> maybe it should be Showcases?
[22:03:07] <seb_kuzminsky> maybe i should have said this when you asked for comments, instead of after the merge?
[22:07:14] <KGB-wlo> push to master branch: http://linuxcnc.org/
[22:07:23] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15SebKuzminsky pushed 1 new commit to 06master: 02https://github.com/LinuxCNC/wlo/commit/2f028b355f93572e0dc986a08b6e573ef715d32c
[22:07:23] -linuxcnc-github:#linuxcnc-devel- 13wlo/06master 142f028b3 15Sebastian Kuzminsky: make it "Showcases", plural, where appropriate
[22:07:49] <jepler> You know, earlier I was going to praise jekyll
[22:08:06] <jepler> but then I had to work around a bug when I tested adding a second showcase entry https://github.com/Shopify/liquid/pull/456
[22:10:12] <seb_kuzminsky> huh, there's some really cool stuff in forum/show-you-stuff
[22:13:55] <jepler> I am tempted to do the captive nut one
[22:14:09] <jepler> that one looks super nice!
[22:15:01] <seb_kuzminsky> wow, yeah
[22:15:35] <seb_kuzminsky> the Showcase rules currently only accept machines that demonstrate how cool and flexible linuxcnc is
[22:15:56] <seb_kuzminsky> that nut project makes me want to relax the rules to also accept cool things made with machines running linuxcnc
[22:16:18] <jepler> umm maybe the rule I wrote doesn't mean what I think it meant
[22:16:38] <jepler> I think that things made on the machines count
[22:16:51] <jepler> it's "you can buy this board for $99" or "you can buy this mill for $9,999" that I don't want
[22:18:20] <seb_kuzminsky> agree 100%
[22:18:21] <jepler> so help me write the words I mean!
[22:18:28] <seb_kuzminsky> the wooden flowers one is cool too
[22:18:48] <jepler> yes, the good news is we have a *lot* of fodder for this new website feature
[22:21:25] <jepler> goodnight, feel free to work on the wording, or we can wait for later.
[22:22:47] <jepler> oh I'd add to the list of things that are good for showcase: Free and Open Source software that works with LinuxCNC (so that engraving software as a f'rinstance), but I'd start with machines and the objects made on them
[22:23:30] <KGB-wlo> push to master branch: http://linuxcnc.org/
[22:23:37] -linuxcnc-github:#linuxcnc-devel- [13wlo] 15jepler pushed 1 new commit to 06master: 02https://github.com/LinuxCNC/wlo/commit/1736dda14e8451bbdf6e0a890f2a0007242945a1
[22:23:38] -linuxcnc-github:#linuxcnc-devel- 13wlo/06master 141736dda 15Jeff Epler: showcase: fix post order...
[23:28:33] <seb_kuzminsky> huh, uspace doesn't need memory locking? that seems dangerous