Back
[08:58:22] <jepler> huh, I must have learned this but forgotten it: arm has "char" as unsigned
[08:59:32] <archivist> I get uppity when char is not unsigned!
[09:06:07] <KGB-linuxcnc> 03Jeff Epler 052.7 0090a9e 06linuxcnc 10src/hal/user_comps/xhc-hb04.cc xhc-hb04: fix negative jogs on non-x86 arches * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0090a9e
[11:58:48] <archivist> how often is the var file supposed to be written
[12:01:20] <archivist> not mentioned here
http://linuxcnc.org/docs/html/gcode/overview.html#_parameters
[12:01:50] <archivist> I ask because I can see it being written often on this logging application
[12:03:17] <archivist> the text implies on shutdown but watching the filing system says otherwise
[12:08:49] <kwallace> I think I recall it being said that the var file was intended to save parameters when LinuxCNC was shutdown. It does get updated often but only should only be considered valid after LinuxCNC shuts down. Maybe?
[12:10:29] <micges> I've noted that also on interp sync (mdi->auto, program stop, mode change, G10 Pn)
[12:11:01] <archivist> when the logging file is opened is also strange depending on what you are logging
[12:18:00] <jepler> archivist: I would like to eventually stamp out any guarantee stronger than "guaranteed to be read at startup, guaranteed to be written at shutdown".
[12:18:27] <jepler> so even if it does something else now, I prefer not to document exactly what it does
[12:18:36] <jepler> it may be written at any time the interpreter cares to write it
[12:18:59] <archivist> once every couple of second?
[12:20:37] <jepler> I think the current code will write when task receives certain requests like mode switches; this in turn is used by some preview-generating UIs today to try to have correct offset information from the var file when they generate a preview
[12:23:26] <archivist> I bet it is related to the funny in the logging
http://sourceforge.net/p/emc/bugs/452/
[12:24:05] <archivist> logging works if you use one of the vars but only then
[12:25:55] <jepler> It is possible they're connected, I haven't looked into that report
[14:19:47] <KGB-linuxcnc> 03Jeff Epler 05master 18517a3 06linuxcnc 10src/emc/rs274ngc/interp_internal.hh task: include <cmath> for std::nearbyint * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=18517a3
[14:48:34] <linuxcnc-build> build #2020 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/2020 blamelist: Jeff Epler <jepler@unpythonic.net>
[14:51:23] <linuxcnc-build> build #3841 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3841 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:19:45] <jepler> > *** warning: bad links found in French docs!
[20:19:54] <jepler> doesn't seem like I could be the one who made that failure
[20:20:37] <jepler> Code: 404 File `/home/buildslave/emc2-buildbot/wheezy-armhf/wheezy-armhf-sim/build/docs/html/lathe/images/tool_positions_fr.png' does not exist
[20:21:44] <jepler> it does exist in docs/src, I wonder what's up
[20:21:59] <jepler> a race condition in the build?
[20:22:11] <jepler> linuxcnc-build: force build --branch=2.7 0000.checkin
[20:22:12] <linuxcnc-build> build forced [ETA 1h57m14s]
[20:22:12] <linuxcnc-build> I'll give a shout when the build finishes
[20:22:37] <jepler> oh I guess that was a master branch build that faile
[20:22:38] <jepler> d
[20:55:30] <seb_kuzminsky> jepler: there was a segfault, up above that
[20:55:49] <seb_kuzminsky> might be time for a therapeutic reboot of my u3 again
[21:19:30] <jepler> seb_kuzminsky: hm I didn't see that, thanks
[21:26:56] <linuxcnc-build> Hey! build 0000.checkin #3842 is complete: Success [3build successful]
[21:26:56] <linuxcnc-build> Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3842
[22:40:03] <skunksleep> http://www.machsupport.com/forum/index.php/topic,31615.0.html