Back
[07:24:49] <KGB-linuxcnc> 03Jeff Epler 05master 0ad006d 06linuxcnc 10debian/control.top.in packaging: add vcs headers a la debian policy * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0ad006d
[07:48:19] <linuxcnc-build> build #4464 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/4464 blamelist: Jeff Epler <jepler@unpythonic.net>
[07:52:29] <linuxcnc-build> build #2139 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/2139 blamelist: Jeff Epler <jepler@unpythonic.net>
[07:58:57] <linuxcnc-build> build #2659 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/2659 blamelist: Jeff Epler <jepler@unpythonic.net>
[08:02:41] <linuxcnc-build> build #1093 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/1093 blamelist: Jeff Epler <jepler@unpythonic.net>
[08:03:42] <linuxcnc-build> build #1093 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/1093 blamelist: Jeff Epler <jepler@unpythonic.net>
[08:03:42] <linuxcnc-build> build #4481 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4481 blamelist: Jeff Epler <jepler@unpythonic.net>
[10:36:39] <JT-Shop> which bit file for a 7i92 would be the same as a parallel port?
[10:38:47] <mozmck> JT-Shop: I think there could be a number of them.
[10:39:30] <JT-Shop> that's what I'm thinking too perhaps the g540 flavor
[10:39:35] <mozmck> I believe the pinout of the headers is the same as a parallel port, but you will need different bit files for different breakout boards.
[10:39:48] <JT-Shop> good point
[10:40:17] <Roguish> JT-Shop: good morning.
[10:40:18] <mozmck> IO is fine, but if the step/dir signal are on different pins between two breakout boards, each one will need it's own bitfile
[10:41:32] <Roguish> do you know if anyone has made significant changes to the Touchy UI? I think my company is going to let me do new controls on the sheetmetal brake back gage.
[10:42:02] <Roguish> I think Touchy is all Glade. right?
[10:44:05] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15robEllenberg commented on issue #138: @zultron I agree, with a slight correction that the correct state (i.e. active from the user's perspective) is the one currently executing in **motion**. Canon state matches the interpreter state, because the last step in interpreting most program lines is to call one or more canon commands. Canon does have some internal state, but conceptually, it's just a translation layer for the i
[10:44:35] <JT-Shop> I'm not sure...
[10:44:42] <Roguish> i
[10:45:08] <Roguish> i'm going to fire up a VM in my fast workstation and play with Touchy..
[10:45:12] <mozmck> It would be nice if linuxcnc-github put a link to the issue so I could click on it here in IRC
[10:46:22] <JT-Shop> morning Roguish
[10:46:54] <pcw_home> JT-Shop:
[10:46:56] <pcw_home> 7i92_DMMBOB1x2D.bit, 7i92_G540x2D.bit, 7i92_MX3660x2D.bit,
[10:46:57] <pcw_home> 7i92_MX4660x2D.bit, 7i92_MX4660x2D.bit, 7i92_MX4660x2D.bit
[10:46:59] <pcw_home> are the parallel port (and parallel port BOB) compatible pinouts
[10:47:07] <JT-Shop> thanks pcw_home
[10:47:58] <pcw_home> oops too many 4660s also 7i92_BENEZANx2D.bit, 7i92_R990x2D.bit
[10:48:47] <pcw_home> main differences are steo/dir locations and extra bits like PWM, chargepump stepgens and encoders
[10:48:58] <JT-Shop> thanks
[10:49:40] * JT-Shop needs to change the oil in the van...
[10:49:53] <JT-Shop> before the wife gets home and want's her spot back
[10:49:55] <pcw_home> you can look at the 5i25 pin files to see the pinouts
[10:50:02] <Roguish> pcw_home: PCW do you know if you have any 7I40HV in stock? like 3 of them?
[10:50:31] <pcw_home> none in stock now they are being built however
[10:50:40] <Roguish> ETA?
[10:51:15] <pcw_home> Ill check where the are on Monday
[10:51:34] <pcw_home> we have kind of buried our assy house
[10:51:43] <Roguish> thx.
[10:52:02] <Roguish> hey, that's a good problem, isn't it.
[10:52:17] <pcw_home> yes and no...
[10:59:47] <mozmck> heh! too many orders can be almost as bad as not enough!
[11:34:42] <JT-Shop> seems we have opposite problems lol
[13:04:10] <seb_kuzminsky> ooh, the freecad in Debian Stretch has the Path module (CAM) integrated
[13:04:13] <seb_kuzminsky> i haven't tried it yet
[14:58:16] <jmkasunich> seb_kuzminsky: jepler_ cradek around?
[14:58:38] <jmkasunich> trying to figure out how to do something in git/github
[14:59:48] <jmkasunich> when I started messing with the beaglebone, jepler created a branch jepler/master/halonly, because I was running out of memory during builds (and because being able to build just RTAPI and HAL could be handy
[15:01:12] <jmkasunich> turns out my memory problem was my fault - I had a browser open. With the browser closed the beaglebone can compile master just fine
[15:01:49] <jmkasunich> I now have two local branches - halonly and master
[15:03:20] <jmkasunich> jepler brought in the machinekit beaglebone gpio driver hal_bb_gpio.c and beaglebone_gpio.h, they are in the halonly branch
[15:04:50] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15gmoccapy commented on issue #139: Hallo Jepler,... 02
https://github.com/LinuxCNC/linuxcnc/issues/139#issuecomment-241219472
[15:08:14] <jmkasunich> I can't figure out how to find jeplers halonly branch on git.linuxcnc.org/gitweb, and can't find his commit in the log. possibly the driver (and branch?) exists only on github?
[15:09:14] <jmkasunich> meanwhile I fixed a bug in the driver. I was working on my local halonly branch (the only one that contains the driver), and I pushed the bugfix to the halonly branch on github:jmkasunich/linuxcnc
[15:09:34] <jmkasunich> I have not submitted a pull request for the fix
[15:10:15] <jmkasunich> two things that I want to happen:
[15:11:21] <jmkasunich> 1)get the driver into linuxcnc/master - the halonly branch is probably a dead end, it isn't needed from a memory point of view, and jepler has found several things that he would do differently if we really wanted a halonly version
[15:11:47] <jmkasunich> 2) get my fixes into the driver - preferably in master, after accomplishing item #1
[15:13:10] <jmkasunich> I need some guidance, I'm still having trouble wrapping my mind around the distributed development model
[15:24:04] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15pcw-mesa commented on issue #139: You really cannot use the FPGA I/O watchdog this way. If you have a watchdog event, its basically ... 02
https://github.com/LinuxCNC/linuxcnc/issues/139#issuecomment-241220424
[15:27:40] <jepler_> jmkasunich: I recommend that you just copy the driver (and other stuff like Makefile to enable it) into a branch based off master and PR it. Please credit the MK authors like I did in my commit.
[15:28:18] <jepler_> as you say, the halonly branch is of limited value
[15:28:42] <jepler_> if you want me to do the git for putting bb_gpio in master branch I'd be happy to.
[15:29:21] <jepler_> eh let me work on it
[15:31:17] <KGB-linuxcnc> 03Jeff Epler 05master e4b0d18 06linuxcnc 10src/rtapi/uspace_rtapi_app.cc uspace: restore thread that reads out messages from realtime * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e4b0d18
[15:31:17] <KGB-linuxcnc> 03Jeff Epler 05master 3a69f64 06linuxcnc 10src/hal/user_comps/mb2hal/Submakefile 10src/hal/user_comps/mb2hal/mb2hal.h mb2hal: remove needless dependency on linuxcnc * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3a69f64
[15:31:17] <KGB-linuxcnc> 03Jeff Epler 05master 5f0865a 06linuxcnc 03docs/man/man3/rtapi_open_as_root.3rtapi 10src/hal/drivers/mesa-hostmot2/hm2_rpspi.c 10src/rtapi/rtapi.h 10src/rtapi/uspace_rtapi_app.cc rtapi: Add rtapi_open_as_root API * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=5f0865a
[15:31:20] <KGB-linuxcnc> 03Jeff Epler 05master 1070a8a 06linuxcnc 10src/Makefile 03src/hal/drivers/beaglebone_gpio.h 03src/hal/drivers/hal_bb_gpio.c hal_bb_gpio: new hardware driver * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1070a8a
[15:31:25] <KGB-linuxcnc> 03Jeff Epler 05master 338a753 06linuxcnc 03docs/src/man/man9/hal_bb_gpio.9 hal_bb_gpio: add manpage * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=338a753
[15:32:00] <jepler> jmkasunich: so hal_bb_gpio.c and hal_bb_gpio.9 should be identical to the ones that I put in the halonly branch, so you should be safe copying your improved versions over and committing them.
[15:40:06] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15gmoccapy commented on issue #139: @pcw-mesa,... 02
https://github.com/LinuxCNC/linuxcnc/issues/139#issuecomment-241221221
[15:41:23] <jmk-mcfaul_> jepler, thanks!
[15:47:03] <linuxcnc-build> build #4468 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/4468 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:49:15] <linuxcnc-build> build #3677 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/3677 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:49:42] <linuxcnc-build> build #4465 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/4465 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:49:53] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jmkasunich opened pull request #155: Fixes to hal_bb_gpio driver (06master...06master) 02
https://github.com/LinuxCNC/linuxcnc/pull/155
[15:50:12] <jmkasunich> I was able to cherry pick my commits instead of copying files...
[15:50:18] <linuxcnc-build> build #2627 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/2627 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:50:42] <linuxcnc-build> build #2626 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/2626 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:53:06] <linuxcnc-build> build #2827 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/2827 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:53:11] <linuxcnc-build> build #1094 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/1094 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:53:34] <linuxcnc-build> build #2140 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/2140 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:53:42] <linuxcnc-build> build #2292 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/2292 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:54:04] <linuxcnc-build> build #1096 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/1096 blamelist: Jeff Epler <jepler@unpythonic.net>
[15:55:51] <jepler> trivkins: dlopen: /home/buildslave/emc2-buildbot/precise-amd64/precise-amd64-sim/build/rtlib/trivkins.so: cannot open shared object file: No such file or directory
[15:55:58] <jepler> how did I break it this time
[15:56:00] <jepler> sigh
[15:57:08] * jepler <-- incompetent, sigh
[15:59:11] <linuxcnc-build> build #2660 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/2660 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:00:00] <KGB-linuxcnc> 03Jeff Epler 05master 423fc54 06linuxcnc 10src/Makefile build: remove 'halonly'-related change unintentionally committed * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=423fc54
[16:09:47] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 0000.checkin
[16:09:52] <linuxcnc-build> The build has been queued, I'll give a shout when it starts
[16:11:17] <linuxcnc-build> build #1094 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/1094 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:12:11] <linuxcnc-build> build #1094 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/1094 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:12:11] <linuxcnc-build> build #4482 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4482 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:22:14] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15pcw-mesa commented on issue #139: I can't duplicate this ... 02
https://github.com/LinuxCNC/linuxcnc/issues/139#issuecomment-241223175
[16:36:44] <linuxcnc-build> build #4466 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/4466 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:39:50] <linuxcnc-build> build #2141 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/2141 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:50:29] <linuxcnc-build> build #1095 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/1095 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:50:53] <linuxcnc-build> build #1095 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/1095 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:50:53] <linuxcnc-build> build #4483 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4483 blamelist: Jeff Epler <jepler@unpythonic.net>
[16:50:54] <linuxcnc-build> build #4484 forced
[16:50:54] <linuxcnc-build> I'll give a shout when the build finishes
[16:53:33] <linuxcnc-build> build #2142 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed install-missing-build-dependencies configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/2142
[17:07:24] <jepler> "linux-image-uspace,rtai-modules-uspace"
[17:07:26] <jepler> well that's afu
[17:07:33] <jepler> your kernel 'uspace' is not known. There might be needed dependencies which won't get set automatically.
[17:07:59] <jepler> oh this is 2.6 branch, "uspace" isn't there yet
[17:10:43] <jepler> so the puzzle is why buildbot tried to build that way
[17:11:02] <jepler> seb_kuzminsky: it would not be hard to make "uspace" be an alias of "sim" in 2.6 if that is convenient...
[17:11:36] <jmkasunich> seems to me that sim is one thing and uspace is another
[17:12:02] <jmkasunich> uspace attempts to provide some level of realtime guarantee doesn't it? sim makes no such attempt
[17:14:27] <jepler> jmkasunich: 2.6 didn't have any userspace realtime, it only had sim. in 2.7, "uspace" can be used either as sim (vanilla kernel) or realtime (with preempt-rt kernel only). now in master, "uspace" can be used as sim or rt with any "major" rt kernel..
[17:14:39] <jepler> so yes
[17:15:59] <jmkasunich> so in 2.6 "uspace" doesn't exist...
[17:16:24] <jmkasunich> if no docs reference it, then there is no reason to make it an alias for anything
[17:17:45] <jepler> there may be, if it is convenient for buildbot
[17:18:21] <jmkasunich> so the problem is that buildbot
[17:18:23] <jmkasunich> oops
[17:18:57] <jmkasunich> buildbot's command line isn't aware of what branch it is building, and can pass ./configure options that aren't supported
[17:22:04] <jepler> yes. it has some hardcoded rules in its scripts and I asked seb to change them so that buildbot would start building uspace with rtai support enabled. I suspect that its attempt earlier to build "sim" with a 2.6-based branch was due to his work in progress
[18:02:09] <KGB-linuxcnc> 03Jeff Epler 05master 75bd22c 06linuxcnc Merge branch 'master' of
https://github.com/jmkasunich/linuxcnc * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=75bd22c
[18:02:09] <KGB-linuxcnc> 03Jeff Epler 05master 8f64b75 06linuxcnc 10src/hal/drivers/hal_bb_gpio.c hal_bb_gpio: error handling is not just calling exit() * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=8f64b75
[18:02:09] <KGB-linuxcnc> 03Jeff Epler 05master b0dcbdf 06linuxcnc 10src/hal/drivers/hal_bb_gpio.c hal_bb_gpio: compensate for 1-based thinking by overallocating * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=b0dcbdf
[18:03:40] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15cradek closed pull request #155: Fixes to hal_bb_gpio driver (06master...06master) 02
https://github.com/LinuxCNC/linuxcnc/pull/155
[18:14:35] <jmkasunich> jepler: this particular error return:
[18:14:40] <jmkasunich> @@ -100,7 +101,7 @@ void configure_gpio_port(int n) {
[18:14:40] <jmkasunich> // check for port enabled
[18:14:40] <jmkasunich> if ( (regvalue & CM_PER_GPIO_CLKCTRL_MODMODE_MASK ) != CM_PER_GPIO_CLKCTRL_MODMODE_ENABLED ) {
[18:14:40] <jmkasunich> rtapi_print_msg(RTAPI_MSG_ERR, "%s: ERROR: GPIO Port %d is not enabled in device tree\n", modname, n);
[18:14:40] <jmkasunich> - exit(1);
[18:14:42] <jmkasunich> + return -errno;
[18:14:44] <jmkasunich> }
[18:14:46] <jmkasunich> munmap((void *)cm_per, CM_PER_LEN);
[18:14:48] <jmkasunich> }
[18:15:05] <jmkasunich> probably shouldn't return -errno, since it is a simple test, not a system call that would set errno
[18:16:04] <jmkasunich> maybe "return -EPERM;" ?
[18:21:00] <jmkasunich> or just -1
[18:21:59] <jepler> oh yes, you're right that -errno isn't correct here
[18:22:51] <jepler> -ENODEV ?
[18:23:59] <jmkasunich> seems reasonable
[18:25:41] <jepler> you want to do it or shall I?
[18:26:17] <jmkasunich> do you mind? I would have to fetch your previous version, modify, push, then you'd have to pull
[18:26:45] <jmkasunich> github adds another layer to the process
[18:29:04] <KGB-linuxcnc> 03Jeff Epler 05master e8f8099 06linuxcnc 10src/hal/drivers/hal_bb_gpio.c hal_bb_gpio: errno didn't make sense here * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e8f8099
[18:29:15] <linuxcnc-build> build #4468 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/4468 blamelist: Jeff Epler <jepler@unpythonic.net>, John Kasunich <jmkasunich@fastmail.fm>
[18:30:11] <jepler> > /home/buildslave/emc2-buildbot/precise-i386/precise-i386-sim/build/scripts/halrun: line 157: 3747 Segmentation fault (core dumped) halcmd_twopass "$filename"
[18:30:17] <jepler> it's sure consistent
[18:31:58] <jepler> doesn't happen on travis-ci, which is precise but with a vanilla kernel
[18:32:35] <jmkasunich> and it seems to have no relation at all to the code that was changed
[18:32:47] <jmkasunich> there is no test that runs that driver
[18:34:13] <linuxcnc-build> build #2143 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/2143 blamelist: Jeff Epler <jepler@unpythonic.net>, John Kasunich <jmkasunich@fastmail.fm>
[18:36:00] <jepler> no, we've never done hardware drivers in our testsuite
[18:37:12] <jmkasunich> so basically the buildbot is smoking something.... or the code was broken before the latest commit
[18:37:57] <jepler> yes
[18:38:04] <jepler> that failure has been happening for .. awhile now
[18:38:17] <jepler> I think it started being seen when the buildbot "upgraded" to rtai for that build
[18:38:45] <jepler> I don't see it, but I have jessie amd64, not precise i386...
[18:38:58] <jepler> oh buildbot is doing a 32-bit build there but travis-ci only does 64-bit builds
[18:39:04] <jepler> so 32 vs 64 bit possibility too?
[18:43:05] <linuxcnc-build> build #1097 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/1097 blamelist: Jeff Epler <jepler@unpythonic.net>, John Kasunich <jmkasunich@fastmail.fm>
[18:44:31] <linuxcnc-build> build #1097 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/1097 blamelist: Jeff Epler <jepler@unpythonic.net>, John Kasunich <jmkasunich@fastmail.fm>
[18:44:31] <linuxcnc-build> build #4485 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4485 blamelist: Jeff Epler <jepler@unpythonic.net>, John Kasunich <jmkasunich@fastmail.fm>
[19:06:26] <jepler> seb_kuzminsky: looks like the wise choice will be to re-disable uspace+rtai in the buildbot and declare it "not ready for prime time"
[19:09:11] <linuxcnc-build> build #4469 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/4469 blamelist: Jeff Epler <jepler@unpythonic.net>
[19:12:29] <linuxcnc-build> build #2144 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/2144 blamelist: Jeff Epler <jepler@unpythonic.net>
[19:23:21] <linuxcnc-build> build #1098 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/1098 blamelist: Jeff Epler <jepler@unpythonic.net>
[19:24:04] <linuxcnc-build> build #1098 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/1098 blamelist: Jeff Epler <jepler@unpythonic.net>
[19:24:04] <linuxcnc-build> build #4486 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4486 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:50:32] <skunkworks_> zlog
[22:00:29] <jmk-mcfaul_> jepler: is there a reason that the man page for hal_bb_gpio is in docs/src/man/man9 instead of docs/man/man9?
[22:00:42] <jmk-mcfaul_> there are many man pages in the latter location, only three in the former
[22:01:12] <jmk-mcfaul_> one of the three is actually asciidoc rather than troff
[22:25:16] <jepler> jmk-mcfaul_: yeah we are in a transition that nobody has gotten around to finishing
[22:25:38] <jepler> we would like to have all the man sources under docs/src/man and copy or process them (convert from asciidoc to man) at build time
[22:25:59] <jepler> (asciidoc is more pleasant to write, but we don't want to give off the excellent offline / terminal based interface to our manpages)
[22:26:35] <jepler> right now there's a problem where if you don't have asciidoc it doesn't copy the roff-format manpages either. we probably will eventually just make asciidoc mandatory for building
[22:26:43] <jepler> nobody's really touched it lately, it's been in this transitional state
[22:26:48] <jepler> 'night
[22:32:16] <jmk-mcfaul_> since nobody has touched it in a long time, can I move the troff man page for the bb driver to docs/man/man9? if/when there is a wholesale move of stuff from doc/man to doc/src/man, that one can move with all the others
[22:35:15] <jepler> jmk-mcfaul_: sure
[22:55:27] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jmkasunich opened pull request #156: Move hal_bb_gpio manpage from docs/src/ to docs/man/ (06master...06master) 02
https://github.com/LinuxCNC/linuxcnc/pull/156