Back
[10:29:22] <skunkworks> Hi alex_joni
[10:38:09] <JT-Shop> Hi alex_joni
[10:38:11] <mozmck> so does everyone not like the x.y.z numbering scheme? I kind of like it myself. For x.y numbering, would y be bug-fix releases and x by major ones?
[10:38:48] <mozmck> I guess there is not much difference except the major number increases faster.
[10:39:54] <seb_kuzminsky> mozmck: "x.y.z" is like 2.7.1, right? the x.y (2.7) is the "major version", and the z (.1) is the minor version. the issue for me is, when do you increment X vs increment Y? ie, is the next version 2.8 or 3.0?
[10:40:23] <seb_kuzminsky> the distinction is not useful to me, so i'd rather collapse those two numbers into one, and increment it for each new stable version
[10:40:50] <seb_kuzminsky> it makes the number simpler, without losing the information of "this is a new stable version"
[10:41:06] <mozmck> that may be so
[10:41:27] <seb_kuzminsky> but it's your release and i dont have a strong feeling about it ;-)
[10:41:51] <mozmck> One thing I have seen that I kind of like is having even Y numbers be stable and odd for development releases. I don't know if we want to get into that though.
[10:42:06] <mozmck> I don't have strong feelings about it either.
[10:42:23] <seb_kuzminsky> that was how the linux kernel did it in the early days, but they moved away frmo it
[10:42:45] <seb_kuzminsky> we dont really release development code currently, except as buildbot packages from the master branch
[10:42:52] <mozmck> Jumping to 3.0 is fine by me especially if we get JA in.
[10:43:39] <seb_kuzminsky> we indicate pre-release with the "~preN" suffix to the version number (the ~ works well with how debian packages are sorted)
[10:43:48] <mozmck> yes
[10:44:57] <mozmck> btw, I ran across another static website CMS:
http://get-simple.info/
[10:45:43] <seb_kuzminsky> our version numbers are slightly more complicated than what we've been talking about, for "interim builds" between the releases, since we tack on "-CommitNumber-gHash" after the release version number
[10:46:11] <seb_kuzminsky> v2.6.10-24-g61d6c88
[10:46:19] <mozmck> Seems like the buildbot packages should be mentioned a little more prominently on the website - so it is easier for those who would like to try the development version to find them.
[10:47:03] <seb_kuzminsky> the X.Y.Z is 2.6.10, then the rest indicates we're 24 commits past that release, and the commit that was built is 61d6c88
[10:47:12] <mozmck> I see. That's more like a.b.c-d-xyz!
[10:47:13] <seb_kuzminsky> mozmck: yeah, that's probably a good idea
[10:47:47] <seb_kuzminsky> those are not "official" releases, they're "interim builds" (which is a term i just made up) that are sort of like the development snapshots leading up to the next official release
[10:48:57] <mozmck> They only show up on the buildbot builds?
[10:49:06] <seb_kuzminsky> yep
[10:49:17] <seb_kuzminsky> the official releases on wlo are all numbered "x.y.z"
[10:49:36] <mozmck> I'm fine with changing to x.y - doesn't matter to me.
[10:49:50] <seb_kuzminsky> you can see how those numbers are generated by running scripts/get-version-from-git
[10:49:59] <mozmck> I've seen that
[10:50:14] <mozmck> pretty nifty
[10:50:22] <seb_kuzminsky> checkout out the current tip of 2.6 and it'll generate and x.y.z-commitnumber-gsha
[10:50:41] <seb_kuzminsky> then checkout out a release tag like v2.6.10 and it'll generate the official version number for that release
[10:51:10] <seb_kuzminsky> the release checklist wiki page discusses how to create release tags, did i show you this?
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ReleaseCheckList
[10:51:37] <mozmck> I think you did a while back. I'll read it again.
[10:51:44] <seb_kuzminsky> heh
[10:51:58] <seb_kuzminsky> i think we're a ways away from 2.8.0 (or 3.0, or whatever) so no rush
[10:52:26] <mozmck> probably so.
[11:02:07] <archivist> the argument for 3 digits is incompatible changes of the 2-3 and improvements in the .8 and bugs in the .1
[11:02:15] <alex_joni> hi guys
[11:06:05] <seb_kuzminsky> hi alex_joni
[11:06:38] <seb_kuzminsky> archivist: but we've been doign incompatible changes btween every major version (2.5 to 2.6, 2.6 to 2.7, etc)
[11:11:05] <jepler> http://semver.org/ sure has opinions about software versioning. but as we seldom make purely bugfix releases, if we followed semantic versioning we'd always be releasing x.y.0 and not using the third digit
[11:11:31] <jepler> I think two digits is enough for the style of development style and release-making that we do in linuxcnc right now
[12:07:51] <seb_kuzminsky> FernV replied privately to my email about LinuxCNC Features. he said nick was the original developer but has not been actively maintaining Features for "some time". Fern claims to not be a developer, but that he fixed some bugs and made it more user friendly, and then Nick picked up all Fern's changes into his repo
[12:09:44] <mozmck> interesting.
[12:10:45] <skunkworks> that sounds messy...
[12:10:52] <cradek> well it could just be done
[12:11:00] <cradek> sometimes it's hard to tell done from abandoned
[12:11:31] <seb_kuzminsky> Fern said he would need help integrating Features with LinxuCNC's repo & packaging
[12:11:59] <cradek> so would anyone
[12:21:22] <mozmck> If I have a max velocity set for each axis, is there a good reason to set a TRAJ MAX_VELOCITY?
[12:21:51] <cradek> probably not on a trivkins machine
[12:22:29] <mozmck> ok, I have not had it set and had no problems, but Gscreen issues a warning about it.
[12:22:53] <cradek> hmm if a gui uses it for the top of a slider or something, maybe you need it
[12:23:12] <mozmck> Yeah, I don't in my skin though.
[12:24:00] <mozmck> I use a percentage slider (0 - 100%) and set the jog rate of each axis to that percentage of it's max vel
[13:07:00] <skunkworks> mozmck, you guys get mentioned I noticed about changing to linuxcnc...
[13:07:45] <skunkworks> http://www.plasmaspider.com/viewtopic.php?f=3&p=105281
[13:11:25] <mozmck> skunkworks: neat! thanks. I don't browse forums much.
[13:30:15] <skunkworks> you know what is interesting.. I do a lot of google searching - I don't think I have ever gotten a hit from a yahoo group.
[13:30:20] <skunkworks> that seems like a waste.
[13:32:19] <mozmck> maybe yahoo doesn't let google index their group pages.
[13:32:34] <mozmck> have you tried searching yahoo?
[13:36:59] <skunkworks> in my experience google gives me results I am looking for. (yahoo not so much)
[13:37:15] <skunkworks> but maybe I am better speaking google than yahoo
[13:37:29] <mozmck> yeah, I just wondered if yahoo would show results from their groups.
[13:37:40] <skunkworks> right- I will have to try that.
[13:38:07] <skunkworks> it is funny that it just dawned on me that I never get yahoo group results.
[14:53:43] <KGB-linuxcnc> 03John Morris 05zultron/remap-startline-fix 2afd00a 06linuxcnc 10src/emc/task/emctaskmain.cc Bugfix: Start line and remap interaction * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2afd00a
[14:55:25] <seb_kuzminsky> woo!
[15:04:47] <jepler> jthornton: when you have a chance, can you put up a notice that the forum migration will be the weekend of 5/6 november and that the forum will be set to read-only mode before the migration starts? thank you!
[15:05:25] <Tom_itx> moving it to your server?
[15:06:18] <jepler> Tom_itx: I'll be hosting it on a digitalocean.com vps actually
[15:06:29] <seb_kuzminsky> awesome
[15:06:34] <jepler> but the real point is modernizing the installs of joomla and kunena
[15:06:40] <Tom_itx> the one you've been testing here
[15:06:41] <jepler> and separating it from the www.linuxcnc.org website
[15:06:43] <jepler> right
[15:07:02] <Tom_itx> good idea
[15:07:56] <jepler> Some other people have expressed interest in having a main website that is generated by a static website generator and version controlled by git, and I hope they will step forward and do that soon after the forum is moved
[15:08:36] <Tom_itx> yeah it could use a facelift
[15:08:38] <jepler> due to the large volume of files that www.linuxcnc.org hosts, I think we'll want to leave that on dreamhost because they have unlimited disk
[15:16:37] <jepler> in ~24 hours (October 26 in PDT -0700 time zone) there were 1618 unique hosts in 1507 different class Cs requesting the "Release" file of our deb repositories
[15:17:35] <jepler> lucid saw requests from 720 unique class Cs (the most), wheezy saw 620 (second) and others saw fewer than 200
[15:20:06] <jepler> ("Release" is one of the files that will be automatically fetched when getting the list of available updates)
[15:21:34] <jepler> looking at 2 days data instead of 1, there are 2152 unique hosts in 2119 unique class Cs represented
[15:23:07] <jepler> so there are thousands of turned-on, net-connected linuxcnc systems out there checking for updates
[15:26:48] <KGB-linuxcnc> 03John Morris 05zultron/subs-follow-main-fix 69aeafd 06linuxcnc 10src/emc/rs274ngc/interp_o_word.cc 03tests/interp/m98m99/08-sub-follows-main/expected 03tests/interp/m98m99/08-sub-follows-main/test.ngc 03tests/interp/m98m99/08-sub-follows-main/test.sh Fix subs breaking when placed after main program * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=69aeafd
[15:28:37] <andypugh> jepler: That’s quite a lot, and possibly less than half of them.
[15:28:58] <andypugh> If we charged $100 we would still be poor, though.
[15:29:51] <jepler> yeah better to charge £100, that's real money
[15:30:02] <jepler> but let's face it, who would pay money for linuxcnc
[15:31:43] <andypugh> Possibly a sizable group who don’t trust free sotfware.
[15:33:48] <jepler> don't get me started
[15:33:54] <jepler> have you *used* commercial software?
[15:36:02] <jepler> (said the guy with the irrational distrust of commercial software)
[15:57:35] <andypugh> I am using Autodesk Inventor as we speak
[15:57:53] <andypugh> The CAM is excellent, but my demo license expires tomorrow.
[15:58:22] <andypugh> (for the CAM, I have a legitimate license for the CAD software)
[16:13:03] <linuxcnc-build> build #1756 of 1405.rip-wheezy-armhf is complete: Failure [4failed apt-get-update compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/1756 blamelist: John Morris <john@zultron.com>
[16:22:28] <skunkworks> zlog:
[16:25:03] <skunkworks> we have m98,99 now?
[16:29:30] <linuxcnc-build> build #3567 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/3567 blamelist: John Morris <john@zultron.com>
[16:30:47] <linuxcnc-build> build #3569 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/3569 blamelist: John Morris <john@zultron.com>
[16:31:18] <linuxcnc-build> build #3568 of 1200.rip-lucid-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/3568 blamelist: John Morris <john@zultron.com>
[16:44:51] <linuxcnc-build> build #2776 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/2776 blamelist: John Morris <john@zultron.com>
[16:53:21] <linuxcnc-build> build #3568 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/3568 blamelist: John Morris <john@zultron.com>
[17:06:15] <linuxcnc-build> build #3571 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/3571 blamelist: John Morris <john@zultron.com>
[17:09:01] <KGB-linuxcnc> 03John Morris 05zultron/subs-follow-main-fix a636070 06linuxcnc 03tests/interp/subs-follow-main/expected 03tests/interp/subs-follow-main/test.ngc 03tests/interp/subs-follow-main/test.sh Fix subs breaking when placed after main program * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a636070
[17:11:22] <linuxcnc-build> build #1728 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/1728 blamelist: John Morris <john@zultron.com>
[17:14:34] <linuxcnc-build> build #1727 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/1727 blamelist: John Morris <john@zultron.com>
[17:14:36] <linuxcnc-build> build #1238 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/1238 blamelist: John Morris <john@zultron.com>
[17:14:53] <linuxcnc-build> build #1919 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/1919 blamelist: John Morris <john@zultron.com>
[17:22:01] <jthornton> jepler, done
[17:22:03] <KGB-linuxcnc> 03John Morris 05zultron/subs-follow-main-fix 3302db2 06linuxcnc 10src/emc/rs274ngc/interp_o_word.cc 03tests/interp/subs-follow-main/expected 03tests/interp/subs-follow-main/test.ngc 03tests/interp/subs-follow-main/test.sh Fix subs breaking when placed after main program * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3302db2
[17:25:41] <jepler> jthornton: thank you
[17:26:09] <jepler> hmm except I said nonsense dates :-P
[17:27:12] <jepler> 6/7, I can work with that
[17:27:35] <JT-Shop> I can change them
[17:27:44] <jepler> it's OK
[17:27:48] <JT-Shop> 7/8?
[17:27:53] <jepler> yeah that's what I meant
[17:28:00] <jepler> not sure what month of calendar I looked at
[17:28:00] <JT-Shop> I'll fix it
[17:28:02] <jepler> thanks
[17:30:35] <JT-Shop> fixed
[17:30:48] <linuxcnc-build> build #1391 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/1391 blamelist: John Morris <john@zultron.com>
[17:33:03] <linuxcnc-build> build #195 of 1502.rip-jessie-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1502.rip-jessie-amd64/builds/195 blamelist: John Morris <john@zultron.com>
[17:35:00] <linuxcnc-build> build #195 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/195 blamelist: John Morris <john@zultron.com>
[17:35:18] <linuxcnc-build> build #195 of 1503.rip-jessie-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1503.rip-jessie-rtpreempt-amd64/builds/195 blamelist: John Morris <john@zultron.com>
[17:37:25] <linuxcnc-build> build #195 of 1501.rip-jessie-rtpreempt-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1501.rip-jessie-rtpreempt-i386/builds/195 blamelist: John Morris <john@zultron.com>
[17:37:25] <linuxcnc-build> build #3580 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3580 blamelist: John Morris <john@zultron.com>
[18:00:18] <linuxcnc-build> build #3569 of 1200.rip-lucid-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/3569 blamelist: John Morris <john@zultron.com>, dummy
[18:00:24] <linuxcnc-build> build #3568 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/3568 blamelist: John Morris <john@zultron.com>, dummy
[18:00:33] <linuxcnc-build> build #3569 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/3569 blamelist: John Morris <john@zultron.com>, dummy
[18:01:16] <linuxcnc-build> build #3570 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/3570 blamelist: John Morris <john@zultron.com>, dummy
[18:04:11] <linuxcnc-build> build #1728 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/1728 blamelist: John Morris <john@zultron.com>, dummy
[18:04:19] <linuxcnc-build> build #1729 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/1729 blamelist: John Morris <john@zultron.com>, dummy
[18:04:39] <linuxcnc-build> build #2777 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/2777 blamelist: John Morris <john@zultron.com>, dummy
[18:04:44] <linuxcnc-build> build #1920 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/1920 blamelist: John Morris <john@zultron.com>, dummy
[18:05:21] <KGB-linuxcnc> 03John Morris 05zultron/subs-follow-main-fix 6afa3c7 06linuxcnc 10src/emc/rs274ngc/interp_o_word.cc 03tests/interp/subs-follow-main/expected 03tests/interp/subs-follow-main/test.ngc 03tests/interp/subs-follow-main/test.sh Fix subs breaking when placed after main program * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6afa3c7
[18:05:35] <linuxcnc-build> build #1239 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/1239 blamelist: John Morris <john@zultron.com>, dummy
[18:05:56] <linuxcnc-build> build #1757 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/1757 blamelist: John Morris <john@zultron.com>, dummy
[18:06:11] <linuxcnc-build> build #196 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/196 blamelist: John Morris <john@zultron.com>, dummy
[18:06:22] <linuxcnc-build> build #196 of 1502.rip-jessie-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1502.rip-jessie-amd64/builds/196 blamelist: John Morris <john@zultron.com>, dummy
[18:06:33] <linuxcnc-build> build #1392 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/1392 blamelist: John Morris <john@zultron.com>, dummy
[18:06:53] <linuxcnc-build> build #196 of 1503.rip-jessie-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1503.rip-jessie-rtpreempt-amd64/builds/196 blamelist: John Morris <john@zultron.com>, dummy
[18:06:58] <linuxcnc-build> build #196 of 1501.rip-jessie-rtpreempt-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1501.rip-jessie-rtpreempt-i386/builds/196 blamelist: John Morris <john@zultron.com>, dummy
[18:07:39] <KimK_laptop> This docs format is nice, two separately scrollable windows:
http://docs.kicad-pcb.org/en/eeschema.html
[18:15:42] <linuxcnc-build> build #3572 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/3572 blamelist: John Morris <john@zultron.com>, dummy
[18:15:42] <linuxcnc-build> build #3581 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3581 blamelist: John Morris <john@zultron.com>, dummy
[18:50:10] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 ba70d82 06linuxcnc 10src/emc/motion-logger/motion-logger.c motion-logger: fix mock of SET_POSITION_LIMITS * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ba70d82
[18:52:33] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6-mountaindew 86dc81b 06linuxcnc 10(10 files in 2 dirs) tests: add a motion-logger test of a possible remap bug * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=86dc81b
[19:41:44] <jepler> -mountaindew?
[19:57:48] <seb_kuzminsky> it's the cnczone handle of the guy who reported that bug
[19:58:00] <seb_kuzminsky> which doesn't look like a bug to me
[20:01:19] <jepler> ah
[20:08:02] <jepler> ugh run from line and remap
[20:41:05] <seb_kuzminsky> jepler, zultron: i dont think it's a real bug
[20:41:44] <seb_kuzminsky> the repro gcode program that mountaindew produced, that zultron wrote his fix for, had a bug (nested (comments))
[20:42:03] <seb_kuzminsky> fix that bug and it runs fine as far as i can tell
[20:50:43] <jepler> particularly if (nested (comments)) will make the interpreter go out to lunch, I would be happy to see it be an error instead
[20:51:12] <KGB-linuxcnc> 03Jeff Epler 05jepler/hm2-explicit-queue-write c339d1e 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hm2_eth.c 10src/hal/drivers/mesa-hostmot2/hostmot2-lowlevel.h 10src/hal/drivers/mesa-hostmot2/hostmot2.c hm2_eth: make write queueing explicit, not implicit * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c339d1e
[20:51:12] <KGB-linuxcnc> 03Jeff Epler 05jepler/hm2-explicit-queue-write 66ca88f 06linuxcnc 10src/hal/drivers/mesa-hostmot2/hostmot2.c hm2_eth: explicitly queue up writes from force_write * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=66ca88f
[20:51:19] <jepler> READ => (nested (comments))
[20:51:20] <jepler> Nested comment found
[20:51:21] <jepler> oh look it does
[20:51:54] <jepler> though the message sure doesn't tell you much
[20:52:16] <jepler> .. what is the consequence of nested comments? shrug
[20:57:50] <skunkworks> it is probably a remap issue
[21:07:41] <seb_kuzminsky> task says:
[21:07:45] <seb_kuzminsky> > emc/task/emctask.cc 389: interp_error: Nested comment found
[21:07:54] <seb_kuzminsky> > emcTaskPlanClose() called at emc/task/emctaskmain.cc:768
[21:08:08] <seb_kuzminsky> yay, tuesday night == hackspace night!
[21:08:19] <seb_kuzminsky> imma start wiring up the new robot arm controller :-)
[21:08:20] <seb_kuzminsky> bbl
[21:16:17] <jepler> fun
[21:55:45] <linuxcnc-build> build #3572 of 1200.rip-lucid-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/3572 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[21:58:53] <linuxcnc-build> build #3571 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/3571 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[21:58:54] <linuxcnc-build> build #3573 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/3573 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:06:49] <linuxcnc-build> build #2780 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/2780 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:06:49] <linuxcnc-build> build #1732 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/1732 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:09:28] <linuxcnc-build> build #1731 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/1731 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:15:36] <linuxcnc-build> build #3572 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/3572 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:19:38] <linuxcnc-build> build #199 of 1502.rip-jessie-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1502.rip-jessie-amd64/builds/199 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:20:38] <linuxcnc-build> build #1395 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/1395 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:21:03] <linuxcnc-build> build #199 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/199 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:30:52] <linuxcnc-build> build #3575 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/3575 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[22:30:52] <linuxcnc-build> build #3584 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3584 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[23:12:10] <linuxcnc-build> build #2885 of 4003.deb-lucid-i386 is complete: Failure [4failed apt-get-update shell_1] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/2885 blamelist: Jeff Epler <jepler@unpythonic.net>
[23:12:44] <seb_kuzminsky> derp
[23:14:11] <linuxcnc-build> build #801 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_1] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/801 blamelist: Jeff Epler <jepler@unpythonic.net>
[23:17:02] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6-mountaindew c7dd463 06linuxcnc 10tests/motion-logger/mountaindew/checkresult mountaindew test: verify the result in the right directory * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c7dd463