#linuxcnc-devel Logs

Nov 20 2017

05:55 AM linuxcnc-build: build #5181 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/5181 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
05:57 AM linuxcnc-build: build #5178 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/5178 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
05:57 AM linuxcnc-build: build #4391 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/4391 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:03 AM linuxcnc-build: build #2855 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/2855 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:03 AM linuxcnc-build: build #3340 of 1403.rip-wheezy-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/3340 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:03 AM linuxcnc-build: build #3541 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/3541 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:03 AM linuxcnc-build: build #3339 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/3339 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:03 AM linuxcnc-build: build #1806 of 1500.rip-jessie-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1500.rip-jessie-i386/builds/1806 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:04 AM linuxcnc-build: build #3006 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/3006 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:04 AM linuxcnc-build: build #1807 of 1520.rip-jessie-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1520.rip-jessie-amd64/builds/1807 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:04 AM linuxcnc-build: build #1806 of 1510.rip-jessie-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1510.rip-jessie-rtpreempt-i386/builds/1806 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:05 AM linuxcnc-build: build #1808 of 1530.rip-jessie-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1530.rip-jessie-rtpreempt-amd64/builds/1808 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:07 AM linuxcnc-build: build #194 of 1630.rip-stretch-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1630.rip-stretch-rtpreempt-amd64/builds/194 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:08 AM linuxcnc-build: build #195 of 1610.rip-stretch-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1610.rip-stretch-rtpreempt-i386/builds/195 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:15 AM linuxcnc-build: build #3349 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/3349 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:22 AM linuxcnc-build: build #383 of 1540.rip-jessie-armhf is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1540.rip-jessie-armhf/builds/383 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
06:22 AM linuxcnc-build: build #5199 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5199 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
07:55 AM linuxcnc-build: build #4130 of 4007.deb-precise-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4007.deb-precise-i386/builds/4130 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
07:56 AM linuxcnc-build: build #4130 of 4008.deb-precise-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4008.deb-precise-amd64/builds/4130 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
07:58 AM linuxcnc-build: build #2699 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/2699 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
07:58 AM linuxcnc-build: build #2960 of 4009.deb-precise-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4009.deb-precise-rtai-i386/builds/2960 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
08:26 AM linuxcnc-build: build #1098 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/1098 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
08:44 AM linuxcnc-build: build #283 of 4025.deb-jessie-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4025.deb-jessie-armhf/builds/283 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
08:44 AM linuxcnc-build: build #155 of 4030.deb-stretch-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4030.deb-stretch-rtpreempt-i386/builds/155 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
08:57 AM linuxcnc-build: build #2702 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/2702 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:02 AM linuxcnc-build: build #1261 of 4019.deb-jessie-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4019.deb-jessie-rtpreempt-i386/builds/1261 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:04 AM linuxcnc-build: build #1959 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/1959 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:05 AM linuxcnc-build: build #1993 of 4015.deb-wheezy-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4015.deb-wheezy-rtpreempt-amd64/builds/1993 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:14 AM linuxcnc-build: build #2390 of 4018.deb-wheezy-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4018.deb-wheezy-rtai-i386/builds/2390 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:17 AM linuxcnc-build: build #155 of 4031.deb-stretch-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4031.deb-stretch-rtpreempt-amd64/builds/155 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:20 AM linuxcnc-build: build #1372 of 4022.deb-jessie-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4022.deb-jessie-amd64/builds/1372 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:21 AM linuxcnc-build: build #1260 of 4020.deb-jessie-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4020.deb-jessie-rtpreempt-amd64/builds/1260 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:23 AM linuxcnc-build: build #1374 of 4021.deb-jessie-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4021.deb-jessie-i386/builds/1374 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:23 AM jepler: it would be nice if he fixed those errors
10:27 AM skunkworks: Ok - figured out the limit git thing. I just assumed the one on linuxcnc git hub was pulled from machinekit - but it was the other way around. (seb created it first)
10:29 AM archivist: skunkworks, got a text for JS's wake, do I dont I
10:35 AM skunkworks: wow - that seems like a long time...
10:35 AM skunkworks: (between when he died and the wake?
10:35 AM skunkworks: over here it seems to be a few days
10:35 AM archivist: this thursday iirc
10:36 AM archivist: sometimes there is something extra for non family/whatever
10:39 AM cradek: who died?
10:40 AM archivist: John Stevenson
10:40 AM archivist: the noisy one
11:13 AM cradek: hm he posted to emc-users 3 times in 2009
11:13 AM cradek: I think I don't know/remember him from anywhere
11:17 AM hazzy: JS was very active on Practical Machinist and several other forums
11:18 AM hazzy: I grew up reading his posts for hours on end, very amusing and informative generally
11:18 AM cradek: ah
11:18 AM cradek: well that sucks then.
11:36 AM skunkworks: hazzy, is that why you started with mach?
11:36 AM skunkworks: ;)
11:39 AM hazzy: skunkworks: Yes, actually, I had heard so much about Mach it seemed like that was all there was
11:39 AM hazzy: Little did I know :)
12:22 PM skunkworks: https://github.com/Nikolay-Kha/PyCNC
12:25 PM Tom_itx is now known as Tom_L
12:28 PM skunkworks: uh oh
12:28 PM hazzy: skunkworks: That project looks very interesting
12:29 PM hazzy: oops, wonder what happened there ....
12:29 PM skunkworks: I think I saw it on cnczone a while ago.
12:31 PM andypugh: Which project?
12:31 PM hazzy: https://github.com/Nikolay-Kha/PyCNC
12:33 PM andypugh: Ah, OK. How does he generate steps? Or isn’t that ehat it does?
12:35 PM -!- #linuxcnc-devel mode set to +v by ChanServ
12:36 PM hazzy: It is written in pure python, but uses Direct Memory Access to somehow control the GPIO directly from the RAM buffer so it basically real time
12:37 PM hazzy: Seems like an interesting idea, but I don't understand it
12:40 PM Tom_L: is that based on grbl?
12:40 PM andypugh: Someone was threatening to do that for the Pi with LinuxCNC.
12:41 PM andypugh: It’s simple in theory, you fill a buffer with bit patterns and then cycle it out through the GPIO registers at the required base-rate.
12:41 PM Tom_L: wtf is E axis?
12:42 PM andypugh: Extruder
12:42 PM andypugh: Mungkie was going to write a driver and sell a kit, but I can’t believe that this Indigogo campaign was really serious. https://www.indiegogo.com/projects/linuxcnc-drivers-for-raspberry-pi/#/
12:42 PM Tom_L: so not as open hardware wise as lcnc
12:43 PM Tom_L: and targeted to the glue gun croud
12:43 PM skunkworks: so - it is basically a buffered system?
02:03 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:50 PM hazzy: hello Chris
05:57 PM hazzy: Chris_Morley: Do you know if it is possible to use Qt Designer's Slot/Signal editor to connect custom signals in the plugins?
05:58 PM Chris_Morley: tell me more of what you are trying to do.
05:59 PM Chris_Morley: Do you want to have a custom slot in a custom widget and then use designer to connect it to other python code
05:59 PM hazzy: I don't have anything particular in mind
05:59 PM hazzy: Yes
06:00 PM Chris_Morley: I believe you can, You can use decorators to create slots - designer should be able to see them - but i havent specifically tried it.
06:01 PM Chris_Morley: thanks for the heads up on build errors - i see it's something else then i thought it was :)
06:06 PM hazzy: Ok thanks! I am and going to play with making some plugins and see what kinds of things are possible, designer seems far more capable than glade ...
06:06 PM hazzy: np :)
06:12 PM Chris_Morley: Ok Kurt i'll see about cleaning up the branch and rebasing it ttyl
06:22 PM hazzy: sounds good, thanks Chris
07:18 PM linuxcnc-build: build #1099 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/1099 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
08:05 PM linuxcnc-build: build #156 of 4031.deb-stretch-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4031.deb-stretch-rtpreempt-amd64/builds/156 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
08:46 PM linuxcnc-build: build #156 of 4030.deb-stretch-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4030.deb-stretch-rtpreempt-i386/builds/156 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:17 PM hazzy: Chris_Morley: Looks good!
09:17 PM hazzy: thank you
09:17 PM Chris_Morley: You bet
09:20 PM Chris_Morley: I see that the project is called qtvcp but We actually use 'qtscreen' in the ini file to load screens. I wonder if to be consistent - it should also be renamed qtvcp?
09:20 PM hazzy: I was wondering about that
09:21 PM Chris_Morley: orignally there was going to be both - one for HAL panels one for screens
09:22 PM hazzy: I was kinda thinking qtscreeen what the whole thing, which was built with qtvcp, so I did not see it as an inconsistency
09:22 PM hazzy: ah
09:22 PM Chris_Morley: It could be left - can cross that bridge later :)
09:22 PM hazzy: yes, it does not bother me :)
09:23 PM Chris_Morley: ok
09:23 PM hazzy: I am working on replacing your debug prints with the python logging module, is that something you would find valuable?
09:24 PM Chris_Morley: I've not used it - what the advantage?
09:24 PM Chris_Morley: log to a file>
09:25 PM Chris_Morley: are you going to play with it as pyqt4 and python 2? or should we convert to pyqt5 and python 3 now?
09:25 PM hazzy: You can set the log level per module, so you can silence noisy files that have already been debugged
09:25 PM Chris_Morley: that sounds interesting !
09:26 PM hazzy: I am going to play with it as qt4 to get a better idea of how QT works and what you are after
09:26 PM hazzy: and then think about switching
09:27 PM Chris_Morley: ok. i might try some sample code using pyqt5 and python 3 to see if i can get it working here before spending time converting the project again.
09:27 PM hazzy: yes I think that is a good idea
09:28 PM hazzy: Here is a terminal out put from hazzy: http://i.imgur.com/ze76Sek.png
09:28 PM hazzy: I am basically doing the same thing for qtvcp
09:29 PM hazzy: instead of `print msg` you do `log.debug('msg')` or `log.error('msg')`
09:30 PM Chris_Morley: That looks good.
09:31 PM Chris_Morley: I must confess i tend to leave losts of debugging code around. i assume it is easy to turn logging on and off?
09:32 PM Chris_Morley: like with the -d switch
09:32 PM hazzy: yes, it is better to err of the side of too many prints than too few!
09:33 PM hazzy: you set the log level by `log.setLevel(DEBUG)` etc
09:33 PM Chris_Morley: it does sometimes help when other are using and need help.
09:33 PM hazzy: I also have it logging to a file
09:33 PM hazzy: specified in the INI, but defaulting to the home dir
09:34 PM Chris_Morley: very nice
09:35 PM hazzy: I will convert a few files to using logging and let you look at is and say yay or nay :)
09:36 PM Chris_Morley: oh i think its yay already
09:36 PM hazzy: haha, ok
09:37 PM hazzy: I have to go do family stuff, bbl
09:38 PM Chris_Morley: i'll leave you to play. im off to do boring life things :) i'm enthused about working together. later
09:38 PM hazzy: same!