[13:50] <smoser> powersj, so obviously my general inability to keep up with things is the cause of the problem.
[13:50] <smoser> but https://code.launchpad.net/~syed1/cloud-init/+git/cloud-init/+merge/322024
[13:51] <smoser> links to a bunch of failures that dont exist
[13:51] <smoser> anything we could do about that ?
[13:51] <powersj> Looking
[13:52] <powersj> 1. Easiest is to trigger a rebuild or 2. I can up the amount of runs we keep even higher. That doesn't guarantee this won't happen again though.
[13:52] <smoser> even the rebuild button doesnt work :)
[13:52] <powersj> O.o
[13:53] <smoser> cause it points to the same build
[13:53] <smoser> which had the context of which branch was built and such
[13:54] <powersj> hmmm
[13:58] <powersj> increasing the number of jobs we keep may not even help without increasing it greatly. With 25 we only have 10 days worth
[13:58] <powersj> I did manually kick a job off though
[14:02] <smoser> its kind of pointless though really. i wonder we could reasonably post at least the failure portion of it to the log
[14:17] <powersj> yeah
[14:33] <smoser> blackboxsw, you were looking for a bitesize bug
[14:33] <smoser> i dont have a bug (you can open one)
[14:33] <smoser>  we use yaml
[14:33] <smoser> http://stackoverflow.com/questions/27743711/can-i-speedup-yaml
[14:33] <smoser> we dont use it extensively, and its even possible that loading the c code could have overhead for the small bits of yaml that we load...
[14:33] <smoser> but i've wanted to look at that
[14:33] <smoser> that make sense ?
[14:34] <blackboxsw> smoser, sure reading that now.
[14:36] <blackboxsw> yeah that makes sense
[14:36] <blackboxsw> ok will file a bug about it as I test out whether there is a good performance imact.
[14:36] <blackboxsw> *impact
[14:57] <smoser> bug 1
[17:48] <rharper> smoser: is there such a think as a daily-ppa but for fedora/centos cloud-init rpms ?
[17:49] <rharper> larsks: ^^
[17:49] <smoser> https://build.opensuse.org/ is the closest thing that i'm aware of
[17:51] <rharper> maybe a lxd centos/fedora container calling build-rpm ?
[17:52] <powersj> https://gist.github.com/smoser/19e65095b342e98fd4d6466e4d4fa1ac
[17:52] <powersj> I've been using that locally to prototype running unittests and build tests for centos
[17:52] <powersj> I think I made only a few slight changes
[17:53] <rharper> powersj: nice!
[17:55] <smoser> rharper, but honestly.. the suse build service migth be useful.
[17:55] <smoser> i think it is basically the equivalent of ppas
[17:55] <smoser> so we could have daily builds for rpm
[17:55] <smoser> that anyone could easily use
[17:55] <rharper> for fedora/centos  ?
[17:55] <rharper> I assumed it was suse specific
[17:55] <powersj> open build service does other distros
[17:57] <rharper> cool
[19:49] <smoser> rharper, all the touches to datasources/*.rst there...
[19:49] <smoser> those just make targets for links ?
[20:04] <rharper> smoser: I think so, I might need more context
[20:05] <rharper> smoser: ah those touches were for anchors
[20:05] <rharper> you're talking about the netconfig update
[20:05] <rharper> you have to put a header in those files to allow link refs to work
[20:06] <rharper> smoser: in particular, I wanted to document which network config was supported in which datasources
[20:06] <rharper> and in the network doc link to that datasource documentation page
[20:07] <rharper> since I was in the few that support network config; I wanted to touch all of them in case someone else wanted to use the refs later on
[20:10] <smoser> rharper, yeah, i paste failed.
[20:10] <smoser> meant to include link
[20:17] <rharper> no worries, does the above make sense?
[20:23] <smoser> yeah,  that sfine
[20:47]  * smoser is out
[20:47] <smoser> rharper, i commented on your mp
[20:47] <smoser> it does look really good  thank you.
[20:47] <rharper> ok
[20:48] <rharper> sure