Back
[00:43:38] <linuxcnc-build> build #4468 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4468 blamelist: Jeff Epler <jepler@unpythonic.net>
[00:49:22] <seb_kuzminsky> jepler: ok, your push to master is currently building with all apt sources updated to include linuxcnc.org base
[01:07:59] <linuxcnc-build> build #4454 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/4454 blamelist: Jeff Epler <jepler@unpythonic.net>, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <bjt128@gmail.com>
[01:23:47] <linuxcnc-build> build #4469 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4469 blamelist: Jeff Epler <jepler@unpythonic.net>, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <bjt128@gmail.com>
[07:17:24] <jepler> seb_kuzminsky: rip-precise-amd64 is just a generic kernel !??
[07:18:48] <jepler> successfully configured for 'uspace-Debian-7.11'-'uspace+rtai+xenomai'..
[07:19:04] <jepler> checking for realtime API(s) to use... uspace+lxrt+xenomai
[07:19:19] <jepler> yay rip-wheezy-i386 configures right
[07:20:40] <jepler> rip-wheezy-amd64 didn't configure for uspace+lxrt+xenomai but I think that's expected because there's no rtai kernel package for wheezy-amd64
[07:24:58] <jepler> and since rip-precise-amd64 crashed and burned for unrelated reasons, we don't know how the pbuildering step went
[08:53:14] <seb_kuzminsky> linuxcnc-build: force build --branch=master 0000.checkin
[08:53:15] <linuxcnc-build> build forced [ETA 13h09m11s]
[08:53:15] <linuxcnc-build> I'll give a shout when the build finishes
[09:09:44] <linuxcnc-build> build #4455 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/4455
[09:27:52] <jepler> !!! what now !!!
[09:27:54] <jepler> same as the last failure?
[09:28:19] <cradek> oh my
[09:28:51] <cradek> on emc-users someone notices the initial startup conditions being wrong (offsets not showing in the dro), and caused me to test 2.7.5 where it is NOT broken
[09:29:21] <linuxcnc-build> build #4470 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4470
[09:29:26] <cradek> what is happen
[09:29:39] <cradek> I guess I'll bisect
[09:29:53] <cradek> what a swirl
[09:40:55] <seb_kuzminsky> jepler: looks like that problem where realtime fails to shut down in a timely fashion, and then the next test(s) fail(s)
[09:41:01] <seb_kuzminsky> cradek: thanks for looking in to it
[09:41:04] <seb_kuzminsky> bbl
[09:46:15] <cradek> 8fffa9d1569be967a9f137cfceca6b0879de2edf is the first bad commit
[09:46:22] <cradek> Revert "Task: simplify handling of emcCommand"
[09:46:24] <cradek> fff
[09:47:32] <cradek> wait, this change was supposed to have no effect
[09:49:15] <cradek> I'm going to apply 516deae (which from the commit log I think is supposed to make no difference) to the tip of 2.7 and see if that fixes it
[09:52:18] <cradek> .... no
[09:52:19] <cradek> it doesn't
[09:57:27] <cradek> these are all mergeups so I should be testing 2.6
[09:57:32] <cradek> 2.6.11 works right; 2.6.12 does not
[09:58:28] <cradek> wait 2.6.12 works too
[09:59:07] <jepler> cradek: what problem are you chasing? the buildbot failures are leftover linuxcnc lock files, I think
[09:59:26] <jepler> after an original problem where the vm got sick and buildbot killed the test in prgress
[09:59:56] <cradek> dro wrong at startup: active g5x offset is not shown, preview display of axes/origins is wrong in the same way
[10:00:00] <jepler> ah ok
[10:00:34] <cradek> ok 2.6 tip is bad; 2.6.12 (last release) is good
[10:00:55] <cradek> I think seb accidentally fixed this when breaking the other stuff that he's now reverted
[10:01:54] <cradek> https://i.ytimg.com/vi/dpTNxlVNw-0/hqdefault.jpg
[10:11:17] <seb_kuzminsky> cradek: what's the repro recipe?
[10:11:57] <cradek> start sim/axis and look at the extended dro - if it says g53 that's wrong
[10:12:07] <seb_kuzminsky> thx
[10:13:34] <cradek> more: save a g54 offset and restart; notice you don't get the two origins when AXIS is in relative mode; mdi motion is correct and honors the saved offset but the preview origin/dro is wrong
[10:14:13] <cradek> I'm bisecting in 2.6 now
[10:14:18] <seb_kuzminsky> if you look at the stat buffer (with linuxcnctop or python), does that have the wrong g5x_index and _offsets?
[10:14:27] <seb_kuzminsky> (i guess i should just try, instead of bugging you about it)
[10:14:28] <cradek> yes index is 0, which it never should be
[10:14:54] <seb_kuzminsky> i fear that the bisect will point at me....
[10:14:57] <cradek> b996c7708612e8468961b89cffd6869d5340f0dd is the first bad commit
[10:15:30] <cradek> // cause the interpreter's starting offset to be reflected
[10:15:32] <cradek> !!!
[10:15:56] <cradek> you took out the thing and it stopped doing the thing it said the thing would do
[10:16:08] <cradek> lemme try putting just that back at the tip of 2.6
[10:16:43] <seb_kuzminsky> derp
[10:16:59] <cradek> if it's a one line fix that would make bunny cry less
[10:18:33] <cradek> yes reverting b996c77 fixes 2.6 branch
[10:21:04] <seb_kuzminsky> that makes me cry more
[10:21:53] <cradek> maybe the things after emcTaskPlanInit() in emctask_startup() nuke/re-clear the stat buffer
[10:22:06] <seb_kuzminsky> because a few lines above the line that b996c77 took out it calls emctask_startup(), which calls emcTaskPlanInit()
[10:22:31] <seb_kuzminsky> ... yeah
[10:22:38] <cradek> maybe the TaskPlanInit before TaskInit is ordered wrong
[10:23:03] <seb_kuzminsky> "Idempotent is a good word." "You can say *that* again!"
[10:23:25] <seb_kuzminsky> well thanks for unhorking it
[10:23:30] * seb_kuzminsky backs away from Task
[10:25:05] <cradek> I don't see anything smoking in emcTaskInit()
[11:38:07] <cradek> // set the default startup modes: emcTaskSetState(EMC_TASK_STATE_ESTOP);
[11:38:37] <cradek> this calls emcTaskAbort which clears the interplist, discarding 4 important setup messages
[12:11:50] <cradek> think I've nailed it
[12:22:51] <seb_kuzminsky> nice
[12:23:32] <seb_kuzminsky> i think my removal of the second emcTaskIPlanInit() was only valid along with the drain_interp_list flag i added about the same time
[12:23:42] <seb_kuzminsky> it would preserve those startup NML commands
[12:40:12] <KGB-linuxcnc> 03Sebastian Kuzminsky 05seb/2.6/startup-state-test e47321e 06linuxcnc 10(8 files) add a test validating the startup state of the Status buffer * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e47321e
[12:40:33] <seb_kuzminsky> that test passes on 2.6.12, but reproduces the g5x_index problem in the tip of 2.6
[12:40:36] <KGB-linuxcnc> 03Chris Radek 05cradek/2.6/interp-startup 92760ae 06linuxcnc 10src/emc/task/emctaskmain.cc Fix startup regression regarding coordinate systems and more * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=92760ae
[12:40:36] <KGB-linuxcnc> 03Chris Radek 05cradek/2.6/interp-startup 7a24584 06linuxcnc 10(6 files) Test initial coordinate system and RS274NGC_STARTUP_CODE * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7a24584
[12:40:47] <cradek> oh guess what - I wrote a test too
[12:41:00] <seb_kuzminsky> good :-)
[12:41:21] <cradek> and you beat me to the buildbot by a few seconds
[12:42:01] <seb_kuzminsky> buti didn't write a fix to go with it
[12:42:40] <cradek> you tested more of the stat init, but I also tested STARTUP_CODE
[12:43:23] <cradek> let's come back in a few hours and decide what to keep...
[12:45:14] <seb_kuzminsky> good plan
[12:45:21] <seb_kuzminsky> thanks a ton for fixing my mess
[12:48:21] <seb_kuzminsky> cradek: i merged my test into your fix branch and it failed in a new place:
[12:48:38] <seb_kuzminsky> assert(s.spindle_brake == 1)
[12:48:39] <seb_kuzminsky> AssertionError
[12:50:14] <seb_kuzminsky> merging my test into 2.6 it gets detects the g5x_index bug, but spindle_brake is correct
[12:50:47] * seb_kuzminsky returns to $DAYJOB, will come back to this later
[13:08:05] <cradek> hmm thanks, I need to look closer
[13:10:28] <linuxcnc-build> build #4456 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/4456 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[13:17:37] <cradek> ok that fixes it
[13:18:03] <cradek> thanks for your much more complete test
[13:23:30] <cradek> startup messages are different; a bunch of tests are going to fail
[13:23:37] <cradek> stupidly I didn't run them all (soooo slow)
[13:23:48] <cradek> I'll keep poking at it
[13:27:23] <linuxcnc-build> build #4471 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4471 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[13:28:45] <seb_kuzminsky> ugh, somebody is mirroring all of the buildbot's dists/
[13:28:57] <seb_kuzminsky> but on the plus side, i got to learn about apache's mod_bw today
[13:36:28] <jepler> seb_kuzminsky: how big is the public www area on buildbot? would it make more sense to push it out to the internet (dreamhost) or are most of the files downloaded so infrequently that it wouldn't be a benefit on your overall bandwidth usage?
[13:37:01] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron opened pull request #147: M30 remap interaction lcnc26 (062.6...06m30-remap-interaction-lcnc26) 02
https://github.com/LinuxCNC/linuxcnc/pull/147
[13:49:09] <linuxcnc-build> build #4457 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/4457 blamelist: Chris Radek <chris@timeguy.com>
[13:49:58] <linuxcnc-build> build #2616 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/2616 blamelist: Chris Radek <chris@timeguy.com>
[13:50:49] <linuxcnc-build> build #1084 of 1520.rip-jessie-amd64 is complete: Failure [4failed apt-get-update compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1520.rip-jessie-amd64/builds/1084 blamelist: Chris Radek <chris@timeguy.com>
[13:50:53] <linuxcnc-build> build #2616 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/2616 blamelist: Chris Radek <chris@timeguy.com>
[13:52:05] <linuxcnc-build> build #4455 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/4455 blamelist: Chris Radek <chris@timeguy.com>
[13:53:14] <linuxcnc-build> build #2282 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/2282 blamelist: Chris Radek <chris@timeguy.com>
[13:53:33] <linuxcnc-build> build #4457 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/4457 blamelist: Chris Radek <chris@timeguy.com>
[13:53:46] <linuxcnc-build> build #1084 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/1084 blamelist: Chris Radek <chris@timeguy.com>
[13:53:47] <linuxcnc-build> build #4457 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/4457 blamelist: Chris Radek <chris@timeguy.com>
[13:55:53] <linuxcnc-build> build #3667 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/3667 blamelist: Chris Radek <chris@timeguy.com>
[14:01:11] <seb_kuzminsky> jepler:
[14:01:13] <seb_kuzminsky> 0 12:33:20 seb@buildmaster /home/buildmaster/public_html> sudo du -scm * | sort -rn
[14:01:16] <seb_kuzminsky> 21995 total
[14:01:19] <seb_kuzminsky> 12880 dists
[14:01:22] <seb_kuzminsky> 7778 release
[14:01:24] <seb_kuzminsky> 822 clang
[14:01:27] <seb_kuzminsky> 475 doc
[14:01:29] <seb_kuzminsky> 42 hm2
[14:01:39] <seb_kuzminsky> i think it's fine to keep it here
[14:07:05] <cradek> seb_kuzminsky: now I'm matching the entire old startup, except for not doing a couple things twice in a row. new push coming as soon as my tests run
[14:08:50] <linuxcnc-build> build #4468 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/4468 blamelist: Chris Radek <chris@timeguy.com>
[14:08:51] <linuxcnc-build> build #4472 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4472 blamelist: Chris Radek <chris@timeguy.com>
[14:09:14] <cradek> linuxcnc-build: now please stay idle for a few minutes
[14:15:14] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron opened pull request #148: "duplicate O-word label" in remap 2.6 (062.6...06remap-dup-oword-lcnc-2.6) 02
https://github.com/LinuxCNC/linuxcnc/pull/148
[14:23:03] <KGB-linuxcnc> 03Chris Radek 05cradek/2.6/interp-startup 85210a3 06linuxcnc 10src/emc/task/emctaskmain.cc 10tests/motion-logger/basic/expected.builtin-startup.in 10tests/motion-logger/mountaindew/expected.motion-logger Fix startup regression regarding coordinate systems and more * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=85210a3
[14:23:03] <KGB-linuxcnc> 03Chris Radek 05cradek/2.6/interp-startup 61ad22a 06linuxcnc 10(6 files) Test initial coordinate system and RS274NGC_STARTUP_CODE * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=61ad22a
[14:23:03] <KGB-linuxcnc> 03Sebastian Kuzminsky 05cradek/2.6/interp-startup 588b186 06linuxcnc 10(8 files) add a test validating the startup state of the Status buffer * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=588b186
[14:33:26] <andypugh> Homing to absolute scales. Any ideas how to do it in 2.7.6? (I have recommended Master).
https://forum.linuxcnc.org/forum/49-basic-configuration/31427-absolute-linear-scales#79035
[14:40:33] <linuxcnc-build> build #4458 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/4458 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>, Chris Radek <chris@timeguy.com>
[14:48:52] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron opened pull request #149: Remap IO M62-M68 2.6 (06master...06remap-io-lcnc-2.6) 02
https://github.com/LinuxCNC/linuxcnc/pull/149
[14:49:45] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron closed pull request #149: Remap IO M62-M68 2.6 (06master...06remap-io-lcnc-2.6) 02
https://github.com/LinuxCNC/linuxcnc/pull/149
[14:50:24] <jepler> cradek: will you keep looking at those interpreter PRs? I feel like I'm not as qualified to do it as you
[14:50:36] <jepler> ugh not sure why we'd accept interpreter changes in 2.6 though
[14:50:47] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron reopened pull request #149: Remap IO M62-M68 2.6 (062.6...06remap-io-lcnc-2.6) 02
https://github.com/LinuxCNC/linuxcnc/pull/149
[14:52:35] <cradek> I'll do my best, probably won't be this weekend at all
[14:54:10] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #149: (the 2.6 branch isn't enabled for travis-ci at the moment. I think the switch of base branch caused travis-ci to think it could build, but it can't because required scripts are missing whch led to the reported failure.) 02
https://github.com/LinuxCNC/linuxcnc/pull/149#issuecomment-241112534
[14:59:35] <cradek> rip-precise-amd64 seems stuck
[14:59:55] <cradek> but cradek/2.6/interp-startup does look ok now I think
[15:02:33] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron opened pull request #150: Fix subs breaking when placed after main program 2.6 (062.6...06subs-follow-main-lcnc-2.6) 02
https://github.com/LinuxCNC/linuxcnc/pull/150
[15:02:33] <linuxcnc-build> build #4473 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4473 blamelist: dummy, Sebastian Kuzminsky <seb@highlab.com>, Chris Radek <chris@timeguy.com>
[15:17:33] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron opened pull request #151: M98/M99 subprograms (06master...06m98m99-lcnc) 02
https://github.com/LinuxCNC/linuxcnc/pull/151
[15:19:06] <cradek> wow
[15:24:07] <KGB-linuxcnc> 03Chris Radek 052.7 df183a4 06linuxcnc 10src/emc/task/emctaskmain.cc 10tests/motion-logger/basic/expected.builtin-startup.in 10tests/motion-logger/mountaindew/expected.motion-logger Merge branch '2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=df183a4
[15:24:39] <KGB-linuxcnc> 03Chris Radek 052.6 588b186 06linuxcnc fast forward * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=588b186
[15:27:57] <KGB-linuxcnc> 03John Morris 05glo/zultron/remap-io-lcnc-2.6 e007416 06linuxcnc 10(22 files in 2 dirs) Enable remap of M62-M68 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e007416
[15:32:17] <seb_kuzminsky> cradek: thanks!!
[15:33:23] <seb_kuzminsky> are you going to merge 2.7 into master too, or do you want me to do that one?
[15:33:43] <seb_kuzminsky> i left my task fix/breakage in master, so there might be conflicts or other problems there...
[15:42:28] <linuxcnc-build> build #4459 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/4459 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[15:43:29] <seb_kuzminsky> rip-precise-amd64: wth is wrong with you
[15:45:08] <cradek> seb_kuzminsky: it'd be nice if you felt like doing the last merge
[15:46:02] <cradek> seb_kuzminsky: I have only barely kept up with what's going on with those changes - I'm not even sure what design we're working toward (what should abort do, are we going to use state-tags to do it in master)
[15:46:36] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron opened pull request #152: interp_o_word.cc: remove unused `tmpFileName` variable (062.6...06remove-unused-var-lcnc) 02
https://github.com/LinuxCNC/linuxcnc/pull/152
[15:47:18] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #149: Whoops, meant to submit against 2.6; try again 02
https://github.com/LinuxCNC/linuxcnc/pull/149#issuecomment-241111461
[15:52:05] <cradek> seb_kuzminsky: my feelings say the answers to that are: in the stable branches abort should stop and not change the interpreter state (it remains in readahead state I guess) and in master state-tags should be used to reset it to what was currently executing, as much as possible (I doubt it'll work right with cutter comp etc)
[16:02:34] <seb_kuzminsky> ok, i'll do the merge of 2.7 into master
[16:02:46] <seb_kuzminsky> and i'd love to have a conversation about what the design for abort should be...
[16:03:03] <cradek> hm, "I doubt it'll work right" is a really shitty design spec
[16:04:12] <cradek> yeah it seems like you and I and zultron should probably do that before we bother hacking on it any more
[16:05:09] <cradek> one of his comments was like "I believe the linuxcnc folks want it to ___" and it's unfair making him guess
[16:05:36] <linuxcnc-build> build #4474 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4474 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[16:09:25] <cradek> yeah whatevs
[16:27:29] <linuxcnc-build> build #4460 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/4460 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[16:28:42] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron closed pull request #152: interp_o_word.cc: remove unused `tmpFileName` variable (062.6...06remove-unused-var-lcnc) 02
https://github.com/LinuxCNC/linuxcnc/pull/152
[16:43:25] <jmk-mcfaul_> I have a tentative revision of tests/limit3.1 that hopefully will pass on all buildbots
[16:44:12] <jmk-mcfaul_> you guys seem to be driving the buildbot slightly nuts already, is there a way to test my thing without interfering?
[16:45:52] <jepler> it's a piñata today isn't it
[16:46:08] <jepler> jmk-mcfaul_: if you create a pull request I can feed it to buildbot for you.
[16:47:11] <linuxcnc-build> build #4475 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4475 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[16:47:38] <jmk-mcfaul_> preparing PR...
[16:48:51] <jepler> Machine configuration file is 'linuxcncrsh-test.ini'
[16:48:51] <jepler> Application initialization failed: no display name and no $DISPLAY environment variable
[16:48:54] <jepler> Not starting new LinuxCNC
[16:49:21] <jepler> so the failure on rip-precise-amd64 continues to be that it detects linuxcnc still running
[16:49:49] <jepler> that's a file in /tmp that may not be cleaned up by a mere reboot...
[16:50:49] <seb_kuzminsky> but earlier linuxcnc invocations work
[16:50:53] <seb_kuzminsky> like abs.0
[16:51:11] <jepler> abs.0 isn't a linuxcnc invocation, it's just a halrun invocation
[16:51:18] <seb_kuzminsky> err, hmm, right
[16:51:34] <seb_kuzminsky> yes:
[16:51:35] <seb_kuzminsky> -rw-r--r-- 1 buildslave buildslave 0 Aug 18 20:53 linuxcnc.lock
[16:52:09] <seb_kuzminsky> linuxcnc-build: force build --branch=master 1306.rip-precise-amd64
[16:52:14] <linuxcnc-build> The build has been queued, I'll give a shout when it starts
[16:52:22] <seb_kuzminsky> sigh
[16:52:29] <seb_kuzminsky> sorry for all the noise
[16:53:12] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jmkasunich opened pull request #153: revise limit3.1 test to deal with rounding effects (06master...06master) 02
https://github.com/LinuxCNC/linuxcnc/pull/153
[16:55:15] <KGB-linuxcnc> 03John Kasunich 05master a9284c6 06linuxcnc 10tests/limit3.1/expected 04tests/limit3.1/skip 10tests/limit3.1/test.hal revise limit3.1 test to deal with rounding effects * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a9284c6
[16:58:17] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #149: Thanks, @jepler. I pushed to glo; buildbot results [here][1]... 02
https://github.com/LinuxCNC/linuxcnc/pull/149#issuecomment-241140479
[17:03:41] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15cradek closed pull request #153: revise limit3.1 test to deal with rounding effects (06master...06master) 02
https://github.com/LinuxCNC/linuxcnc/pull/153
[17:04:56] <jepler> umm well I didn't do what I intended with git 10 minutes ago
[17:05:09] <jepler> I even looked at the output of git push --dry-run and didn't see that I did it wrong
[17:05:21] <jepler> jmk-mcfaul_: so I apparently went ahead and shoved that into our master branch, my mistake.
[17:05:32] <jepler> we'll just fix it if it's still broke
[17:06:11] <jmkasunich> hopefully it won't be broke
[17:12:38] <linuxcnc-build> build #4461 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/4461 blamelist: John Morris <john@zultron.com>
[17:12:38] <linuxcnc-build> build forced [ETA 22m01s]
[17:12:38] <linuxcnc-build> I'll give a shout when the build finishes
[17:15:10] <KGB-linuxcnc> 03John Morris 05zultron/subs-follow-main-lcnc-2.6 32bf073 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=32bf073
[17:17:08] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #150: Pushed to glo; I expect buildbot results to be [here][1]... 02
https://github.com/LinuxCNC/linuxcnc/pull/150#issuecomment-241144267
[17:18:45] <seb_kuzminsky> http://i.imgur.com/6NfmQ.jpg
[17:28:47] <linuxcnc-build> build #4476 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4476 blamelist: John Morris <john@zultron.com>
[17:33:18] <linuxcnc-build> Hey! build 1306.rip-precise-amd64 #4462 is complete: Warnings [8warnings compile]
[17:33:18] <linuxcnc-build> Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/4462
[17:37:47] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #151: Ugh, things keep changing out from under this patch. I'll fix it later.... 02
https://github.com/LinuxCNC/linuxcnc/pull/151#issuecomment-241148082
[17:38:29] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 1090f54 06linuxcnc 10(9 files in 6 dirs) Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1090f54
[17:38:29] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 2ebaf81 06linuxcnc 10src/emc/task/taskintf.cc Task: update stat->traj.joints before iterating over it * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2ebaf81
[18:06:09] <linuxcnc-build> build #2822 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/2822 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:07:20] <seb_kuzminsky> wat
[18:07:21] <jmkasunich> drat
[18:07:52] <seb_kuzminsky> no, it's jepler's merge, not your test change
[18:07:59] <seb_kuzminsky> i think
[18:08:23] <linuxcnc-build> build #1089 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/1089 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:10:02] <seb_kuzminsky> err, not jepler's merge, but something's wonky
[18:10:42] <jmkasunich> yeah, the limit3 tests passed
[18:11:18] <seb_kuzminsky> yeah, and the tests that failed look suspiciously like the stuff chris and i were working on, but our commits aren't supposed to be in the version that got built
[18:12:01] <linuxcnc-build> build #2135 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/2135 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:13:51] <linuxcnc-build> build #2287 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/2287 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:16:18] <linuxcnc-build> build #2621 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/2621 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:16:40] <linuxcnc-build> build #1089 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/1089 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:18:06] <linuxcnc-build> build #2621 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/2621 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:18:11] <linuxcnc-build> build #1091 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/1091 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:18:41] <seb_kuzminsky> i poked around the buildslaves' build directories, and the source looks sane (correct commit checked out, no dodgy untracked or ignored files present)
[18:20:30] <linuxcnc-build> build #1089 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/1089 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:20:30] <linuxcnc-build> build #4477 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4477 blamelist: John Kasunich <jmkasunich@fastmail.fm>
[18:20:48] <seb_kuzminsky> all the buildslaves are running incredibly slow, wonder if that's related
[18:21:11] <seb_kuzminsky> check out the "task: main loop took..." messages here:
http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/2135/steps/runtests/logs/stdio
[18:22:21] <jmkasunich> on 1403.rip-wheezy-amd64: command timed out: 1200 seconds without output, attempting to kill
[18:22:32] <jmkasunich> does that means its stuck again?
[18:24:22] <seb_kuzminsky> not in the usual way
[18:24:44] <seb_kuzminsky> since finishing build 2135, that buildslave has started a new one and is making progress
[18:31:20] <jmkasunich> well, limit3.1 passed on all slaves, so I'm happy
[18:33:38] <jmk-mcfaul_> seb_kuzminsky, what is required to make a buildslave?
[18:35:21] <jmk-mcfaul_> never mind, I found buildslave admin guide
[18:36:40] <jmk-mcfaul_> I'm thinking about setting up a beaglebone buildslave
[18:36:48] <jmk-mcfaul_> just because I can
[18:45:29] <seb_kuzminsky> jmk-mcfaul_: i have an armhf wheezy buildslave (on an odroid u3), i have a second u3 (that jepler sent me) that i'm in the process of setting up as an armhf/jessie buildslave
[18:47:40] <jmk-mcfaul_> never heard of odroids before
[18:47:55] <jmk-mcfaul_> looks like much more compute power than the bone
[18:47:59] <jmk-mcfaul_> but less IO I think
[18:48:26] <jmk-mcfaul_> ewww, "all I/O interfaces are 1.8V"
[18:48:35] <jmk-mcfaul_> 3.3 is bad enough
[18:52:29] <jmk-mcfaul_> do either of those odroids run realtime?
[18:53:35] <linuxcnc-build> build #1090 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/1090 blamelist: John Morris <john@zultron.com>
[18:55:55] <linuxcnc-build> build #2622 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/2622 blamelist: John Morris <john@zultron.com>
[18:58:03] <seb_kuzminsky> jmk-mcfaul_: there's an rt-preempt kernel for them (courtesy of jepler) but the buildslaves are running vanilla kernels
[18:58:12] <seb_kuzminsky> but with uspace it doesn't matter as much
[18:59:00] <jmk-mcfaul_> my thought is to be running a buildslave (hardware and distro) that is a likely candidate for people to use as a machine controller
[18:59:18] <jmk-mcfaul_> I would be running a bone with the machinekit linux image
[19:00:10] <jmk-mcfaul_> Linux beaglebone 3.8.13-xenomai-r78 #1 Sat Sep 26 16:54:43 UTC 2015 armv7l GNU/Linux
[19:00:45] <jmk-mcfaul_> actually I would be running the latest rev of that image - I downloaded this one in Feb, I think the most recent is june
[19:00:46] <seb_kuzminsky> the linuxcnc.deb you built on a beaglebone would be the same as a linuxcnc.deb build on any other armhf, right?
[19:00:55] <jmk-mcfaul_> I don't know anything about debs
[19:01:12] <jmk-mcfaul_> since my tinkering requires a few custom comps, I use rip
[19:01:41] <seb_kuzminsky> makes sense
[19:01:44] <seb_kuzminsky> bbl
[19:02:17] <jmk-mcfaul_> I'm thinking the buildslave could test beaglebone specific drivers, etc
[19:09:19] <linuxcnc-build> build #4478 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4478 blamelist: John Morris <john@zultron.com>
[19:11:14] <jepler> Running test: /home/buildslave/emc2-buildbot/wheezy-amd64/rip-wheezy-amd64/build/tests/abs.0
[19:11:17] <jepler> HAL: ERROR: version code mismatch
[19:11:20] <jepler> HAL: ERROR: could not init shared memory
[19:11:22] <jepler> halcmd: hal_init() failed: -22
[19:11:25] <jepler> now wth
[19:11:27] <jepler> but besides that more of this
[19:11:28] <jepler> Application initialization failed: no display name and no $DISPLAY environment variable
[19:13:24] <jmk-mcfaul_> that HAL version code hasn't changed in eons has it?
[19:32:47] <linuxcnc-build> build #2623 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/2623 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[19:35:13] <linuxcnc-build> build #1091 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/1091 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[19:46:37] <linuxcnc-build> build #4479 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4479 blamelist: Chris Radek <chris@timeguy.com>, Sebastian Kuzminsky <seb@highlab.com>
[20:55:28] <seb_kuzminsky> linuxcnc-build: force build --branch=master 0000.checkin
[20:55:29] <linuxcnc-build> build #4480 forced
[20:55:29] <linuxcnc-build> I'll give a shout when the build finishes
[21:20:06] <linuxcnc-build> build #4463 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/4463
[21:27:01] <linuxcnc-build> build #2624 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/2624
[21:32:17] <jepler> http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/2624/steps/runtests/logs/stdio is yet a different new misbehavior, it seem to show the slow thread interrupting the fast thread...
[21:32:38] <jepler> > Note: Using LXRT realtime
[21:32:46] <jepler> this is .. what !?
[21:33:17] <jepler> uname:
[21:33:18] <jepler> Linux wheezy-i386 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686 GNU/Linux
[21:33:44] <jepler> oh weird, I am surprised rip-wheezy-i386 is not running a vanilla kernel, so it is a new bug in lxrt realtime
[21:34:48] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened issue #154: uspace+lxrt: evidence that rate monotonic scheduling is not enforced 02
https://github.com/LinuxCNC/linuxcnc/issues/154
[21:35:59] <linuxcnc-build> build #1092 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/1092
[21:36:19] <jepler> halrun: line 157: 23462 Segmentation fault (core dumped) halcmd_twopass "$filename"
[21:36:44] <jepler> I wonder what this is and how it can depend on the rtos
[21:36:45] <linuxcnc-build> build #1092 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/1092
[21:36:46] <linuxcnc-build> build #4480 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4480
[21:37:05] <jepler> Note: Using LXRT realtime
[21:37:06] <jepler> command timed out: 1200 seconds without output running /bin/bash -c 'if [ -f scripts/rip-environment ]; then source scripts/rip-environment; else source scripts/emc-environment; fi; runtests -v', attempting to kill
[21:37:11] <jepler> and here it just cheesed the vm
[21:37:16] <jepler> sigh
[21:38:06] <seb_kuzminsky> jepler: that is weird, isn't it
[21:39:03] <seb_kuzminsky> looking at dpkg.log, i think it "upgraded" from linux-image-3.2 to linux-image-3.4-rtai when i added 'base' to the apt sources last night
[21:39:14] <jepler> ah, that could explain it
[21:39:21] <seb_kuzminsky> wonder how many of our problems the past day are explained by this
[21:39:28] <jepler> I think I found this kernel didn't work on my amd64 machine: 3.16.7-6linuxcnc
[21:39:50] <jepler> I did my devel and testing with initrd.img-3.18.0-1-rtai-amd64
[21:39:53] <jepler> afk for the night
[21:42:46] <seb_kuzminsky> linuxcnc-build: force build --branch=master 1400.rip-wheezy-i386
[21:42:47] <linuxcnc-build> build #2625 forced
[21:42:47] <linuxcnc-build> I'll give a shout when the build finishes
[22:02:52] <linuxcnc-build> Hey! build 1400.rip-wheezy-i386 #2625 is complete: Warnings [8warnings compile]
[22:02:52] <linuxcnc-build> Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/2625
[22:03:56] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #150: Looks like this passed the buildbot, except two builders that say `HAL: ERROR: version code mismatch`. 02
https://github.com/LinuxCNC/linuxcnc/pull/150#issuecomment-241173929
[22:14:43] <seb_kuzminsky> ok that worked
[22:15:09] <seb_kuzminsky> so maybe it's at least partially due to rtai kernels on the vanilla/rt-preempt buildslaves, plus uspace+rtai?
[22:15:15] <seb_kuzminsky> bbl
[23:07:39] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #151: By the way, this patch depends on the fix in #150. 02
https://github.com/LinuxCNC/linuxcnc/pull/151#issuecomment-241176503
[23:26:10] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #151: Wow, thing really *are* moving around under me.... This time it's 85210a33. Trying once more to get a passing build.... 02
https://github.com/LinuxCNC/linuxcnc/pull/151#issuecomment-241177171
[23:45:23] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #151: Yay! A pass on Travis. 02
https://github.com/LinuxCNC/linuxcnc/pull/151#issuecomment-241177812
