[08:14] <dbarth> hey trainguards
[08:14] <dbarth> or qa
[08:14] <sil2100> Hey! What's up?
[08:15] <dbarth> i'm trying to push https://requests.ci-train.ubuntu.com/#/ticket/1503#audit_log but the lander signoff flag got resetted
[08:15] <dbarth> i don't know why britney is so unhappy tbh
[08:16] <dbarth> hmm, or maybe :
[08:16] <dbarth> 2016-06-20 17:06:26 +0200 (abreu-alexandre) Preparing packages.
[08:16] <sil2100> dbarth: you want it to be APproved by Lander?
[08:16] <dbarth> i will re-approve then; just reloading the packages to be double sure
[08:16] <sil2100> Ok
[08:16] <dbarth> grr :)
[08:16] <sil2100> Yeah ;)
[08:16] <robru> dbarth: it was still in state "currently building" when you set it, that's not allowed
[08:17] <robru> dbarth: efrrr
[08:17] <sil2100> robru: sightseeing, now!
[08:17] <robru> dbarth: yeah sorry it's because Alex rebuilt, I misread
[08:18] <dbarth> right probably
[08:18] <dbarth> rgrrr
[08:18] <robru> sil2100: I'm sightseeing the laundromat Right now
[08:18] <sil2100> robru: they have one in the hotel?
[08:18] <robru> sil2100: no it's some blocks away
[08:19] <robru> sil2100: in an hour I'll go for lunch
[08:24] <robru> xavigarcia: only public branches are supported
[08:26] <xavigarcia> robru: hey, thanks for pointing out! I will ask the guys who maintain that project to make it public!
[08:26] <robru> xavigarcia: you're welcome
[08:39] <sil2100> robru: just not to the restaurant upstairs ;) Hope you don't eat there no more
[08:47] <robru> sil2100: haven't been upstairs even once since The Incident
[10:24] <sil2100> robru: hey!
[10:24] <sil2100> robru: you still somewhere around?
[10:25] <robru> sil2100: what's up?
[10:25] <sil2100> robru: I noticed that commitlogs stopped working since the usual API bits for published_versions doesn't seem to get updated (at least on first look?)
[10:25] <sil2100> https://requests.ci-train.ubuntu.com/v1/comments?published_versions=:&text=Merging
[10:25] <sil2100> I use this and the last published_version mention is from the 16th
[10:26] <robru> sil2100: hmmm that's odd.
[10:26] <sil2100> All landings later than that are not registered there
[10:26] <sil2100> hmm
[10:26] <robru> sil2100: I did touch the audit logging code but it should all still be hooked up with the published versions
[10:26] <sil2100> For instance grepping for the recent ubuntu-ui-toolkit release gives me nothing
[10:27] <sil2100> e.g. we had 1.3.2009+15.04.20160615.3 released around yesterday and it's not there
[10:28] <robru> sil2100: ok I'll check what changed on the 16th
[10:30] <sil2100> robru: thanks :)
[10:31] <robru> sil2100: ok I have some leads to follow up here. but first, are you sure you can't change your commitlog script to just inspect what package versions were built in the image? I've always felt trying to inspect the train for it's publications would be error-prone, like this.
[10:32] <sil2100> robru: I do that, but I need the binding package_version->landing from somewhere
[10:32] <sil2100> I get the list of package versions from the manifests and look for the corresponding landings to those versions
[10:32] <robru> hmmm
[10:33] <sil2100> How am I supposed to know which package version was coming from which landing otherwise?
[10:33] <robru> sil2100: why does it matter which landing it came from? can't you just inspect the changelog on the released package to know everything you need to know about it?
[10:33] <sil2100> robru: no, since we want to know the landing description as well
[10:33] <robru> hmmm
[10:34] <sil2100> robru: since I print out changelog entries as well, but we need to know which packages came from which landing, as a landing can be composed from many different packages
[10:34] <sil2100> Changelogs give us info about the certain package, but we want to know if that package was part of a bigger piece or not
[10:35] <robru> sil2100: yeah but I don't really understand why you need to track this relation, can't the commitlog just say "ok, this image has a new unity8, new mir, etc"
[10:35] <sil2100> So we need: landing description and group the package releases into landings
[10:36] <sil2100> Well, one of the reasons might be reverts: when we want to revert a package, we need to know what other packages from the landing might need reverting
[10:36] <sil2100> But in overall it also gives a good understanding of what feature-sets have landed
[10:36] <sil2100> As I said, a changelog gives you info about just one component
[10:36] <sil2100> While landings are made out of multiple components that make up for a landing
[10:37] <sil2100> And that landing might have more importance when all pieces are released - without this info we waste time by trying to connect packages together
[10:38] <sil2100> Looking at the changelogs and then trying to figure out: "was this landed as a separate thing? Did this go with any other changes? Where are the other bits? Are there any other bits?"
[10:41] <robru> sil2100: ok I pushed a fix, after about an hour, if there are any tickets currently in proposed, you should see their published_versions fields being populated.
[10:41] <robru> sil2100: eg just look at https://requests.ci-train.ubuntu.com/v1/comments?published_versions=: to see the values being filled before the merge happens
[10:41] <sil2100> \o/
[10:42] <robru> sil2100:  eg https://requests.ci-train.ubuntu.com/#/tickets?status=pocket this one ticket should be the guinea pig for now
[10:42] <robru> sil2100: not a retroactive fix, of course, anything already merged is lost
[10:46] <sil2100> robru: ok, no worries, I just won't re-generate silos in that case ;)
[10:46] <sil2100> I mean, commitlogs
[10:48] <sil2100> robru: anyway, thanks!
[10:51] <robru> sil2100: you're welcome
[11:27] <rvr> mardy: ping
[11:27] <rvr> mardy: I can't authenticate in Instagram, is it known?
[11:29] <rvr> mardy: I see a json response, {"code": 403, "error_type": "OAuthForbiddenException", "error_message": "You are not a sandbox user of this client"}
[11:33] <rvr> pstolowski: ping
[12:00]  * sil2100 goes for a longer lunch
[12:06] <mardy> rvr: interesting...
[12:09] <mardy> rvr: please file a bug on the instagram scope: https://www.instagram.com/developer/sandbox/
[12:18] <pstolowski> rvr, pong
[12:18] <rvr> pstolowski: Hi
[12:19] <pstolowski> hey
[12:19] <rvr> pstolowski: I found a problem with silo 1 and Flickr
[12:19] <rvr> pstolowski: After posting a comment, the page was refreshed, but I couldn't post any other comments
[12:20] <rvr> pstolowski: Scope said "Please login to post a comment". I checked and was still authorized in Accounts.
[12:20] <rvr> pstolowski: See the screenshot in the trello card
[12:25] <pstolowski> rvr, hmm, i don't think changes in this silo could cause this, did you have time to check it without the silo?
[12:38] <pstolowski> rvr, i'm reflashing to check this
[12:39] <rvr> pstolowski: Sorry. Nope, I didn't check without the silo packages.
[13:05] <pstolowski> rvr, ok, i check with and without the silo
[13:06] <pstolowski> rvr, i cannot reproduce the problem. in both cases after hitting 'Post' i'm still able to enter a comment. however, the scope seems to be broken. in both scenarios i don't see my comments. scope-registry.log has this:2016/06/21 15:03:37 post a comment:  fail
[13:07] <rvr> pstolowski: I see
[13:07] <pstolowski> rvr, re your particular problem, i suspect a problem with online accounts; i've seen similar issues in the past, removing and re-adding the account may help
[13:08] <rvr> pstolowski: In stable it still shows the text field to enter a new comment
[13:08] <pstolowski> rvr, also, without the silo the preview gets reversed; the silo fixes it
[13:08] <rvr> pstolowski: But I see that the content sort problem is gone
[13:09] <pstolowski> rvr, do you ever see your comments really submmited after posting?
[13:09] <rvr> pstolowski: Nope
[13:10] <rvr> pstolowski: They aren't posted, I don't see them checking in the website
[13:11] <pstolowski> rvr, can you grep /home/phablet/.cache/upstart/scope-registry.log for 'post a comment' ?
[13:41] <robru> sil2100: fix confirmed: https://requests.ci-train.ubuntu.com/v1/comments?published_versions=:
[14:31] <renato___> robru, messaging app is faling to build on  arm64 for yakkety and xenial, with some strang open gl bug
[14:32] <robru> renato___: please refer to channel topic
[14:32] <renato___> robru, is this a blocker? I think this is not new, since this is not related with my changes
[14:34] <renato___> robru, sorry  I thought that you are back , enjoy your vocations
[14:34] <robru> Thanks!
[14:37] <kenvandine> robru, lol.... you need to learn how to vacation :)
[14:37] <kenvandine> no irc allowed!
[14:39] <sil2100> I told him that!
[14:39] <sil2100> But at least in case of serious forest fires we can reach out to him
[14:59] <dbarth> jibel: hey, i have silo 19 which seems not to want to go onto the QA board
[15:00] <dbarth> ie https://requests.ci-train.ubuntu.com/#/ticket/1545
[15:00] <dbarth> can you add it?
[15:00] <jibel> dbarth, yes, I'll have a look
[15:00] <dbarth> thanks
[16:32] <renato___> trainguards,  silo 46 is not pushing the packages to the ppa? Could you guys help me with that?
[16:58] <sil2100> renato___: let me take a quick look
[16:59] <sil2100> renato___: I see packages recently built, what's wrong with those?
[16:59] <sil2100> renato___: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-046/+packages
[17:00] <renato___> sil2100, I ask to update the the diff, and started to work.
[17:00] <renato___> thansk
[20:40] <kenvandine> sil2100, what does this mean?
[20:40] <kenvandine> Diff missing (qtbase-opensource-src-gles/vivid, qtbase-opensource-src/vivid, qtdeclarative-opensource-src-gles/vivid, qtdeclarative-opensource-src/vivid).