#linuxcnc-devel | Logs for 2016-07-01

Back
[00:07:23] <linuxcnc-build> build #4283 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/4283 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[00:57:05] <linuxcnc-build> build #4298 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4298 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[01:29:25] <seb_kuzminsky> this is a gif of me messing with Task in a stable branch: https://i.imgur.com/qotQfUU.gifv
[01:29:38] <seb_kuzminsky> sort of a, "well what did you think was going to happen" kind of situation
[01:44:39] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 404be0f 06linuxcnc 10src/emc/task/emctask.cc Task: fix a recent "surprise motion on abort" bug * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=404be0f
[01:46:33] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 c9a8a3b 06linuxcnc 10src/emc/task/emctask.cc Merge remote-tracking branch 'origin/2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c9a8a3b
[01:46:57] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 6a79b48 06linuxcnc 10src/emc/task/emctask.cc Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6a79b48
[02:51:48] <linuxcnc-build> build #3126 of 4004.deb-lucid-amd64 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/3126 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[02:58:24] <linuxcnc-build> build #3127 of 4003.deb-lucid-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/3127 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[03:05:02] <linuxcnc-build> build #444 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/444 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[03:07:08] <linuxcnc-build> build #3123 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/3123 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[04:13:58] <linuxcnc-build> build #3124 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/3124 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[04:17:10] <linuxcnc-build> build #3128 of 4003.deb-lucid-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/3128 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[04:27:33] <linuxcnc-build> build #3127 of 4004.deb-lucid-amd64 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/3127 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[05:20:09] <linuxcnc-build> build #2481 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/2481 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[05:58:57] <linuxcnc-build> build #4301 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4301 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[07:19:36] <jepler> hm not sure the best way to solve the isnan problem in lineardeltakins, that header is included by both C and C++ users, and it wants to contain a use of isnan. "using std::isnan" in lineardeltakins.cc doesn't do it, it makes compile errors on jessie
[07:19:56] <jepler> I guess I'll have to get a 16.04 system for myself and mess with it, ugh
[08:44:41] <skunkworks> https://www.youtube.com/watch?v=fjyJIOoiLW0 I don't know if I ever thought about using the axis preview to show actual part dimensions... That is pretty cool
[08:52:17] <archivist> audio is a bit low on that vid
[08:57:26] <skunkworks> I had not even listened to the audio yet.
[09:00:07] <mozmck> I don't think there is any
[09:05:50] <archivist> turn the volume to max it is there just
[09:21:12] <seb_kuzminsky> linuxcnc-build: force build --branch=master 0000.checkin
[09:21:14] <linuxcnc-build> build forced [ETA 1h25m56s]
[09:21:14] <linuxcnc-build> I'll give a shout when the build finishes
[09:52:36] <mozmck> seb_kuzminsky: do you still think we should tag 44c5fb919801bdee (...) as v2.8.0-pre2? Wasn't the bug gene found from before that?
[10:26:34] <linuxcnc-build> Hey! build 0000.checkin #4302 is complete: Success [3build successful]
[10:26:34] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4302
[10:31:51] <seb_kuzminsky> mozmck: yeah, i spoke too hastily and blamed ja for my own bug, sorry
[10:32:16] <seb_kuzminsky> just make a pre-release before each of my commits instead ;-)
[10:32:23] <mozmck> no problem here, just wanted to make sure I understand it correctly
[10:33:07] <mozmck> That does sound like a good idea really.
[11:04:53] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 0000.checkin
[11:04:54] <linuxcnc-build> build forced [ETA 1h15m38s]
[11:04:54] <linuxcnc-build> I'll give a shout when the build finishes
[11:17:20] <seb_kuzminsky> linuxcnc-build: force build --branch=2.7 0000.checkin
[11:17:26] <linuxcnc-build> The build has been queued, I'll give a shout when it starts
[12:13:23] <linuxcnc-build> build #3129 of 4003.deb-lucid-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/3129
[12:15:27] <linuxcnc-build> build #3128 of 4004.deb-lucid-amd64 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/3128
[12:22:16] <seb_kuzminsky> well there it is
[12:22:23] <seb_kuzminsky> lucid is no longer at archive.ubuntu.com
[12:23:16] <jepler> old-releases.ubuntu.com ?
[12:23:35] <seb_kuzminsky> yeah
[12:24:30] <linuxcnc-build> build #3125 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed apt-get-update shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/3125
[12:29:11] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 0000.checkin
[12:29:18] <linuxcnc-build> The build has been queued, I'll give a shout when it starts
[12:30:21] <linuxcnc-build> Hey! build 0000.checkin #4303 is complete: Success [3build successful]
[12:30:21] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4303
[12:30:22] <linuxcnc-build> build forced [ETA 1h20m32s]
[12:30:22] <linuxcnc-build> I'll give a shout when the build finishes
[12:37:59] <linuxcnc-build> build #447 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/447
[12:44:29] <seb_kuzminsky> jepler: thanks for turning me on to git worktrees the other week, that's good stuff
[13:10:48] <mozmck> what is a worktree? guess I should look it up!
[13:12:15] <mozmck> ooh, nice! kinda like going back to bzr, svn, cvs... ;-) (just kidding!)
[13:46:10] <mozmck> seb_kuzminsky: are you using docker with buildbot?
[13:49:44] <jepler> I'm actually grumpy about worktrees now. on the machine where I do most of my linuxcnc development, git is confused about its worktrees
[13:50:12] <jepler> http://paste.debian.net/773941/
[13:50:26] <linuxcnc-build> build #3129 of 4004.deb-lucid-amd64 is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/3129
[13:58:05] <linuxcnc-build> build #3130 of 4003.deb-lucid-i386 is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/3130
[13:58:48] <linuxcnc-build> build #3126 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/3126
[14:02:56] <linuxcnc-build> Hey! build 0000.checkin #4304 is complete: Success [3build successful]
[14:02:56] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4304
[14:02:57] <linuxcnc-build> build forced [ETA 1h26m33s]
[14:02:57] <linuxcnc-build> I'll give a shout when the build finishes
[14:41:52] <CaptHindsight> https://opentrons.com/ yet another CNC project that didn't build on Linuxcnc
[14:42:13] <CaptHindsight> why would you want to use Java vs G-code?
[14:43:43] <CaptHindsight> http://mix.bio/ they created all this vs use G-code
[14:56:48] <seb_kuzminsky> jepler: crikey
[14:57:03] <seb_kuzminsky> mozmck: no docker or containers, it's all KVM virtual machines
[14:57:36] <seb_kuzminsky> you can't put a different kernel inside a container, right? so i still need different machines for rtai vs rt-preempt vs vanilla
[14:58:17] <mozmck> a container can't have it's own kernel? I have never used or needed docker so really know nothing about it.
[14:58:36] <mozmck> So how does the master talk to the virtual machines?
[14:58:47] <mozmck> I presume several run on one box?
[14:58:56] <seb_kuzminsky> i think a container is like a chroot with its own namespace for mounts, pids, networking, etc
[14:59:19] <seb_kuzminsky> the buildmaster VM and all the buildslave VMs have network connectivity to each other
[14:59:24] <seb_kuzminsky> the slaves make tcp connections to the master
[14:59:42] <mozmck> I see.
[15:00:40] <seb_kuzminsky> i have two hypervisor machines, each with a dozen or so buildslave VMs
[15:00:52] <mozmck> hypervisor?
[15:01:07] <seb_kuzminsky> the real machine that runs the virtual machines
[15:03:03] <mozmck> thanks
[15:03:31] <seb_kuzminsky> mmyep
[15:59:34] <linuxcnc-build> Hey! build 0000.checkin #4305 is complete: Success [3build successful]
[15:59:34] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4305
[16:00:08] <linuxcnc-build> build #3127 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/3127
[16:02:34] <linuxcnc-build> build #3130 of 4004.deb-lucid-amd64 is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/3130
[16:07:19] <linuxcnc-build> build #449 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/449
[19:37:27] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6
[19:37:27] <linuxcnc-build> you must provide a Builder, try 'force build [--branch=BRANCH] [--revision=REVISION] [--props=PROP1=VAL1,PROP2=VAL2...] <WHICH> <REASON>'
[19:37:32] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 0000.checkin
[19:37:33] <linuxcnc-build> build forced [ETA 1h41m34s]
[19:37:33] <linuxcnc-build> I'll give a shout when the build finishes
[20:09:37] <jepler> wtf, installing linuxcnc build deps on ubuntu 16.04 brings in a webserver
[20:09:40] <jepler> apache to be precise
[20:18:42] <mozmck> try --no-recommends
[20:21:52] <jepler> yeah that would have helped
[20:22:39] <mozmck> I remember it saving about 400 MB of downloads when setting up lucid.
[20:22:43] <jepler> it doesn't matter much, it's an image I'll destroy once I track down the build errors in master branch on that distro
[20:23:35] <mozmck> I have a 16.04 image to start testing with. Looks like it needs an entry in the configure script
[20:23:49] <jepler> yeah
[20:24:44] <jepler> this is what I came up with https://emergent.unpythonic.net/files/sandbox/0001-debian-configure-support-ubuntu-16.04.patch
[20:26:48] <jepler> and there was apparently just one compile error left :-P
[20:26:51] <jepler> https://emergent.unpythonic.net/files/sandbox/0001-lineardeltakins-fix-compile-error-on-Ubuntu-16.04.patch
[20:27:28] <mozmck> thanks for the configure patch.
[20:28:04] <jepler> *** Error in `rs274': double free or corruption (!prev): 0x000000000106ff30 ***
[20:28:14] <mozmck> It looked like it might need the line PYTHON_PACKAGING=dh_python2 like Debian8 from what I saw - did it not need that?
[20:28:24] <jepler> I dunno, I did not build a package
[20:28:35] <jepler> so I'll hold off pushing that one, and let you verify the package builds
[20:29:19] <mozmck> I see. It complained about python-support and it looks like it was replace in 16.04 as in debian 8
[20:30:07] <mozmck> I'll look at it as soon as I can. It's be crazy here. Spent two days un-encrypting all the files on our file servers at work because of a windows virus :-)
[20:30:23] <jepler> ugh
[20:30:34] <jepler> fresh linux install + restore documents from last tape backup
[20:30:49] <mozmck> yeah. and I'm kind of the only network admin there - and I'm not there most of the time.
[20:31:22] <mozmck> The server is debian, but the main file share was mapped as a drive on the win computer that got infected.
[20:31:42] <jepler> ah no you reinstall those computers too
[20:31:52] <jepler> the windows ones
[20:32:30] <mozmck> I think we got it all cleaned out. It was the Nemucod ransomware
[20:33:18] <mozmck> You would re-install the server? I don't think it could do anything on that (but I'm not a security professional either)
[20:34:14] <jepler> no, I'd reinstall all the windows computers with linux
[20:35:17] <mozmck> Heh, that's what I would do too, but not everyone will go for that. This computer has to run Quickbooks. We did install kaspersky internet security which should help.
[20:36:07] <jepler> quickbooks has a web-based version that works fine on linux fwiw
[20:36:26] <jepler> but no I understand you can't just make this declaration that everybody gets linux tomorrow
[20:36:31] <mozmck> Hmm, I might have to look into that.
[20:37:17] <mozmck> We do have a lot more running linux now. We can probably switch some more over too. My boss considers Win10 a virus which is good.
[20:38:30] <mozmck> well, I'll look at the configure script later - maybe later tonight. bll
[20:38:31] <mozmck> bbl
[20:49:06] <jepler> well I guess we'd better work around this, it's been a year since some boost boffin said he'd try to get a fix in...! https://emergent.unpythonic.net/files/sandbox/0001-rs274-work-around-boost-python-bug.patch
[20:56:52] <skunkworks_> backups are good
[20:57:14] <linuxcnc-build> build #450 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/450
[20:59:50] <skunkworks_> we caught one a year or so ago... it caused enough network traffic that we fount it pretty quick
[21:00:05] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened pull request #102: rs274: work around boost::python bug (06master...06jepler/2.7/boost-workaround) 02https://github.com/LinuxCNC/linuxcnc/pull/102
[21:00:12] <skunkworks_> found
[21:00:44] <linuxcnc-build> Hey! build 0000.checkin #4306 is complete: Success [3build successful]
[21:00:44] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4306
[21:00:50] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #102: The affected code is in 2.6 too, but our platform support notes show that even Debian 8.x (jessie) isn't expected to build 2.6 in the first place, so I didn't bother putting the PR that far back in time. 02https://github.com/LinuxCNC/linuxcnc/pull/102#issuecomment-230076624
[21:01:13] <skunkworks_> we are still finding random encrypted files on the network..
[21:04:51] <skunkworks_> backup servers are not shared
[21:05:30] <KGB-linuxcnc> 03Jeff Epler 05master b0a683d 06linuxcnc 10src/emc/kinematics/lineardeltakins.cc lineardeltakins: fix compile error on Ubuntu 16.04 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=b0a683d
[21:05:30] <KGB-linuxcnc> 03Jeff Epler 05master a6ebc47 06linuxcnc 10src/emc/pythonplugin/python_plugin.cc rs274: work around boost::python bug * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a6ebc47
[21:15:10] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15cradek closed issue #101: isnan error while compiling 02https://github.com/LinuxCNC/linuxcnc/issues/101
[21:18:55] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #101: I created a 16.04 virtual machine, and after the above commit I got a full build. Tests failed until I added the patch in #102, which is also in our master branch now. I didn't try any interactive/graphical features before I blitzed the VM and called it a day. 02https://github.com/LinuxCNC/linuxcnc/issues/101#issuecomment-230077496
[22:21:17] <seb_kuzminsky> ////~.
[22:26:20] <seb_kuzminsky> linuxcnc-build: force build --branch=2.7 0000.checkin
[22:26:26] <linuxcnc-build> The build has been queued, I'll give a shout when it starts
[22:33:38] <linuxcnc-build> build forced [ETA 1h30m11s]
[22:33:38] <linuxcnc-build> I'll give a shout when the build finishes