#linuxcnc-devel Logs

Jan 17 2018

07:21 AM jepler: seb_kuzminsky: https://emergent.unpythonic.net/files/sandbox/memory-usage-flo.png
07:23 AM jepler: seb_kuzminsky: and yes, previously we tuned down some process limits in apache due to memory use
08:25 AM jepler: btw I tried fluxcapacitor but it doesn't succeed in speeding up the runtests.
08:26 AM jepler: I bet it's great for things which use a few, large sleeps; but not things that use a whole lot of small sleeps like linuxcnc
09:30 AM pcw_home: Yow, lots of spam on wiki
09:31 AM pcw_home: forum I mean
09:33 AM mozmck: pcw_home: the spam seems to come in spurts. I'll get rid of it right quick. I usually disable the poster as well when I do it.
09:34 AM pcw_home: Yeah looks like all same user
09:40 AM mozmck: Couple of users actually. jepler, is there a way to see all posts of a user? I can't find it if there is.
09:42 AM mozmck: heh, well both users have the same IP address, so maybe same user after all.
10:04 AM seb_kuzminsky: does anyone know of any reason to hold back 2.7.12?
10:41 AM skunkworks__: can you just say - don't use pncconf?
11:04 AM jepler: skunkworks__: are you saying there's a regression in pncconf from 2.7.11 to the current tip of 2.7? Or is your question in response to something else?
11:10 AM jepler: mozmck: https://forum.linuxcnc.org/forum/search?searchuser=USERNAME&childforums=1
11:10 AM jepler: mozmck: which is part of the "search" page
11:11 AM mozmck: ah, thanks! I guess I should have thought to look there. I'm more used to other forums which have a link in the user's page or something.
11:12 AM jepler: mozmck: you can also search in the administrator back end for the user https://forum.linuxcnc.org/administrator/index.php?option=com_kunena&view=users
11:12 AM jepler: you can click the checkbox to the left of the username, then "trash messages". you can also ban them from there.
11:13 AM mozmck: Yes, that's how I find them to ban them, but I didn't see the "trash messages"
11:13 AM jepler: https://www.kunena.org/forum/general-questions-and-how-tos/141936-how-to-delete-all-posts-from-a-certain-user
11:14 AM mozmck: Ah, it's at the top. That will be helpful - thanks!
11:15 AM mozmck: I don't know if kuena has something like this, but on another forum I maintain there is an "Activation Justification" plugin which requires the user to type in something explaining why they want on the forum.
11:16 AM mozmck: Kunena that is...
11:17 AM mozmck: I get an email for every user joining the forum though and that might be a pain on this one. It has eliminated spammers though on this other forum.
11:18 AM jepler: is this information manually reviewed before the account is enabled, or what?
11:21 AM mozmck: Yes
11:24 AM jepler: we could set up something similar on the forum. However, in the distant past I had a requirement that the user's first *message* be approved by a moderator, and we changed away from that for some reason. I think the feeling was it was better to let people post right away and deal with some spam. I think andypugh might have had an opinon about all of this.
11:25 AM mozmck: Yeah, I remember that, and I think users didn't like it.
11:25 AM mozmck: And maybe too much work for moderators.
11:25 AM jepler: new users ignored the notices and posted their message 99,999 times
11:26 AM mozmck: Yeah
11:27 AM mozmck: There aren't that many spammers getting on overall I think.
11:34 AM pcw_home: this is the first big batch I have seen in a while
11:35 AM jepler: thanks for cleaning it up
11:37 AM pcw_home: Yes, Thanks mozmck
11:37 AM mozmck: no problem
12:12 PM skunkworks__: jepler, I am not sure - https://forum.linuxcnc.org/38-general-linuxcnc-questions/33866-future-of-linuxcnc?start=10
12:12 PM skunkworks__: I have never used it so I don't even know how it works.
12:27 PM pcw_home: Ill try pncconf (and mesaflash) on the stretch ISO some time today
02:48 PM pcw_mesa: skunkworks__ on the THC, I wonder if position error based PID gain scheduling ( low gain if error is less than a volt equiv or so ) would help reduce random small dithering (an least more cleanly than a deadzone)
02:53 PM pcw_mesa: Was it somethind I said?
02:59 PM mozmck: his head exploded
05:18 PM linuxcnc-build: build #2806 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/2806 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:19 PM linuxcnc-build: build #3067 of 4009.deb-precise-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4009.deb-precise-rtai-i386/builds/3067 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:24 PM linuxcnc-build: build #2809 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/2809 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:32 PM linuxcnc-build: build #4237 of 4008.deb-precise-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4008.deb-precise-amd64/builds/4237 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:32 PM linuxcnc-build: build #3410 of 4003.deb-lucid-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/3410 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:35 PM linuxcnc-build: build #4237 of 4007.deb-precise-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4007.deb-precise-i386/builds/4237 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:50 PM linuxcnc-build: build #3408 of 4004.deb-lucid-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/3408 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:01 PM linuxcnc-build: build #1205 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/1205 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:14 PM linuxcnc-build: build #3405 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/3405 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:23 PM linuxcnc-build: build #2100 of 4015.deb-wheezy-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4015.deb-wheezy-rtpreempt-amd64/builds/2100 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:31 PM linuxcnc-build: build #2066 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/2066 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:31 PM jepler: seb_kuzminsky: so after about a day, the memory usage has stabilized at 30-35% instead of 50%. I wonder whether it makes more sense to increase the http connection counts, or something in mysql caching
06:33 PM jepler: we are using the old type of sql database, MyISAM, which says it relies primarily on OS caching for performance. In that case, the fact that we have over 1GB of disk cache should be getting us lots of benefit.
06:33 PM jepler: I assume this is just due to how we imported from a very old mysql where that was the default, we're on 5.7 where the default is now InnoDB
06:47 PM linuxcnc-build: build #2497 of 4018.deb-wheezy-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4018.deb-wheezy-rtai-i386/builds/2497 blamelist: Sebastian Kuzminsky <seb@highlab.com>
07:34 PM jepler: desktop-file-validate debian/extras/usr/share/applications/linuxcnc-integratormanual-fr.desktop debian/extras/usr/share/applications/linuxcnc.desktop debian/extras/usr/share/applications/linuxcnc-halmanual-fr.desktop debian/extras/usr/share/applications/linuxcnc-gcoderef.desktop debian/extras/usr/share/applications/linuxcnc-gettingstarted.desktop
07:34 PM jepler: debian/extras/usr/share/applications/linuxcnc-gettingstarted-fr.desktop debian/extras/usr/share/applications/linuxcnc-gcoderef-fr.desktop debian/extras/usr/share/applications/linuxcnc-documentation.desktop debian/extras/usr/share/applications/linuxcnc-latency.desktop debian/extras/usr/share/applications/linuxcnc-pncconf.desktop debian/extras/usr/share/applications/linuxcnc-stepconf.desktop
07:34 PM jepler: debian/extras/usr/share/applications/linuxcnc-usermanual-fr.desktop
07:34 PM jepler: See "desktop-file-validate --help" for correct usage.
07:34 PM jepler: make: *** [install] Error 1
07:35 PM jepler: on wheezy, despite the manpage synopsis of
07:35 PM jepler: SYNOPSIS
07:35 PM jepler: desktop-file-validate [--no-warn-deprecated] [--warn-kde] FILE...
07:36 PM jepler: only one filename is actually accepted
07:36 PM jepler: herp derp commandline is not stable api
07:36 PM jepler: $ desktop-file-validate debian/extras/usr/share/applications/linuxcnc.desktop
07:36 PM jepler: debian/extras/usr/share/applications/linuxcnc.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated...
07:37 PM jepler: $ desktop-file-validate debian/extras/usr/share/applications/*.desktop
07:37 PM jepler: See "desktop-file-validate --help" for correct usage.
07:37 PM jepler: seb_kuzminsky: ^ my findings about those build errors
07:39 PM jepler: a short report on "macchiatobin" (arm64 sbc) http://blog.alteholz.eu/2018/01/first-steps-with-arm64/
07:41 PM jepler: https://www.solid-run.com/marvell-armada-family/macchiatobin/ marvell 8040 CPU, 1 DDR4 RAM slot, sata, PCIEx4 slot, etc
07:41 PM jepler: I think this is one that had been mentioned around here before
10:34 PM seb_kuzminsky: did i say packaging-fixes? i meant packaging-breakage
10:35 PM seb_kuzminsky: i only tested it on jessie