/srv/irclogs.ubuntu.com/2014/07/15/#ubuntu-ci-eng.txt

alecuany trainguards around to ask about publishing landing-009?01:09
cjwatsonalecu: looking01:13
alecuthanks01:13
cjwatsonlooking at that too :)01:17
imgbot=== trainguard: IMAGE 131 building (started: 20140715 02:05) ===02:05
alecuYay03:07
imgbot=== trainguard: IMAGE 131 DONE (finished: 20140715 03:40) ===03:40
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/131.changes ===03:40
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #119 promoted | Need CI Train help? Ping: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
sil2100psivaa: I wonder what happened with the UITK tests in the latest image, we seem to have a lot of failures due to an qmlscene crash07:16
sil2100ogra_: eh, manta and flo are still terrible, we can't even get full test results there still ;/07:17
sil2100We need to get someone looking at that ASAP07:17
ogra_sil2100, hmm, and UITK has its hiccup again it seems07:44
sil2100ogra_: yeah, I poked psivaa about that already07:45
sil2100brendand: !08:11
sil2100brendand: so! Could you take a look at two things on the dashboard?08:11
sil2100brendand: first thing - we seem to have 2 failures each time for system-settings08:11
ogra_with the new version from 13008:11
sil2100brendand: and I would concentrate on this one, trying to see if the same tests fail and if they're reproducible08:12
ogra_it clearly started with the landing08:12
sil2100brendand: then we would need someone with a keen-AP eye to check if the UITK hiccup in the latest image was an 'accident' as before ;)08:12
ogra_oh, bot settings failures are related to the dropped phone page ...08:13
ogra_seems that will just need updating08:13
ogra_*both08:13
ogra_(of the tests)08:14
ogra_sil2100, brendand, seems the UITK failures also have a related unity8 crash08:14
ogra_(and qmlscene)08:14
psivaasil2100: ogra_: i'm rerunning uitk tests08:14
sil2100unity8? I saw qmlscene08:14
sil2100Ah, both08:14
ogra_sil2100, there are two08:15
ogra_:)08:15
ogra_i assume unity8 killed the qmlscene instance when crashing08:15
ogra_sil2100, unity8 itself had a crash during its own tests too08:16
brendandogra_, from what i can see the failures are in the About page08:19
ogra_brendand, but using info from the phoe page08:20
ogra_*phone08:20
ogra_hmm, no only one of them08:21
brendandogra_, did the mir issue fix land?08:23
ogra_yep08:23
ogra_supposedly at least08:23
sil2100Didn't seem to help flo or manta test-wise though08:24
sil2100ogra_: can you upgrade your flo/manta and tell us if it's better now?08:29
ogra_after the meeting, yeah08:29
sil2100popey: boing08:31
brendandogra_, which package do you think broke the imei test?08:39
ogra_brendand, system-settings changed the way it recieves info from ofono ... (that was what broke the wizard too) ...08:40
ogra_it moved from ofono-qt to libofono08:40
Laneywhat evidence do you have that this is the same?08:41
ogra_brendand, https://launchpad.net/ubuntu/utopic/+source/ubuntu-system-settings/0.3+14.10.20140711.1-0ubuntu108:42
ogra_Laney, well it tries to recieve the imei via dbus but gets an error back ... i think the AP test wasnt updated alongside the switch08:42
ogra_Laney, it is just a theory :)08:43
sil2100Holy crap my Firefox crashed when leaving the hangout, it had to be devastated by the meeting ending08:58
MirvI can't find an indication of a distro patch to Qt (5.2) regarding the event loop. it was discussed with upstream at https://bugreports.qt-project.org/browse/QTBUG-37677 and downstream marked as Invalid for Qt at bug #1292306 (fixed in Mir)08:59
ubot5bug 1292306 in mir (Ubuntu) "Qt render gets blocked on EGLSwapBuffers [fka Upon upgrading to Qt5.2 the music app no longer plays the next song if the screen is off]" [Critical,Fix released] https://launchpad.net/bugs/129230608:59
sil2100Mirv, ogra_: maybe the workaroudn was in Mir itself?09:02
sil2100Or in qtubuntu/unity-mir? I remember seeing those branches when there were discussions about that09:02
ogra_sil2100, it involved Mir ...09:02
MirvI remember that Mir devs agreed that upstream is not going to change from what it decided in 5.1.0, so they're adapating to the new model09:03
psivaasil2100: uitk is all green. no crash this time09:06
ogra_i guess it is the same flakiness we saw before09:07
brendandhmm, now i can't reproduce the system-settings failure09:09
brendandi'll try a bootstrapped image09:09
sil2100uh09:12
Laneyit's not reproducible09:45
Laneyby the hand of man09:45
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #119 promoted | Need CI Train help? Ping: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
Mirvpopey: spamming complete, and filemanager uploaded10:26
popeythanks Mirv10:40
popeyMirv: could you also do dl when you get a mo.. http://s-jenkins.ubuntu-ci:8080/job/dropping-letters-click/lastSuccessfulBuild/artifact/com.ubuntu.dropping-letters_0.1.2.2.57_all.click10:41
ogra_sil2100, my flo sits on the boot animation since 5 min now ... (wizard ran fine before)10:48
ogra_ah, finally the UI started10:48
sil2100Uh10:48
sil21005 minutes?10:48
ogra_yeah10:48
sil2100What did it do for so long?10:48
ogra_no idea ... it has that since a while ...10:49
ogra_and the UI still hangs hard when starting an app10:49
popeyapport?10:49
sil2100brendand: any luck with the system-settings thing?10:50
sil2100Since if not, I guess it's time to kick a new image10:50
sil2100ogra_: ;/10:50
sil2100ogra_: so it seems it's still broken for flo then10:50
ogra_i'd say nothing is fixed here10:50
brendandsil2100, nope and Laney can't seem to reproduce it either10:50
sil2100ogra_: could you kick a new image then? We'll at least have the scopes fix10:51
sil2100om26er: hi!10:51
om26ersil2100, hey10:51
ogra_popey, apport on every boot ?10:52
sil2100om26er: could you help us in checking if the latest images have https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1339700 fixed?10:52
ogra_unlikely10:52
ubot5Ubuntu bug 1339700 in Mir "[regression] Device locks randomly on welcome screen" [High,Fix committed]10:52
popeyoh10:52
sil2100ogra_: we need someone working on this ASAP...10:52
ogra_i'm just watching the second boot here ... screen timed out the third time now ... with the animation up10:52
sil2100How can we promote an image if 2 of our officially supported platforms are broken ;/ ?10:52
om26ersil2100, ok, upgrading to the latest.10:53
om26ersil2100, which is the latest image currently ? 129 ?10:54
sil2100om26er: 13110:54
ogra_so when starting an app it hangs on the start animation too10:55
sil2100ogra_, brendand: hm, do you think these UI hang-ups in tablets are directly related to the autopilot tests being broken for them?10:55
ogra_they could10:55
sil2100ogra_, brendand: since if yes, we can somehow identify more-or-less in which image it started and trying to find the person responsible for it10:55
sil2100s/person/team10:55
brendandsil2100, and kill them?10:55
sil2100NO! Force them to fix it and THEN kill them10:56
ogra_i guess they are related10:56
ogra_sil2100, i would guess it started around 12310:57
ogra_which had a new unity but also a lot of Qt bits updated10:57
* sil2100 chokes Mirv then10:58
ogra_http://people.canonical.com/~ogra/touch-image-stats/123.changes10:58
ogra_hmm, not sure the Qt bits are atfault at all ... seems its all just plugins from other changes10:59
* ogra_ falshes 122 ... will take 20-30 min10:59
Mirvpopey: dropping letters done too11:00
Mirvsil2100: not my Qt stuff. but uitk is there among else11:00
sil2100:)11:00
ogra_yeah, UITK and unity8 are the most likely candidates on that list11:01
sil2100http://people.canonical.com/~lzemczak/landing-team/123.commitlog <- actually, only telephony, UITK and webbrowser stuff from the Qt side11:01
popeyMirv: ta, will be some more coming11:02
* sil2100 unchokes Mirv 11:02
Mirv:)11:03
sil2100;)11:07
=== pete-woods is now known as pete-woods|lunch
om26ersil2100, the bug says flo, do I need to test on mako11:16
sil2100om26er: well, it seemed to have happened also on mako from what I know11:17
sil2100om26er: and I think it got fixed in mako mostly11:17
ogra_no, i doubt that11:17
ogra_but it only shows very rarely there11:17
ogra_i have like two hangs per day with it ... while flo hangs all the time11:18
ogra_sil2100, 122 is fine on flo ... installing 123 now11:24
sil2100ogra_: thanks! :)11:24
popeysil2100: were you aware that payui 0.2.7 didn't land in the click store because it failed the tests? cc fginther  https://myapps.developer.ubuntu.com/dev/click-apps/878/changerequest/  see http://paste.ubuntu.com/7798095/11:34
sil2100popey: hm, I was unaware of that11:34
popeydoes the payui click get side-loaded in at build?11:35
popeyi cant see it in ogra_ changes11:36
ogra_http://people.canonical.com/~ubuntu-archive/click_packages/click_list11:36
ogra_com.canonical.payui_0.2.6_armhf.click11:37
ogra_obviously still the old one11:37
popeyyes11:37
=== MacSlow is now known as MacSlow|lunch
ogra_sil2100, so with 123 i definitely have the super slow startup after the wizard ...11:49
ogra_and confirmed ... starting an app makes the UI hang ...11:50
sil2100Yeaa!11:50
ogra_sil2100, so the issue is definitely in the packageset of 12311:50
sil2100ogra_: btw. could you kick a new image in the meantime?11:50
ogra_i did11:50
sil2100ogra_: ok, let's poke the unity8 and UITK people11:50
sil2100Oh11:50
sil2100Ok ;)11:50
ogra_hmm11:50
* sil2100 missed that11:50
ogra_why did the bot not announce it11:50
* sil2100 slaps imgbot around a bit with a large trout11:51
ogra_no, rather slap iso.qa.ubuntu.com11:51
ogra_there is no build running11:52
* sil2100 slaps iso.qa.ubuntu.com around a bit with a large trout11:52
ogra_stgraber, hmm, i seem to not be able to trigger touch image builds via the qatracker11:54
* ogra_ runs one manually 11:54
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #119 promoted | Need CI Train help? Ping: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
imgbot=== trainguard: IMAGE 132 building (started: 20140715 12:00) ===12:00
sil2100\o/12:01
sil2100Ok, inbetween stuff, let me check the commitlog agian12:01
* ogra_ makes a bootchart to see what delays the boot so much12:02
sil2100Saviq: hi! So, we're looking for the root cause of our overall problems with tablet form factors12:02
sil2100Saviq: this started off with #12312:02
sil2100Saviq: http://people.canonical.com/~lzemczak/landing-team/123.commitlog12:02
sil2100Saviq: from what can be seen in the commitlog, the only landings that could have affected that are unity8 and UITK, but I see that the UITK landing seems to be some minor change12:03
sil2100ogra_: hm, gles update as well, but I guess unrelated12:03
ogra_Saviq, HAPPY BIRTHDAY !!!12:03
sil2100Oh!12:04
ogra_sil2100, well, who knows ...12:04
sil2100Birthday?12:04
sil2100Saviq: happy birthday then! :)12:04
ogra_the mesa update might have impact (it shouldnt, but might)12:04
sil2100Saviq: yeah, so mesa is also a candidate, but still it would be nice to have someone looking at this12:05
=== alan_g is now known as alan_g|lunch
sil2100ogra_: hmm... actually, maybe you could try downgrading mesa on your 123 image? Do you have some free time?12:06
sil2100ogra_: since you could download the earlier .deb packages, install them and see if it works (just hope it won't force any removals)12:06
ogra_i dont even have the free time for what i did up to now ... but yeah, i can try once it is done with the bootchart12:06
* sil2100 is sad the he doesn't have a tablet12:07
ogra_i doubt mesa has anything to do with it though ... UITK or unity8 is my guess12:07
ogra_and the unity8 change set is quite big12:08
sil2100ogra_: UITK doesn't seem to be responsible, it's only a dep-versioning change12:10
sil2100ogra_: additions of (= ${binary:Version})12:10
sil2100ogra_: so unity8... but I'm not sure if the symptoms look like unity8-stuff?12:12
Saviqsil2100, ogra_, thanks!12:12
sil2100Saviq: ^ could you take a lookie anyways? :)12:12
Saviqsil2100, that unity8 landing couldn't cause anything12:12
sil2100Saviq: it seems to affect all tablets12:12
ogra_sil2100, well, the app-startup animation shows up, the three dots rotate three times and the UI hangs hard for about 30sec12:12
Saviqsil2100, that unity8 landing just added two (unused atm) properties to the mocks12:12
=== psivaa is now known as psivaa-off
Saviqogra_, sil2100 30s?12:13
ogra_sil2100, yeah12:13
ogra_err12:13
ogra_Saviq,12:13
Saviqbug #1340086 ?12:13
ubot5bug 1340086 in telephony-service (Ubuntu) "Importing Ubuntu.Telephony 0.1 causes hang when there's no telephony accounts" [High,Confirmed] https://launchpad.net/bugs/134008612:13
ogra_Saviq, got a flo around ?12:13
Saviqogra_, mc-tool12:13
Saviqmc-tool list12:13
ogra_root@ubuntu-phablet:~# mc-tool list12:13
ogra_mc-tool list: Failed to connect to D-Bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X1112:13
ogra_:P12:13
Saviqogra_, sil2100, oh I read the commitlog wrong12:14
ogra_there is indeed no telephony account on my non-3g flo12:14
Saviqogra_, sounds like your phablet session is bad12:14
ogra_Saviq, well, all sessions since image 123 are12:14
Saviqsil2100, yes, it's unity8's in-call indicator12:14
ogra_oh, wait12:14
sil2100uh oh12:14
Saviqsil2100, and the above bug in telephony service12:15
ogra_phablet@ubuntu-phablet:~$ mc-tool list12:15
ogra_phablet@ubuntu-phablet:~$12:15
ogra_:P12:15
ogra_indeed i was root above12:15
ogra_returns immediately12:15
Saviqogra_, correct, but telephony-account times out after 30s, searching for a ofono account12:16
ogra_Saviq, and that is queried every time i start an app ?12:16
Saviqogra_, check ~/.cache/upstart/unity8.log12:17
sil2100Lunch time, brb12:17
Saviqogra_, should have a bunch of https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1340086/comments/212:17
ubot5Ubuntu bug 1340086 in telephony-service (Ubuntu) "Importing Ubuntu.Telephony 0.1 causes hang when there's no telephony accounts" [High,Confirmed]12:17
ogra_yup, seems i have that ...12:19
ogra_Saviq, so why would that happen for any app i start then ?12:28
Saviqogra_, because we talk to the telephony service when app focus changes12:29
ogra_dies the startup actually query the telephony accounts when i start an app ?12:29
ogra_oh, wow12:29
Saviqogra_, it's apparently not only on startup12:29
ogra_right12:29
ogra_it makes flo completely unusable12:29
SaviqI can imagine12:29
ogra_so i assume the slow session startup is related ...12:29
Saviqyesss12:29
Saviqlet's talk with boiko whether he has a quick fix, otherwise let's revert the in-call hint12:30
ogra_in the bootchart i see everything starting just fine ... but nothing on screen until about 2 min into the boot ... so i guess it even queries multiple times during startup12:30
ogra_Saviq, hmm, so i guess the hangs we see on mako are unrelated then ...12:32
Saviqogra_, aren't hangs on mako due to Mir deadlock?12:34
=== MacSlow|lunch is now known as MacSlow
sil2100ogra_, Saviq: the hangs *might* have been fixed now with the last mir upload, so hm12:35
sil2100For mako that is12:51
ogra_Saviq, i cant tell12:53
ogra_right, i dont run -proposed here12:53
sil2100om26er: were you able to confirm the hang-ups got fixed for mako?12:57
om26ersil2100, that didn't happen for me12:58
om26ersil2100, but then I never saw that before as well12:58
ogra_it is really hard to reproduce since it only happens after a while of usage13:01
sil2100ogra_: do you remember around what hour boiko appears?13:04
sil2100I would be nice to have him looking at it ASAP13:04
boikosil2100: now maybe? :)13:04
ogra_not really, but i guess soon :)13:05
sil2100Oh oooh!13:05
sil2100;)13:05
sil2100boiko: hello!13:05
boikosil2100: I'll look into that, but first we need to land the majority of the dual sim work :/13:05
=== alan_g|lunch is now known as alan_g
sil2100boiko: so, it seems there's a serious issue with telephony-service that causes all tablet devices being basically unusable ;/13:05
boikosil2100: yep, Saviq reported that to me, I'll look into that soon13:06
sil2100boiko: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1340086 <- it would be nice if this could also be a high-priority thing, as per ogra_'s observations it makes tablets really b0rken13:06
ubot5Ubuntu bug 1340086 in telephony-service (Ubuntu) "Importing Ubuntu.Telephony 0.1 causes hang when there's no telephony accounts" [High,Confirmed]13:06
sil2100boiko: thanks :)13:06
rsalvetisil2100: can I get a silo for line 26?13:16
sil2100rsalveti: sure, didn't get a ping yet13:16
sil2100Oh, here it is ;)13:16
rsalveti:-)13:17
=== pete-woods|lunch is now known as pete-woods
rsalvetisil2100: thanks13:23
sil2100yw13:24
sil2100fginther: ping :)13:25
fginthersil2100, hey13:25
rsalvetisil2100: hey, question about the gles packages, I'll create bzr branches for them, and for CI to work properly with them, do we need a project per branch, or would it be fine to use a branch based on the upstream project?13:34
rsalvetilike, having the qtubuntu-gles branch as part of the qtubuntu project13:35
imgbot=== trainguard: IMAGE 132 DONE (finished: 20140715 13:35) ===13:35
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/132.changes ===13:35
bzoltan1sil2100: rsalveti: the UITK build in the silo9 is good to go. It has a two line change in the debian/rules from xnox, so it will need an extra ack13:35
* popey updates13:36
sil2100bzoltan1: ok, will deal with it in a moment13:37
boikosil2100: https://code.launchpad.net/~boiko/telephony-service/fix_freeze/+merge/22682813:45
boikosil2100: I'll wait for jenkins to run and then I'll do the checklist and ask tiago to review it13:46
sil2100boiko: that was FAST13:46
sil2100WOW13:46
sil2100;)13:46
sil2100boiko: ok, once he approves it, let's please get it in a silo ASAP!13:47
sil2100boiko: thanks! :)13:47
boikosil2100: sure, no problems13:47
sil2100ogra_: if anything, let's not promote an image before this lands ^13:47
sil2100ogra_: so I guess no promotions today13:47
sil2100rsalveti: are you usually publishing silos yourself or can I do it?13:53
sil2100Ah13:53
sil2100Ok, I see you publish yourself ;)13:53
rsalvetisil2100: yeah :-)13:53
sil2100rsalveti: nvm!13:53
rsalvetisil2100: not sure if you got my previous question, about the gles packages13:53
sil2100rsalveti: ah! Sorry, missed it, let me backlog13:54
ogra_sil2100, indeed13:54
sil2100rsalveti: so, citrain doesn't require a separate lp project per component, so it can be a sub-branch actually - CI Train only cares if he can merge one branch into another ;)13:55
sil2100rsalveti: so it's fine13:55
rsalvetisil2100: lovely, thanks13:55
Saviqtrainguards, can someone please upload the two pkgs from http://people.canonical.com/~msawicz/qt/qtcomp.tar to silo 006 please?13:57
sil2100Saviq: o/13:58
Saviqsil2100, please reconfigure the silo, too, added those two as additional source packages13:58
sil2100Sure thing13:59
brendand_wow - image notifications are working :)14:05
rsalvetiSaviq: packaging branch might work for some but might confuse some as well (for the gles packages), guess a normal bzr branch will probably be easier14:06
rsalvetiwill start from the same root, so they can at least me merged14:06
sil2100Saviq: packages uploaded14:06
Saviqsil2100, thanks14:06
sil2100Had to re-sign them so it took a few moments14:07
Saviqrsalveti, why confuse? are there source changes ever? and if there are, shouldn't they be patches?14:07
rsalvetiSaviq: no source changes, but I'm thinking about what could happen when someone decides to land something14:08
rsalvetion a packaging branch you need to point out, or import, the orig tarball14:08
Saviqrsalveti, so the orig tarball can't be the non-gles one?14:08
rsalvetiSaviq: can, but you'd need to import that when landing something via a silo14:09
rsalvetiand that's when I think it'll confuse some people14:09
Saviqrsalveti, I think having a separate source branch confuses more :|14:09
Saviqrsalveti, at least when it's packaging only it's clear it's meant to build from some tarball somewhere, you just need to place it next to the packaging branch14:10
rsalvetiright, but if you want to land both the original and the gles version at the same silo, you'd need to first build the original one and then import the orig tarball in the other14:10
rsalvetiand rebuild the gles version14:10
Saviqrsalveti, yeah, and why's that bad?14:10
Saviqrsalveti, that's IMO what should happen anyway14:10
Saviqrsalveti, at least then it's a clear process of "what to do with -gles packages"14:11
rsalvetisure, fine by me, hopefully it'll work for everyone :-)14:11
rsalvetilet me give that a shot then14:11
Saviqrsalveti, if the non-gless builds in the PPA, do you think the train will be able to pick it up from there when preparing the -gles one? or will it require a manual upload anyway?14:12
rsalvetihm, but you can generate a bunch of orig tarball until you land the branch14:12
rsalvetiand import would mean you need to import in a branch that gets merged14:12
Saviqrsalveti, and you only really need to update the -gles just before you land14:13
Saviqrsalveti, I think my ideal workflow would be:14:13
Saviq1. build non-gles14:13
Saviq2. prepare an MP for packaging-only -gles14:13
Saviq3. build -gles14:13
Saviq4. -land14:14
Saviqsince before you build non-gles you don't know the version you'll get anyway14:14
rsalvetiright, the 2 step is the one I'm still thinking if it would work14:14
Saviqand you need to keep those in sync14:14
rsalvetibut should work I guess14:14
rsalvetibzr bd will probably find the right thing to do14:14
Saviqthat'd be great14:14
rsalvetiwe can try and see :-)14:15
rsalvetilet me create the branch for qtubuntu14:15
rsalvetiSaviq: bzr bd merge mode (only the packaging gets included in bzr) needs to find out the orig tarball, it seems there's no support to import the orig tarball in such branch14:18
rsalvetiif we can point that out to look for the orig tarball from the original project, in a ppa, that would work14:19
rsalvetinot sure if doable though14:19
Saviqrsalveti, not in a PPA probably :|14:19
Saviqrsalveti, especially when we're looking at multiple PPAs14:19
rsalvetiyeah14:19
rsalveti"In the future you will be able to use the merge-upstream command to do this for you, but it has not been made to support merge mode yet."14:20
rsalvetithe future that never came14:20
ogra_but it is bright at least14:20
Saviqrsalveti, but maybe somewhere where we can upload the tarball after it's generated in the silo...14:20
Saviqbut that starts beating the purpose...14:20
cjwatsonthe future's orange14:20
ogra_:)14:20
cjwatsongit ftw, pristine-tar works much more easily there14:20
rsalvetiyeah14:21
rsalvetiSaviq: then we'd need to keep it in a normal bzr branch14:21
Saviqrsalveti, no, we can point builddeb to just grab a tarball from somewhere14:21
rsalvetibut then you'd need to upload the package by hand14:22
Saviqrsalveti, why?14:22
Saviqrsalveti, I'd need to upload the tarball somewhere14:22
rsalvetihow can you tell it to grab from the ppa?14:22
rsalvetias you're still landing14:22
rsalvetiright14:22
rsalvetiand put it locally14:22
rsalvetiso it can find it in your machinage14:22
Saviqrsalveti, as long as we have a place where we put the in-flight tarballs14:22
Saviqthat we want -gles to build from14:23
rsalvetineeds to be a place where bzr bd can find14:23
Saviqrsalveti, it can be any http server AFAICT14:23
Saviqrsalveti, as long as it can be parsed into a version thingy14:24
Saviqrsalveti, stupider idea: since we need -gles MPs per-silo anyway, those MPs could point builddeb to the correct silo...14:24
Saviqrsalveti, but I agree it's not ideal :|14:24
rsalvetiSaviq: right, not much better than src package uploads14:25
rsalvetiand not sure if that's indeed supported, trying to find out in bzr-bd14:25
ogra_what happened to "Qt 5.3 will full support runtime detection for GL vs GLES" ?14:26
ogra_*fully14:26
Saviqrsalveti, it is, we're using it in qt packaging14:26
rsalvetiqt 5.4 in theory14:26
Saviqrsalveti, it's dl'ing from qt upstream directly14:26
rsalvetiSaviq: because in our case it'd need to find the orig tarball from a PPA and with a different name14:27
rsalvetilet me grab a qt package branch14:27
rsalvetiogra_: qt 5.3 only landed that for windows14:28
ogra_lol14:28
rsalvetiprobably because that were the money came from14:28
ogra_so we should just run out session under wine then14:28
ogra_*our14:28
Saviqrsalveti, that's why I was thinking like "Downloads" in https://launchpad.net/qtubuntu for example14:30
Saviqrsalveti, and yeah, the other stupid idea was to include (the dynamic part of) the URL to the .orig in the MP for -gles14:31
Saviqbut that'd be *so* hacky14:31
rsalvetiSaviq: we can create a custom get-orig-source in debian/rules that can retrieve the tarball from somewhere we want14:33
rsalvetibut then you'd need to change the PPA address to use at every landing14:33
rsalvetiwhich in theory is fine14:33
cjwatsonDoesn't bzr bd try to use uscan?14:34
cjwatsonSo it could go in debian/watch rather than a custom get-orig-source target14:34
cjwatsonNot that that helps much14:34
rsalvetiright, would need to change at every landing14:35
rsalvetibut probably easier to maintain14:35
rsalvetiSaviq: would that work for you?14:36
=== gatox is now known as gatox_lunch
sil2100kgunn: so, regarding line 30 - it seems that currently almost all components from that landing (instead of mir) are locked by other silos14:43
Saviqrsalveti, yeah, that's what I proposed as the "stupider" idea ;)14:44
sil2100kgunn: how far are you with silo 2 for instance?14:44
kgunnsil2100: silo2 is on hold for this mir landing actually14:44
kgunnsorry about that14:44
rsalvetiSaviq: but guess it's the only one if we want a packaging branch14:44
kgunnwe should have said14:44
kgunnsilo 15 is test only14:45
kgunnsilo 6 is test only (atm)14:45
sil2100kgunn: ok, so let me flush silo 2 in the meantime, no use for it to 'hog' a silo since it will anyway need a rebuild14:45
kgunnactually....we'll drop silo15 altogether14:45
kgunnin favor of the unity-mir as part of the mir silo14:45
Saviqrsalveti, well, the other one I proposed was a static place where we'd upload them, but not overly better14:46
sil2100kgunn: ok, so 15 can be dropped as well?14:46
rsalvetiSaviq: yup14:46
sil2100kgunn: so, I'll free up silo 2 and 15 and assign a silo for line 3014:46
sil2100kgunn: does that sound ok?14:46
sil2100kgunn: just one last thing - what about silo 16? Will that land soon?14:47
sil2100kgunn: since 16 has platform-api14:47
* kgunn checks14:47
sil2100kgunn: it's the QtCompositor landing, importantish it seems14:48
kgunnsil2100: you mean silo6 not 16 right ?14:48
kgunnyeah...qtcomp....it will land after mir14:48
sil2100kgunn: ah! Crap, yes, sorry ;)14:48
kgunnjust a matter of approval churn14:49
sil2100kgunn: right, 006 I meant, damn14:49
sil2100Ok, so mir 0.5.0 goes first14:49
kgunnmir is ready to rock...but qtmir we've got some approvals/reviews to get through14:49
kgunnyep...thanks14:49
sil2100kgunn: just a notice though... we'll probably prefer not to land Mir before promoting, and I would expect having a promotion around tomorrow14:49
sil2100Is that fine?14:50
Saviqrsalveti, hmm hmm, the custom get-orig-source could try all the 20 silos in theory... but that'd be a problem if the same source would be in two silos...14:52
rsalvetiyeah, no good14:53
rsalvetiwe already have one silo that is using qtubuntu for testing (qtmir)14:53
sil2100kgunn: if that's fine with you then I do those flushes and assign a silo for you14:55
seb128kgunn, sil2100: just as a fyi, I'm doing a settings landing, which means the qtcompositor silo might need a rebuild later again14:55
sil2100seb128: ACK14:55
kgunnseb128: thanks for the heads up14:55
kgunnsil2100: yes, perfect flush away and prime the pump for mir0.514:55
kgunnits a small mir bump14:56
kgunnbasically last little bit needed for trusted prompt sessions14:56
seb128kgunn, let me know when you are close from landing and that we should stop hijacking your silo btw ... sorry for doing that, but we can't really lock settings work while your test silo is waiting14:56
kgunnseb128: not a problem!....actually could you or someone you designate please review and approve https://code.launchpad.net/~unity-team/ubuntu-system-settings/use-qtComp/+merge/22554014:58
kgunnand14:58
kgunnhttps://code.launchpad.net/~saviq/ubuntu-system-settings/fix-wizard-sim/+merge/22655514:58
* kgunn check to see they up for review :P14:58
seb128kgunn, sure, the day it's changed from "work in progress" to "needs review" ;-)14:58
kgunnseb128: dang it :)14:58
Saviqkgunn, that last one is landed already14:58
kgunnta14:58
kgunnseb128: ok, changed that one to "needs review"14:59
kgunnhttps://code.launchpad.net/~unity-team/ubuntu-system-settings/use-qtComp/+merge/22554014:59
seb128kgunn, thanks14:59
Saviqsil2100, can you please reupload qtubuntu-gles to silo 006, but remove TODO from debian/docs first? :|15:03
sil2100Saviq: hm, let me see15:03
rsalvetiSaviq: mind giving https://code.launchpad.net/~phablet-team/qtubuntu/gles/ a try?15:13
rsalvetiSaviq: you'd need to create an MR bumping the changelog and changing debian/watch15:14
Saviqrsalveti, I think that'd be awesome enough15:14
Saviqrsalveti, looks real good15:15
rsalvetiSaviq: great15:15
rsalvetiwill do the same for the other ones15:15
Saviqrsalveti, the only disadvantage I can see is that won't work after the silo is freed15:16
Saviqrsalveti, but then you'll be able to just pull the tarball from distro instead15:17
rsalvetiyeah15:17
camakofginther, jenkins is not reviewing my MPs that I put up. Do you happen to know why?15:17
Saviqrsalveti, so I'm fine with that15:17
Saviqrsalveti, any preference to where we'd be putting those branches?15:17
sil2100Saviq: I'll have to bump the version to re-upload...15:17
fginthercamako, do you have an example?15:17
Saviqsil2100, just the ubuntu part, no?15:18
Saviqsil2100, that should be fine I think15:18
camakofginther : https://code.launchpad.net/~cemil-azizoglu/mir/nested_lifecycle_events/+merge/22442615:18
rsalvetiSaviq: under the original projects15:18
sil2100Yeah15:18
Saviqrsalveti, lp:qtubuntu/gles?15:18
Saviqrsalveti, or do we not want to register a series?15:18
camakosomeone added "PS Jenkins bot" as reviewer but didn't help15:19
camakofginther ^15:19
fginthercamako, it should be fixed now, there is an access list that needs to be updated15:20
camakofginther, thanks15:20
rsalvetiSaviq: a series would be fine15:21
rsalvetilet me create one15:21
rsalvetifor qtubuntu15:21
Saviqrsalveti, awesomes15:22
rsalvetiSaviq: done, let me do a similar change for the other ones15:22
Saviqrsalveti, could you make the current ones point at distro and not at a silo yet?15:23
rsalvetiSaviq: sure, just added it initially with a silo/ppa to be easier to change15:24
Saviqrsalveti, uh oh, just thought or something15:24
ogra_stop that !15:24
Saviqrsalveti, if we drive those with MPs, train will overwrite the version15:24
ogra_:)15:24
rsalvetiSaviq: but on the gles side you'd change the changelog yourself15:25
Saviqrsalveti, and will try to look for an .orig that doesn't exist15:25
rsalvetiand you'd know already the version you have for the upstream one15:25
Saviqrsalveti, still, means manual upload to the silo15:25
rsalvetinops15:25
Saviqno? ok15:25
rsalvetiSaviq: you bump the changelog for the gles package, let it as UNRELEASED, and it works fine15:26
Saviqrsalveti, if you say so, we'll find out soon enough :)15:27
rsalveti:-)15:27
fginthercamako, also, I have a configuration ready to add -ci and -autolanding jobs for lp:mir/0.4 and lp:mir/0.5. https://code.launchpad.net/~fginther/cupstream2distro-config/add-mir-0.4-0.5/+merge/22686415:28
fginthercamako, these are both setup to do the exact same build and testing that is done for the devel branch15:29
ogra_plars, does the mako 132 testing hang somewhere or am i to impatient again ?15:31
ogra_oh, ignore me, seems it has actually moved15:32
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #119 promoted | Need CI Train help? Ping: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
=== gatox_lunch is now known as gatox
Saviqrsalveti, fingers crossed https://ci-train.ubuntu.com/job/landing-006-1-build/110/console15:44
Saviqrsalveti, so... I forgot to update the ppa, but :|15:46
Saviquscan warning: In watchfile /tmp/tmpfcdDzF, reading webpage15:47
Saviq  http://ppa.launchpad.net/ci-train-ppa-service/landing-021/ubuntu/pool/main/q/qtubuntu/ failed: 404 Not Found15:47
Saviquscan could not find the needed tarball.15:47
Saviqbzr: ERROR: Unable to find the needed upstream tarball for package qtubuntu-gles, version 0.60+14.10.20140715.15:47
Saviqversion gets mangled regardless of my changelog entry15:47
kgunnogra_: Saviq ...so when we get to the point where we wanna land qtmir, for the twin do we just need a no-change commit on qtmir/qtmir-gles15:49
kgunn?15:49
Saviqkgunn, we need a separate silo for them, that's for sure15:50
kgunnadd it to the silo and done?...or some other magic needs to happen?15:50
kgunnright...gets its own silo15:50
Saviqkgunn, as for no-change commit, the jury's still out on that...15:50
kgunncool...i know there's some comments to work through...and slangasek is gonna package review....so we got a day i'm sure15:51
Saviqkgunn, we're trying to find out whether we can drive it with MPs15:51
Saviqkgunn, if not, we'll need a manual upload to the PPA15:51
ogra_right .. -gles packages --> rsalveti15:51
ogra_:)15:51
sil2100;)15:51
kgunnright...what i refer to as "magic"15:51
* kgunn makes note...magic == rsalveti15:52
ogra_++15:52
ogra_brendand, hmm, didnt you land something for the mediaplayer-app failures ?15:53
ogra_(scene_selector hasnt been skipped in 132)15:54
sil2100Maybe elopio did?15:55
sil2100Since I know he said something about that15:55
ogra_dunno, i only saw an MP ...15:56
ogra_i thought that landed actually15:56
fginthercamako, is lp:mir/0.4 now obsolete?15:56
kgunnfginther: will be15:56
camakofginther, yes will be soon15:56
kgunnwe're workin' on lp:mir/0.515:56
elopiosil2100, ogra_: we have the branches ready.15:56
elopionot yet landed.15:56
ogra_ah, k15:57
ogra_we didnt have the failure in 13115:57
cjwatsonsil2100: Have you thought at all about how we might handle ubuntu-rtm silos in CI Train?15:57
ogra_thats what made me think it already landed15:57
camakofginther, @config for lp:mir/0.4, I'd say no need...15:57
fgintherkgunn, camako, thanks, I'll just plan for having 2 job configurations defined and we'll just stagger them as new ones are created and old ones obsoleted.15:57
cjwatsonsil2100: ("no" is perfectly reasonable, just want to check before starting to try to sort through it ...)15:57
camakofginther... thanks that sounds good too15:58
kgunnfginther: thanks for letting us be a pain in the butt15:58
sil2100cjwatson: sadly, no, didn't really get myself up-to-date with that yet15:58
sil2100Even15:58
cjwatsonOK.  We're going to need to have two sets of silos; the reason to use a derived distro for all this is that it keeps builds insulated from things like chroot updates in the Ubuntu primary archive, and so we'll need one batch of silos for ubuntu and another for ubuntu-rtm15:59
brendandogra_, it's in progress still. going to push to get it landed today15:59
cjwatsonWhich also means, I think, that people will need to declare in the spreadsheet whether they're targeting RTM or not15:59
ogra_brendand, yeah, just learned that :)16:00
=== boiko_ is now known as boiko
Saviqrsalveti, so yeah, no go https://ci-train.ubuntu.com/job/landing-006-1-build/111/console :|16:02
Saviqrsalveti, train still mangles the date stamp even if you put a changelog bump in16:03
Saviqrsalveti, so we're back to manual uploads (still the packaging branch is good to have)16:03
Saviqbut it won't be autolanded16:03
sil2100robru: meeting!16:05
sil2100brendand: o/16:05
sil2100and/or elopio o/16:05
elopiosil2100: I'm having connection problems and keep getting disconnected. I'm sorry.16:07
sil2100elopio: no problems16:07
elopiosil2100: the only comment I had for today are the system settings crashes.16:08
ogra_they seem to be gone16:09
elopiothey are happening a lot on MPs, and yesterday it's the first time I saw them on the dashboard. Seems important.16:10
sil2100elopio: strange thing...16:12
brendandsil2100, sorry we had another meeting16:19
brendandsil2100, filemanager failures - booo16:19
brendandwhat's that about16:19
brendandpopey, !16:19
brendandpopey, have you been naughty?16:19
ogra_it's broken !!!16:19
popeybrendand: !16:19
popeyI have been a good boy and delivered fresh new apps to your phone, yes brendand16:19
rsalvetiSaviq: crap, indeed, it still appends the date16:19
brendandpopey, fresh new broken apps16:19
rsalvetithat's really annoying16:20
popeybrendand: they passed jenkins16:20
popeyfix yo infra bro16:20
ogra_rsalveti, no way to mangle it ?16:20
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #119 promoted | Need CI Train help? Ping: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
Saviqogra_, train will always mangle the +foo16:21
rsalvetiyeah16:21
ogra_ah, evil16:21
rsalvetinot sure if we have an option to skip that16:21
Saviqogra_, so well, it'll work as long as you build the same day ;)16:21
Saviqand the same amount of times16:21
rsalvetiyeah16:21
Saviqrsalveti, now we need to liaise with sil2100 ;)16:22
Saviqbut I need to go, I'm starting to digest myself from the inside16:22
ogra_not on your b-day dude !16:22
Saviqrsalveti, I'm still real happy with what you did, at least it's now something we can follow16:22
ogra_go have cake !16:22
Saviqogra_, yeah, that too ;)16:22
rsalvetiSaviq: oh, happy birthday :-)16:23
Saviqrsalveti, you already made it! :D16:23
Saviqthanks o/16:23
sil2100boiko: silo assigned, spreadsheet should update soon :)16:25
boikosil2100: nice, thanks!16:25
asacsil2100: was there a promotion today?16:27
boikosil2100: should I go ahead and build the packages or should I wait until the spreadsheet reflects the silo assignment?16:30
popeyasac: no16:30
asack16:32
slangasekpopey, sil2100: hmm, why not?  The known blockers were fixed yesterday, right?16:36
ogra_slangasek, new blockers16:39
ogra_slangasek, we only noticed today that the tablets were all completely unusable since a few days ... silo-02 has the fix for that16:40
ogra_we should be able to promote something tomorrow (after we got enough smoke testing from QA)16:41
ogra_err ... s/smoke testing/dogfooding/16:41
sil2100slangasek, asac: no promotions today - we thought that the Mir blocker fix will also make tablets better, but it seemed unrelated16:45
sil2100slangasek, asac: I won't allow for an image to be promoted that would mean our tablet devices being almost unusable16:45
sil2100A fix for that is in a silo16:45
sil2100We'll land that soon and make that our promotion candidate for tomorrow16:45
slangasekogra_, sil2100: ok, thanks for the info16:51
=== alan_g is now known as alan_g|EOD
xnoxsil2100: hm, why a packaging ack is needed, when packaging change was done by a core-dev?17:17
ogra_xnox, it isnt17:17
sil2100xnox: as CI Train doesn't do any smart checking, it just checks if there is a packaging change17:17
sil2100xnox: if we see a core dev doign the change we auto-publish17:18
cjwatsonhuman-auto-publish :)17:18
sil2100i.e. do not check what the change is about17:18
sil2100cjwatson: right ;p17:18
xnox=))))17:19
xnoxok.17:19
sil2100ogra_: the telephony-service fix released, once it lands in the archive we'll build a new image :)17:34
ogra_yeah17:34
sil2100ogra_: I already informed robru about tracking it, but if by any chance you notice it migrating yourself, please feel free to kick an image17:34
ogra_will  do17:35
* sil2100 goes on to make a long TODO list for tomorrow17:35
sil2100Things keep piling up17:35
sil2100o/17:40
bfillerrobru: could you reconfigure silo 10? I added address-book and telephony-service which were not there originally17:51
asacso tomorrow max care?18:11
ogra_asac, who is that ?18:16
robrubfiller, done18:19
ChrisTownsendtrainguards: Hi, could someone hit the publish button for silo-014?18:20
robruChrisTownsend, can you mark it testing:pass in the spreadsheet?18:21
ChrisTownsendrobru: Um, sure.  What's the spreasheet link again?  bregma usually takes care of this, but he's out this week.18:22
robruChrisTownsend, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=018:23
robruChrisTownsend, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=32 rather this page specifically18:23
ChrisTownsendrobru: Thanks, just got the link in the mail too.18:23
ChrisTownsendrobru: So just mark "Testing done" to "Yes", correct?18:24
robruChrisTownsend, yes! we have a bot that pings when that's done ;-)18:24
ChrisTownsendrobru: Oh, cool.  Ok.  Nothing like learning by the seat of my pants:)18:25
pmcgowanChrisTownsend, welcome to CI madness18:26
ChrisTownsendpmcgowan: lol, thanks!18:26
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: citrain | CI Train Status: #119 promoted | Need CI Train help? Ping: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
ChrisTownsendrobru: Seems a manual ack is needed to publish silo-014.  Is there anything I need to do?18:36
robruChrisTownsend, nope, I'm on it18:36
ChrisTownsendrobru: Greats, thanks18:37
ChrisTownsendErr, great even18:37
robruChrisTownsend, you're welcome!18:37
robrubfiller, the problem in silo 10 is that there's another telephony-service just published from silo 2 which hasn't been merged yet18:40
bfillerrobru: ok, I'll hold off until that merges18:40
robrubfiller, ah, silo 2 is merged now, your build should work if you want to try it again19:06
bfillerrobru: thanks19:09
robrubfiller, you're welcome!19:09
rsalvetirobru: new image?19:22
robrursalveti, soon. telephony-service is still in proposed according to rmadison19:22
rsalvetioh =\19:22
robrursalveti, shouldn't be long though, LP already says it's landed and the silo even is already merged. so maybe 10mins or so19:23
rsalvetigreat19:23
ToyKeeperCool, system-settings-wizard crashed after configuring on first boot.19:32
robrursalveti, aha, it's landed now, want to kick an image? ;-)19:35
rsalvetirobru: sure19:35
boikorobru: thanks for triggering the merge&clean job on silo 919:35
robruboiko, you're welcome!19:35
imgbot=== trainguard: IMAGE 133 building (started: 20140715 19:40) ===19:40
ogra_rsalveti, how did you kick that image ? isotracker didnt show that it is re-building19:45
rsalvetiogra_: nukasan as usual19:46
ogra_please dont !!19:46
ogra_we all use the isotracker ... that keeps track if an image is currently building19:46
rsalvetiand how can I use that?19:46
rsalvetisorry if I lost the memo19:46
ogra_(and shows that to me if i click on "build" again)19:46
ogra_http://iso.qa.ubuntu.com/19:47
ogra_log in ...19:47
rsalvetiwhen did we change this?19:47
ogra_about 6-7 months ago19:47
rsalvetiwell, we added support for that, I know19:47
rsalvetibut when did we decided not to use nukasan19:47
ogra_use nusakan if the tracker has issues or so19:47
ogra_but for general builds better use the tracker so others know you started a build already19:48
ogra_rsalveti, about 6-7 months ago19:48
ogra_:P19:48
rsalvetiwell, you told me to use nukasan a few weeks ago19:48
rsalveti:-)19:48
ogra_when dider was still doing the train19:48
rsalvetino, that was a while ago19:48
rsalvetiogra_: anyway, where should I click?19:48
ogra_rsalveti, i remember ... the tracker was broken19:48
ogra_no, i mean when dider was still doing the train we changed the rule to use the tracker ...19:49
rsalvetiright19:49
ogra_so i unchecked all products except touch on the lleft19:49
ogra_then i click on "utopic daily"19:50
rsalvetiI don't see touch here19:50
ogra_heh, other way round19:50
ogra_click utopic daily19:50
rsalvetiright19:50
ogra_then uncheck all but touch19:50
ogra_that should leave you with two entries19:50
rsalvetiyup19:50
ogra_check the checkboxes, scrolll down ... click "update rebuild status"19:51
ogra_thats it19:51
rsalvetibut then I need to select an arch?19:51
ogra_the entry next to the checkbox should have (rebuilding) or some such next to it then19:51
ogra_click the checkbox in the header19:51
ogra_it selects both19:52
rsalvetiright, but I can only select the checkboxes after I already selected either armhf or i38619:52
ogra_?19:53
rsalvetihm, and I don't see update rebuild status19:53
ogra_http://iso.qa.ubuntu.com/qatracker/milestones/315/builds19:53
ogra_thats what i'm looking at19:53
rsalvetiogra_: that's what I get19:54
rsalvetibut I only see Ubuntu Touch armhf / Ubuntu touch i38619:54
rsalvetiif I click on armhf or i386 I can select all the test cases19:55
ogra_http://people.canonical.com/~ogra/isotracker.png19:56
rsalvetibut then in the actions I get: Passed with no bugs, subscribe, unsubscribe19:56
rsalvetiogra_: not what I get here19:56
* ogra_ doesnt get it 19:56
rsalvetiogra_: not sure if I need to be included in a specific group19:56
ogra_you need to be in cdimage19:56
ogra_or alternatively in core-dev i think19:57
rsalvetithought core-dev would be enough19:57
ogra_yeah, should19:58
ogra_but anyway, you would be in both19:58
rsalvetiogra_: http://people.canonical.com/~rsalveti/iso.png19:59
ogra_rsalveti, bah19:59
rsalvetiit might need yet another special group :-)20:00
ogra_looks like a permission issue20:00
ogra_yeah20:00
rsalvetiogra_: who can track that down?20:00
ogra_rsalveti, got it20:01
ogra_rsalveti, https://launchpad.net/~ubuntu-touch-release20:01
ogra_cjwatson, can you add rsalveti to https://launchpad.net/~ubuntu-touch-release please ?20:02
rsalvetioh, an special group :-)20:02
ogra_that was initially for proposed migration block/unblock20:02
ogra_but iirc it was also used for the isotracker access20:02
rsalvetigot it20:03
ogra_so yeah, use nusakan until we got that sorted :P20:03
ogra_dang20:03
rsalveti:-)20:03
rsalvetiwill use that once I'm allowed :-)20:03
ogra_thanks20:04
ogra_we should add sil2100 to it too20:04
robruogra_, oh can you add me to the group of people who can kick image builds? seems I'm constantly begging people to do that for me20:07
ogra_robru, no, i cant, but cjwatson does ...20:08
robruah20:08
ogra_robru, i'll talk to himm tomorrow (he seems gone)20:08
robruogra_, thanks20:08
ogra_and get you, sil and ricardo added20:08
ogra_(if there are no objections ... i *think* initially team membership was bound to core-devs)20:08
ogra_(because you can fiddle with proposed migration too with the power this team gives)20:09
robruogra_, ah I see.20:09
robruogra_, well sil and I are supposed to be working towards core dev status sooner or later...20:10
ogra_++20:10
imgbot=== trainguard: IMAGE 133 DONE (finished: 20140715 21:35) ===21:35
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/133.changes ===21:35
bfillerrobru: need an reconfigure on silo 10 again please21:51
robrubfiller, done21:51
bfillerrobru: thanks21:51
robrubfiller, need the MP url, not branch url21:51
robruit failed21:51
bfillerdoh21:51
bfillerrobru: fixed21:53
ricmmrobru: hi, silo 009 has been tested and works fine, could you help me publish it?21:59
robruricmm, sure one sec21:59
ricmmthank you21:59
robruricmm, you're welcome22:01
ricmmrobru: cheers!22:03
popeyballoons: you about? shall we push fm to the store in readyness for the morning image?22:49
cjwatsonogra_,rsalveti: done.  I can only add core-devs - that may have been "initially" but hasn't been rescinded.22:53
cjwatsonogra_: I certainly don't mind Ɓukasz and Robert being able to trigger image builds, but you'll have to ask stgraber to extend that facility beyond the ubuntu-touch-release team22:53
cjwatson(maybe we need YA team)22:53
robruricmm, false alarm, everything's ok23:09
tedgrobru, Silo please for line 3223:20
robrutedg, oh oops, I thought I had done it but it failed due to the conflicts in silo 8. ok you got silo 13 now23:21
tedgrobru, Cool, thanks!23:21
robrutedg, you're welcome!23:22

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!