These are chat archives for machinekit/machinekit

29th
Nov 2015
Bob van der Linden
@bobvanderlinden
Nov 29 2015 11:14 UTC
we could also send build notifications here on gitter... not sure whether that's something we'd want, but could be useful
Michael Haberler
@mhaberler
Nov 29 2015 11:15 UTC
that'be great - archived, searchable, no mailbox searching needed
did you find some travis integration for that?
(besides having the upside of getting developers onto this room)
Bob van der Linden
@bobvanderlinden
Nov 29 2015 11:16 UTC
check the screwdriver in your top-right and hit integrations
i'll make a pr
Michael Haberler
@mhaberler
Nov 29 2015 11:18 UTC
that says there is a webhook for travis, but unsure what to do with it
Bob van der Linden
@bobvanderlinden
Nov 29 2015 11:18 UTC
one sec, i'll add it and do a pr
Michael Haberler
@mhaberler
Nov 29 2015 11:18 UTC
did you do all this before?
Bob van der Linden
@bobvanderlinden
Nov 29 2015 11:20 UTC
it's very similar to the changes @kinsamanka did for email
Michael Haberler
@mhaberler
Nov 29 2015 11:20 UTC
ah
bbl in an hour or two, but if nobody around just merge yourself
Bob van der Linden
@bobvanderlinden
Nov 29 2015 12:49 UTC
Yay, build status is available on the right under Activity.
Bas de Bruijn
@luminize
Nov 29 2015 12:50 UTC
awesome!
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:01 UTC
@kinsamanka I don't understand the second docker run in #805 ? Could you explain why this is needed instead of using proot?
I see it first tars /opt/rootfs (the arch-specific environment) and then letting docker untar the file through docker build so that it can run the /opt/rootfs as if it were a root... but doesn't proot does exactly that with -R?
GP Orcullo
@kinsamanka
Nov 29 2015 13:12 UTC
@bobvanderlinden I replied on the github page
proot is basically a chroot for non-root users
and running services under a chroot environment is a bit tricky
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:13 UTC
hmm, is that related to process isolation of docker?
why would it not be possible to run inside a chroot instead of docker?
GP Orcullo
@kinsamanka
Nov 29 2015 13:14 UTC
also you need the real chroot on some services, like avahi, to run properly
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:15 UTC
but ok, then I understand that it's about avahi and rsyslog
is systemd being used nowadays btw?
I think systemd-nspawn would be a good alternative in that case
GP Orcullo
@kinsamanka
Nov 29 2015 13:15 UTC
and using chroot needs the --privileged flag when invoking docker run, this is not compatible with other CI providers
hmm, systemd :smirk:
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:16 UTC
yes, it would be preferable if privileged wasn't needed indeed
but i understand why docker is used that way now
GP Orcullo
@kinsamanka
Nov 29 2015 13:17 UTC
nosetests complains if syslog is not running
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:17 UTC
ugh
hopefully we can change that around as well at some later point
GP Orcullo
@kinsamanka
Nov 29 2015 13:18 UTC
avahi will be needed by @strahlex
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:18 UTC
yes, i see how that's needed
ah, systemd will come in 16.04... alright docker it is :)
Bas de Bruijn
@luminize
Nov 29 2015 13:51 UTC
@bobvanderlinden i see only your activity (bobvabderlinden/machinekit) in the side panel.
Bob van der Linden
@bobvanderlinden
Nov 29 2015 13:52 UTC
oops...
ohw...
oh no, i added the wrong webhook url of gitter :'( I'll make another PR
it's too bad it's hard to test this without it actually being on master branch of machinekit/machinekit
Bas de Bruijn
@luminize
Nov 29 2015 13:54 UTC
no harm done i’d say :) btw, when I’m in travis, I can see all of the other builds too. That’s very good to see all the activity
very nice!
Bob van der Linden
@bobvanderlinden
Nov 29 2015 14:04 UTC
ah, the problem isn't using the wrong url, but if anyone uses the machinekit fork they will also use .travis.yml if Travis builds their repo. Travis will execute the url for whichever fork there is. Kind of funny really. I've found a solution that keeps the gitter url private in Travis.
Bas de Bruijn
@luminize
Nov 29 2015 14:05 UTC
so you mean that anybody who builds in travis gets noted in the sidepanel here?
Bob van der Linden
@bobvanderlinden
Nov 29 2015 14:05 UTC
anybody who builds the current versions of machinekit in travis, yes
not anymore though, i've removed the url from gitter
created a new one
added that new one as a private variable to Travis
and now creating a PR that uses that private variable for the webhook for Travis to use
so that way the url is unknown to everyone except for the machinekit maintainers
GP Orcullo
@kinsamanka
Nov 29 2015 14:23 UTC
Maybe you can use that webhook as a trigger for the builders
Bob van der Linden
@bobvanderlinden
Nov 29 2015 14:27 UTC
yes, but the contents of the http request isn't customizable. I think using curl or something like that inside the test-script like they did in the url you sent is more viable
found out CircleCI also supports build artifacts
Bob van der Linden
@bobvanderlinden
Nov 29 2015 14:32 UTC
I tried drone.io, but I couldn't get it to configure properly through .drone.yml. The documentation and posts mostly talk about a self-hosted drone server, instead of drone.io. Not sure what was up with that. So, maybe trying CircleCI is a next step... I do like that drone can be self-hosted though.
GP Orcullo
@kinsamanka
Nov 29 2015 14:33 UTC
CircleCI allows only 1 concurrent job for free
Bob van der Linden
@bobvanderlinden
Nov 29 2015 14:34 UTC
ah k, nm then
GP Orcullo
@kinsamanka
Nov 29 2015 14:34 UTC
I don't know if they have build timeouts
Bob van der Linden
@bobvanderlinden
Nov 29 2015 14:37 UTC
couldn't find it in their documentation, but https://discuss.circleci.com/t/timeout-more-than-120-minutes/640 seems to suggest there is a timeout for each command (so that could still be interesting)
not sure if it's indeed 120m like they say in that post, as that might be for paying customers
Bas de Bruijn
@luminize
Nov 29 2015 18:39 UTC
I found this app “Mantis CI" inside the app store when I searched for “Travis CI”. When you search for “machinekit” inside the app, you see all the builds like here http://floydpink.github.io/Mantis-CI-www/#/search/machinekit
Bas de Bruijn
@luminize
Nov 29 2015 21:33 UTC
just dumping a thought on visibility: I installed scilab which has xcos, which is similar to simulink. You can wire up blocks, and you can output that to an xml file.
Screen Shot 2015-11-29 at 22.27.30.png
Alexander Rössler
@machinekoder
Nov 29 2015 22:42 UTC
would be most interesting to make this bi-directional, from HAL to XML should be pretty easy
hmm, why not writing a xml to hal convert in python
not a code generator, more a loader
Alexander Rössler
@machinekoder
Nov 29 2015 22:50 UTC
the biggest problem with these approaches is to me combining generated code with written code
a schematic like aproach where every "sheet " has in and outputs that can be connected would be a solution for that
e.g. a Python class that can load such a XML file and create HAL "sheet" connectable with an existing configuration
sheets could be namind entities
e.g. prefixing component and names
sheet1.and2-foo.in0
signal sheet1.foobar
some sheet IO component might be required to expose the "signals"
Alexander Rössler
@machinekoder
Nov 29 2015 22:55 UTC
with a variable number of named in, io and out pins
Michael Haberler
@mhaberler
Nov 29 2015 23:08 UTC
just pointing out this looks like an offline design idea - I would consider live interaction with a save/restore option more interesting - note that halshow is aging tcl/tk code
not sure we need a grand design tool, but a good GUI inspector with load/newinst/delinst/net/unlink capability sounds interesting