[01:10] <sergiusens> balloons, hey, do you know how to edit in d.c.c, I'm supposed to have edit rights, but I am failing to find the edit button
[07:32] <dholbach> good morning
[08:14] <fgimenez> good morning
[08:16] <mvo> hey fgimenez and dholbach, good morning :)
[08:17] <dholbach> hey mvo
[08:19] <fgimenez> hey mvo and dholbach :)
[08:20] <dholbach> hola fgimenez
[08:22] <fgimenez> hola dholbach! :) guten Morgen
[08:22] <dholbach> :-)
[10:04] <JamesTait> Good morning all; happy Wednesday, and happy Education Support Professionals Day! 😃
[11:10] <fgimenez> mvo, these errors have begun to show up in the suite execution this morning http://162.213.34.171:8080/job/github-snappy-integration-tests-cloud/53/
[11:11] <fgimenez> mvo, here's the console output http://162.213.34.171:8080/job/github-snappy-integration-tests-cloud/53/consoleFull, search for "FAIL:"
[11:11] <mvo> fgimenez: yeah, I noticed them too
[11:12] <fgimenez> mvo hello-world failed to install: unpack /tmp/hello-world730293314 to /apps/hello-world.canonical/1.0.18 failed with exit status 1
[11:12] <fgimenez> i'll try to reproduce locally in kvm
[11:14] <mvo> fgimenez: thanks
[11:14] <mvo> fgimenez: my kvm did not have network this morning
[11:26] <fgimenez> mvo, same here, 249 is throwing me into emergency mode
[11:31] <mvo> fgimenez: uh, emegerncy mode? fresh install or upgrade?
[11:33] <fgimenez> mvo, i've just generated it with udf
[11:33] <mvo> fgimenez: for me 241->249 works, but I have not tried a fresh one, let me do this now
[12:07] <sergiusens> mvo, ogra_ dpm I took a stance of updating the porting guide, the only thing a bit wonky is all the uEnv.txt comments which were replaced https://gist.github.com/sergiusens/fa40a344ad4b395a99ed
[12:07] <sergiusens> anyone care to look a bit
[12:07] <sergiusens> dpm, I didn't update the guide directly as I couldn't find the `edit` button
[12:20] <dpm> dholbach ^
[12:22] <dpm> sergiusens, we're working in getting the documents directly imported from markdown. But for now, you can also edit the page on the developer site directly: https://developer.ubuntu.com/openid/login/
[12:41] <sergiusens> dpm, ah, so clicking on login last night did nothing, I only had the option to go to myapps in the combo
[12:41] <sergiusens> :)
[12:42] <sergiusens> dpm, feel free to use my markdown as a base ;-)
[12:48] <mvo> fgimenez: fwiw, it seems like there is one bug in the systemd.enable code that I fixed, there is also a issue with systemd-tmpfiles-setup.service that shows as failing
[12:57] <fgimenez> mvo, ok thanks
[13:18] <dpm> sergiusens, hm, what does "did nothing" mean? I see you're a member of https://launchpad.net/~ubuntudeveloperportal-editors, so assuming you had the box ticked in the SSO login, that should get you into the site with edit rights (i.e. you should see the edit toolbar at the top of the browser)
[13:19] <sergiusens> dpm, I had no way to login, the direct link you gave me, logged me in ;-)
[13:20] <dpm> sergiusens, did you have the ubuntudeveloperportal-editors checkbox ticked? SSO always asks for team permissions
[13:21] <sergiusens> dpm, the scopes don't always show up
[13:22] <sergiusens> to be clear, on the top bar I had a 'Log in' button that did nothing, only showd a combo box that took you to 'My Apps'
[13:22] <dpm> sergiusens, not sure we're talking about the same thing. Which scopes?
[13:22] <sergiusens> after I clicked on the link you gave me, (and I suspect the magical openid/login/ at the end helped), I had that 'Log in' turned into 'Sergio'
[13:23] <sergiusens> dpm, by scopes I mean oauth scopes (the checkbox you asked if I had clicked)
[13:23] <sergiusens> and no, I didn't have to click on anything
[13:24] <sergiusens> dpm, to be even more clear and obvious, go into private mode in your browser, then go here http://developer.ubuntu.com/en and try to login ;-)
[13:27] <dpm> sergiusens, my point is that this is the url that should be used for login https://developer.ubuntu.com/openid/login/ , the combo box has no other function that tell you you're logged in (and to log out). I think what might have happened is that you logged in the first time without checking the boxes. So you might need to log out and log in again
[13:28] <dpm> I've just tried it on a private browser to make sure the site is not broken, seems to work
[13:37] <sergiusens> dpm, right, with your magical link I can log in just fine, the problem is, I had no idea that was the only way to login
[13:37] <sergiusens> dpm, I was saying, try to login without going straight to https://developer.ubuntu.com/openid/login/ and try to reach that from the main site ;-)
[13:52] <dpm> sergiusens, did you get a copy of the editor guide? Let me just send it to you
[13:52] <dholbach> sergiusens, taking a look
[14:15] <dholbach> davidcalle, I just tried to help sergiusens and update https://developer.ubuntu.com/en/snappy/guides/porting/ but I got all confused with the eight-col / twelve-col bits
[14:15] <dholbach> can you help me?
[14:15] <dholbach> and can we maybe make this easier somehow?
[14:15] <dholbach> I feel really bad about asking you every time :)
[14:16] <sergiusens> dholbach, davidcalle wait, I need some reviews for that from ogra_ or mvo ;-)
[14:17] <dholbach> ok...
[14:21] <davidcalle> sergiusens, eight-col is text, twelve-col is code, that's the Ubuntu web guidelines, can't do much about it. Also, if you have any suggestions on how to ease the editing process, I'm all ears :)
[14:23] <sergiusens> davidcalle, heh, that was for dholbach I guess.
[14:23] <davidcalle> sergiusens, hah :)
[14:24] <davidcalle> sergiusens, still, I'm open to suggestions :p
[14:24] <sergiusens> davidcalle, my only suggestion is autogenerated d.u.c ;-)
[14:25] <sergiusens> davidcalle, I would like it to use pandoc which supports the github """extensions"""
[14:26] <davidcalle> sergiusens, well, all docs can't be autogenerated, but we could see how to add a markdown editor, that would help for some large docs.
[14:27] <sergiusens> davidcalle, certainly; that is also a great idea
[14:28] <dholbach> davidcalle, once we have the new djangocms landed we can check into adding new modules :)
[14:29] <davidcalle> dholbach :)
[14:45] <mvo> fgimenez: I think I found and fixed the issue, lets see if the next image is better
[14:49] <fgimenez> mvo, great! we haven't yet in place the automated process for creating the images used by jenkins, ping me when ready to upload it
[14:54] <plars> fgimenez: mvo: I'm seeing that issue too with 249, is there a new one building now?
[14:54] <plars> or will it be tomorrow?
[14:56] <mvo> plars: now, should be ready in ~30min
[14:56] <plars> mvo: woo! thanks :)
[14:57] <mvo> plars: well, bbb will be a bit slower and I only tested by live-patching the initrd so it may take another iteration (but I hope not)
[14:59] <plars> mvo: understand, thanks
[15:27] <plars> mvo: looks like it worked :)
[15:38] <mvo> plars: yay, I'm still downloading :/
[15:41] <jdstrand> mvo: hi!
[15:42] <jdstrand> mvo: so, I did snappy update yesterday and rolling edge amd64 r248 didn't have policygen
[15:42] <jdstrand> mvo: so then I upgraded this morning to r249 and it went into emergency mode. looks like plymouht failed?
[15:42] <jdstrand> mvo: is this known?
[15:42] <mvo> jdstrand: r250 from ~5min ago fixes it
[15:43] <mvo> jdstrand: yes, know, plymouth is a red-herring, it was me breaking the initramfs in an unfortunate way
[15:43] <jdstrand> ah
[15:43] <mvo> jdstrand: if you run the update again it should be good
[15:44] <jdstrand> well, I couldn't seem to get a shell that would allow me to do that
[15:44] <jdstrand> that's ok though-- I use kvm snapshots
[15:45]  * jdstrand is getting 250 now
[15:47] <jdstrand> mvo: hmm, so, r250 doesn't seem to have policygen either
[15:47] <jdstrand> mvo: is that known?
[15:48] <jdstrand> mvo: basically, yesterday I was in the process of writing the email to the list about it and then I wanted to wait until it was on the image
[15:51] <mvo> jdstrand: uh, that sucks, looks like unfortunate timing between daily build and git importer :/
[15:51] <mvo> jdstrand: give me a sec to check
[15:53] <mvip> hey ricmm_. Thanks for coming out to the BBVA event on Monday.
[15:58] <jdstrand> mvo: ok-- I don't want you to go out of your way for this. I just wanted to make sure things were working as planned
[15:58] <mvo> jdstrand: could you approve my https://myapps.developer.ubuntu.com/dev/click-apps/3966/ ? its the first squashfs based snap for the store
[15:59] <mvo> jdstrand: I'm very thankful that you brought it up
[15:59] <mvo> jdstrand: I triggered a build of snappy and will soon make a new image with it
[16:00] <jdstrand> mvo: can you request a manul review? if I do, then I can't approve it I don't think
[16:00] <mvo> jdstrand: its a bit unfortunate that the turnaround time is close to 24h in the worst case, I merged last afternoon thats something the snappy team needs to discuss/improve :)
[16:00] <mvo> jdstrand: I think I did that now
[16:05] <jdstrand> mvo: that is good timing-- I have a branch that I've been working on to handle squashfs snaps
[16:05] <jdstrand> (for the review tools)
[16:05] <mvo> jdstrand: nice
[16:05] <jdstrand> mvo: so, if you are uploading to the store, that means that snappy has enough implemented to install it?
[16:05] <jdstrand> mvo: I guess when this new image comes out?
[16:06] <mvo> jdstrand: yes, it has enough implementation for this now and it will be useful as a regression test
[16:06] <mvo> jdstrand: its rolling only so should not affect anyone who is not up for the ride
[16:06] <jdstrand> mvo: well, this needs the policygen branch, no?
[16:07] <mvo> jdstrand: the current code will just unpack it, the next image (once I get review) will properly mount it for that the policygen is required
[16:08] <jdstrand> I see
[16:08] <mvo> jdstrand: are you concerned that it might break? I could use something different or a different name
[16:08] <jdstrand> I'll accept and now I have a snap to work with
[16:08] <mvo> jdstrand: great, thanks
[16:22] <elopio> fgimenez: ogra_: I gave up with this when xz was killed because it was consuming too much RAM.
[16:22] <elopio> https://github.com/ubuntu-core/snappy/pull/122
[16:24] <mvo> fgimenez, elopio: could you update the base image to r250 for the integration tests?
[16:24] <mvo> please :)
[16:26] <fgimenez> mvo, elopio i was trying the new jenkins job for automating this and i think it's already done, let me check
[16:27] <mvo> fgimenez: \o/
[16:33] <fgimenez> elopio, ok np, when automated the initramfs resize test could be filtered/annotated like the gadget snap ones, so that we can keep all them together and reuse the helpers
[16:38] <fgimenez> elopio, i've pinned some of the build reports in the jenkins executions for you to have a look, most of the errors will be probably because of the canonistack instances http://162.213.34.171:8080/job/github-snappy-integration-tests-cloud/
[16:48] <elopio> fgimenez: /me looks.
[16:51] <elopio> fgimenez: this looks wrong: Error: unable to create /boot/grub/grub.cfg/grub.cfg: open /boot/grub/grub.cfg/grub.cfg: not a directory
[16:51] <elopio> but I was debugging it yesterday and the test started passing.
[16:51] <elopio> now without the init going crazy I hope it will be easier to debug.
[16:51] <fgimenez> elopio, i'm looking into it right now too :) it's present in the latest 3 executions
[16:56] <fgimenez> elopio, i've tried the fake update manually and it works fine, not sure where does this come from
[16:57] <elopio> fgimenez: my last try last night seemed to be caused by initramfs test being killed and leaving a weird state. I don't see that in this log.
[16:57] <elopio> but let me run dozens today again, and I'll tell you what's going on.
[17:02] <fgimenez> elopio, yes, initramfs hasn't been executed yet, this happens for the three failover test, and it seems that up to this point https://github.com/ubuntu-core/snappy/blob/master/integration-tests/tests/failover_test.go#L57 all goes fine
[17:03] <elopio> I ran only the three failover tests, and couldn't reproduce that. But only a couple of times. I'm not yet sure if it's caused by the full suite.
[17:04] <elopio> moar runs!
[17:04] <fgimenez> elopio, :) it may be related to the slow instances too
[17:05] <fgimenez> but didn't happen before yesterday afaik
[17:12] <fgimenez> leaving, have a nice day o/
[17:46] <mvo> jdstrand: I have more interessting stuff for you :) https://myapps.developer.ubuntu.com/dev/click-apps/3753/
[18:13] <mvo> jdstrand: and the os snap in https://myapps.developer.ubuntu.com/dev/click-apps/3752/
[18:13] <mvo> jdstrand: if those could get in that would be very nice indeed
[18:52] <jdstrand> mvo: re https://myapps.developer.ubuntu.com/dev/click-apps/3753, can you request a manual review?
[18:53] <jdstrand> mvo: same with https://myapps.developer.ubuntu.com/dev/click-apps/3752
[18:53] <jdstrand> man, you are going to keep me busy with the review tools
[18:56] <mvo> jdstrand: ups, I thought I did request that already, sorry. requested it now :)
[18:58] <jdstrand> mvo: done
[18:58] <mvo> jdstrand: \o/
[19:00] <jdstrand> mvo: I think once I teach the tools not to just die on non-click snaps (in progress), these tests will simply see if it is a kernel or os and then flag for manual review. nothing more. if someone wants to add more tests for the review tools for those once things have settled, that would be great
[19:01] <mvo> jdstrand: I think thats totally fine
[21:22] <mvo> jdstrand: hey, fwiw I found and fixed the issue that held the policygen stuff back its now ready but for some reason the import imports are disabled in cron. I asked sil2100 about it but no feedback yet. I will wait until my morning and if its not there by then I will manually import the image
[21:26] <jdstrand> mvip_: ack, thanks
[21:26] <jdstrand> mvip_: sorry
[21:27] <jdstrand> mvo left and you got tab completed :)