[00:04] It'd be nice if freenode wouldn't freak out when I change the host connected to my proxy... as I'm about to do. Probably gonna get flood-kicked in a moment. [00:07] popey my znc is all confused it seems :-P [01:07] good "evening" all [01:16] Wellark, Are you testing silo 19? [01:16] tedg: which one is that? [01:16] tedg: ... [01:17] * Wellark goes to get a clue [01:17] Wellark, connectivity api singleton [01:17] oh, that [01:17] just land it [01:17] if it compiles, and tests pass it's fine [01:18] same for silo 11 [01:18] that can be landed as well [01:18] Wellark, Is no one using connectivity api that we should check? [01:19] tedg: not yet [01:19] I landed it like on Friday [01:19] and have not announced it on the ubuntu-phone ml yet [01:19] will do it when silo 19 lands [01:19] k [01:19] tedg: so, please mark both silos "Testing Done" [01:20] wtf.. it's 4am already.. [01:20] * Wellark sometimes wonders what is the meaning of life [01:22] Wellark, It seems that 11 should be installed on a device and made sure it's sane, we're definitely using indicator-network. [01:22] dobey: Around? The ubuntuone-credentials test plan seems to be out of date. [01:23] tedg: it's sane [01:23] trustme [01:24] it's just a try {} catch {} [01:24] nothing more [01:24] try{} does not have side effects [01:24] Wellark, Sure, but that can easily break something.It could catch something that went through and was used before elsewhere. [01:24] and it will fix the #1 crasher on touch devices [01:25] tedg: trust me. it's a precision WMD [01:26] I'm going to be trying to land some other silos tonight so I'll be flashing, I can test that one too. [01:26] tedg: ok, thanks [01:26] tedg: the only "test" there is that indicator-network keeps running [01:27] tedg: and you can connect to an accesspoint using it [01:27] Wellark, K [01:30] trainguards: please publish silo 19 ASAP [01:30] it's an API break on a new QML module and we need it to land before users emerge [01:31] and I can't send an announcement email to the ML before it's landed [01:31] that's critical piece of API for the developers [01:40] Wellark: will do, just afk now [01:41] robru, You need to put it in language Wellark understands: "had an emergency, ran out of beer, getting more, be back soon" :-) [01:42] XD [01:43] and don't know if it's sad or funny, but that is just so true... [01:48] ToyKeeper: copy/paste worked for me...from browser to notepad [01:48] i found an issue with msg app last week and had filed a bug [01:49] seemed specific to msg app [01:49] also notepad-to-notepad seems fine [01:50] kgunn: From what I found, long-tap in the browser acts like a double tap, simply selecting the current word. I couldn't get the context menu to come up at all. [01:50] kgunn: Then I tried copy from notepad to SMS. I could select text, copy it, then long-tap in the SMS entry showed 'paste' greyed out. [01:50] right...the greyed out paste is the bug [01:51] Okay, the test plan didn't note anything about that case failing. [01:52] kgunn: Any ideas what happened with the browser's context menu? [01:52] also, the browser is really fickle...but you can get copy to come up [01:52] i mean i can (on multiple devices too) [01:53] The silo is approved since it fixes something and doesn't appear to break anything, but now there's a possible regression to track down. [01:53] ToyKeeper: whats the regression ? [01:54] https://bugs.launchpad.net/messaging-app/+bug/1360429 [01:54] Ubuntu bug 1360429 in messaging-app "paste prompt doesn't highlight" [Undecided,New] [01:54] https://bugs.launchpad.net/platform-api/+bug/1322238 [01:54] Ubuntu bug 1322238 in Ubuntu UI Toolkit "Copy/Paste availability inconsistent between apps" [High,New] [01:54] kgunn: The browser's context menu on highlighted text used to work... not sure when it broke. [01:55] (triple-click a paragraph to select it, tap-and-hold to bring up a context menu, and instead it just reduces the selection to the current word) [01:57] I can get it to copy a link, but it's supposed to be able to copy regular text, right? [01:57] ToyKeeper: oh, honestly, not sure about that....i've only ever copied like whole paragraphs [01:58] In any case, it looks like this isn't a mir issue. I originally thought it was because none of the copy/paste cases worked, but it seems to be individual app issues instead. [01:59] The SMS bug is known, and it seems the browser needs a bug filed too. [01:59] ToyKeeper: yeah for sure...it really is fickle [01:59] i see what you mean now too [01:59] kgunn: Any chance you could update the mir test plan with notes about expected failures and/or more specific steps known to work? [01:59] it has drag handles [02:00] and you can't really drag to a smaller amount of text [02:00] sure [02:02] Thanks robru! [02:02] Heh, I haven't been able to invoke the drag handle in the browser at all today, and in other places it's really really finicky. [02:02] tedg: you're welcome! [02:03] Then again invoking the drag handles on Android is usually difficult too. [02:03] robru, If you're back at a keyboard I'd love a couple of silos as well please. [02:03] tedg: sure just a sec, I'm doing your RTM one for 19 [02:04] robru, Cool [02:04] tedg: also you didn't specify a series for line 64 [02:04] robru, Sorry, fixed. [02:04] tedg: ok you got rtm2 for starters [02:05] === trainguard: IMAGE 209 building (started: 20140827 02:05) === [02:05] thanks queuebot, you're the best friend a man could ask for. [02:08] tedg: ok you got 12 and 14 for utopic [02:08] robru, Great, will build away. [02:09] charles, 14 is yours ^ [02:12] hold on to your butts, I'm gonna run the archive job, bot might freak out (but it really shouldn't!!) [02:16] ToyKeeper: sorry, the online-accounts trusted session stuff landing caused some visible changes, but the plan itself is basically the same. i've updated it [02:17] ok everything seems in order here [02:18] dobey: I got a little distracted mid-testing. Mostly, I just noticed that some "<" back buttons aren't there any more, and the 'add account' thing is gone too. [02:19] dobey: And, er, is there a way to test account creation on staging? I'd prefer if I don't have to delete accounts from production after each test. [02:23] dobey: I've also noticed issues getting to the account settings or to U1 accounts after going back, but it's not consistent and it's not just with the silo. Are there any known bugs about that at the moment? [02:23] ToyKeeper: yes. the easiest way is to run the "setup-staging.sh" script that is included in the pay-service package [02:23] Like, tapping U1 then cancel repeatedly tends to make it stop working. [02:24] alright, I am out. I may respond to pings later but no guarantees [02:25] ToyKeeper: i don't know if there are specific bugs filed or not. with online-accounts using trusted sessions now, there have been some behavioral changes as a result. but all those changes are in online-accounts itself [02:26] ToyKeeper: if you find bugs where system-settings or online-accounts stops responding or such, please file bugs against online-accounts for them [02:26] dobey: Just curious. It's not a silo blocker (happens without the silo too), but it's an issue I was hoping someone already knew about. [02:28] ToyKeeper: mardy would be the person to ask about it. i suspect that issue isn't limited to the u1 account plug-in, and if you hit cancel repeatedly for twitter/google/etc it has the same results? [02:28] Haven't tried the other account types yet. [02:29] Got pulled away just after I found it, and haven't gotten back to it yet. [03:12] dobey: Approved. [03:45] === trainguard: IMAGE 209 DONE (finished: 20140827 03:45) === [03:45] === changelog: http://people.canonical.com/~ogra/touch-image-stats/209.changes === [03:59] tedg: did you have time to test the $silo to get it landed+ [03:59] Wellark, The indicator-network one? [04:00] tedg: yeah [04:00] Wellark, Yup, merged and cleaned. [04:02] tedg: thanks! [04:02] np [04:05] Thought I could run through these ubuntuuitoolkit tests, but I might fall asleep before they finish. [04:06] Wellark: let's see [04:07] looks like published [04:08] indeed [04:08] I think it slightly missed #209 image though [04:09] Wellark: like, er, morning to you, or evening? [04:13] Mirv: something like that [04:13] or between [04:15] o_O [04:17] nice, a crasher fix [04:17] * Mirv updates mako [04:18] * Mirv goes crazy and will update new shiny Qt DPI support there too [04:40] Hmm, no thostr. [04:42] I wonder if anyone knows what bug is fixed in row 49 / rtm-013, "fix crash bug in network indicator". [04:42] It has no MP or bug attached. [04:43] ToyKeeper: looking at the PPA contents, it's https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1343341 [04:43] Ubuntu bug 1343341 in indicator-network (Ubuntu RTM) "/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most" [Critical,In progress] [04:43] something found from errors.ubuntu.com logs [04:44] Thanks! I didn't think about looking in the PPA. [05:08] hmm, ken is not online. anyway, that line 21 conflicts witch the Mir 0.7.0 landing which is also in rtm silo === asac` is now known as asac [07:04] sil2100: hello :) [07:07] sil2100: I'm confused about rtm landing silo 8 [07:08] sil2100: it says build fails because of missing libunity-scopes 0.6.3 which is exactly the version in pulls in...? [07:11] sil2100: or, can I specify somehow that libunity is built before the shell? === dbarth__ is now known as dbarth [07:25] sil2100, hey! if we get our stuff src-copied from u to rtm, do we also need to merge it intro rtm branches? or can we remove/disable these branches for now since we don't diverge from utopic? [07:31] Hey! [07:31] sil2100: good morning [07:32] pstolowski: you don't need rtm branches then, since you just need to make sure you release everything into both more or less [07:32] sil2100: how can I tell the builder to build the src packages in certain order? [07:32] thostr_: hey! Let me take a look on what exactly is happening [07:34] sil2100: we've a process question. bzoltan has run the usual 8h of tests on UITK on ubuntu. will he need to separately run the same 8h of test on ubuntu-rtm? [07:36] Mirv: from my current understanding, the testing will have to be repeated... but I'm not sure if that's the final decision and if QA doesn't have any ideas on getting this better [07:37] thostr_: ok, I kicked a rebuild of those packages... normally it would be stuck in a dep-wait, but I think the debian deps (maybe) weren't bumped [07:38] thostr_: so it's really hard to force a specific build order without build-deps, we might just have to rebuild the packages in this case (which is not a big deal I think) [07:39] sil2100: that's why we bumped the version to 0.6.3 to enforce the order... anyway, I keep my fingers crossed [07:42] bzoltan: ^ dual testing for dual landings for now... [07:42] sil2100: what did you rebuild? I cannot see it building [07:42] and after that, QA signoff [07:43] thostr_: now things build successfully from what I see - I kicked package builds in the PPA [07:43] Mirv: OK, I charge my device and run the tests again [07:43] sil2100: ah, ok, jenkins UI was slow [07:45] thostr_: so, actually the problem that happened is that well, the ubuntu-rtm archive had currently the 0.6.3+14.10.20140820.is.0.6.1+14.10.20140809-0ubuntu1 version of the package (so the build-dep of 0.6.3 in packaging has been satisfied), but since this version is a revert it actually was 0.6.1... so there was no packaging dep wait, as the builder thought it's already satisfiable by the archive [07:46] thostr_: that's a singular case, we rarely do reverts so such a thing should not happen again :) [07:47] sil2100: yes, that was still fallout from rtm landing testing from last week [08:01] brendand, davmor2: once you're up - there's a nifty list of QA sign-off tasks waiting for you :) [08:03] sil2100, so. many. signoffs === moon127` is now known as moon127 [08:03] sil2100, i've still got silo 3 from yesterday. i'll probably sign it off in a minute and move on [08:04] Excellent [08:26] sil2100: I don't care :P [08:27] sil2100: oSoMoN: did browser land in the end? [08:27] davmor2, looks like it did, thanks! [08:28] \o/ [08:32] sil2100: during the testing I got a crash, that's because mediascanner was now built before libunity... so, what we need to do is to combine the rtm silos 7 and 8 and rebuild the mediascanner part [08:32] sil2100, you need to remind people to set 'testing pass' even if they haven't done it [08:33] sil2100, otherwise it doesn't show up on the dashboard as requiring QA signoff [08:37] sil2100, morning! one question, I'd like to create a silo for location-service with two branches that should land in at least rtm (but would be nice to have it land on utopic too) what should I do?? I got lost with all those emails :-/ [08:38] mandel: one moment, I'll get back to you after the meeting [08:38] sil2100, awesome, thx [08:44] mandel: make a regular utopic silo, basically sil will make the rtm silo and copy the packages for you. [08:45] robru, ok, thx [08:46] sil2100: check your emails, i updated the rtm copy script with a fix from Ursinha that finds the dsc files for you, much less work that way [08:47] (Unless your train solution is working yet ;-) [08:47] mandel: you're welcome! [08:50] robru: there'a also the simple copy-archive tool from ubuntu-archive-tools [08:50] no dget/dput needed [08:51] Mirv: does it work across distros? I wrote a script specifically to download from a PPA, change distro, then upload to different distro PPA [08:51] Mirv: this was specifically for utopic to rtm [08:53] robru: yes, it works across distros and PPA:s (Debian/Ubuntu/PPA:s), pitti mentioned it on the mailing list [08:54] robru: https://code.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk [08:55] Mirv: http://paste.ubuntu.com/8152711/ ;-) [08:55] But thanks [08:56] ./copy-package -d debian -s sid --to-distribution=ubuntu --to-suite=utopic --to-ppa=canonical-qt5-edgers --to-ppa-name=qt5-daily $1-opensource-src :) [08:57] so that'd be probably -d ubuntu -s utopic --to-distribution=ubuntu-rtm --to-suite=14.09 --to-ppa=ci-train-ppa-service --to-ppa-name=landing-0xx [08:57] so it's a LP operation and the copy happens immediately [09:06] sil2100, some lines don't have merge requests [09:06] sil2100, is that allowed? [09:08] sil2100: on the latest rtm image I just got upgrade offer for Clock 3.1.69 [09:08] mandel: so! [09:08] which is what I uploaded [09:09] mandel: I see you already got an answer for your question ;) [09:10] Mirv: oh, didn't know this tool actually worked for ppa's as well! [09:10] Mirv: so the next rtm image should have clock 3.1.69 by default instead of as an upgrade? [09:10] brendand: which lines? [09:10] nik90, yep [09:10] sil2100: yeah, I've used for syncing from Debian to Qt landing PPA:s [09:10] nik90: yes [09:11] sil2100, yes, I'll request the silo for utopic and then will do the testing, once that is done you take care of the rest, correct? [09:11] ogra_: sil2100 in case you want to type it down somewhere, snakefruit syncs run at :11' and :41' [09:11] mandel: when ou request silo you get a silo for both utopic and rtm, and you'll need to currently test them both [09:12] http://people.canonical.com/~ubuntu-archive/click_packages/click_list already has the latest clock [09:12] shrotly after the publisher then [09:12] so lets build an image :) [09:12] ogra_: can you build a new image? [09:12] Right ;) [09:12] on it :) [09:12] rtm? [09:13] sil2100: but my last request on ice for time being [09:13] sil2100, lots of them at the bottom of the sheet [09:13] asac`, utopic, then rtm [09:14] cool [09:14] mandel: so, in a nutshell: you request a silo for utopic, we give you a silo for both, you build your merges for utopic, test it there and when you say that it's fine, we copy those packages to the ubuntu-rtm silo for you to do a quick double-check from the ubuntu-rtm side :) [09:14] * asac` waits for a new rtm image [09:14] 3h from now [09:14] sil2100, got it [09:14] well, a bit more since janis server takes time to sync [09:15] yo [09:15] maybe we have system-image before that [09:15] :) [09:15] lol [09:15] high hopes [09:15] * asac` hopes for a full moon night in porland [09:15] :P [09:15] then they will just drink more [09:15] and not work :P [09:15] hah. think stephane can do this in whatever state as long as he is awake :P [09:16] haha [09:16] a pro [09:16] bah, the SIM unlocking is totally messed up in 209 [09:16] (i just did an OTA) [09:17] oh and the carousel is back [09:18] (for music) [09:20] === trainguard: IMAGE 210 building (started: 20140827 09:20) === [09:20] thostr_: your landing conflicts with ted's indicator-transfer landing, so not assigning a silo yet. [09:21] unless that gets sorted out otherwise [09:21] their landing doesn't have a description even, though [09:22] I wonder if that https://code.launchpad.net/~charlesk/indicator-transfer/better-content-hub-use/+merge/232144 should be just taken to your landing [09:44] jibel: when QA signing of silo 8 please make sure you test that together with silo 7 (or vice versa) [10:00] sil2100, did anyone else pick up reminders? elopio? [10:00] sil2100, i might have some breathing space from silos in a few minutes [10:01] brendand: excellent! I didn't get any news from elopio, he was busy testing the clock up probably? [10:01] So you can take a look at that [10:03] sil2100, ok once i finish with this silo [10:06] mandel: ^ so there's the first double silo for you [10:10] double plus good ! [10:10] :) [10:17] looks like the utopic rootfs is done ... https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/utopic/ubuntu-touch [10:17] * ogra_ triggers an RTM build [10:20] hmm, "starting in 26 minutes" ... :( ... https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch [10:24] ogra_: that was just a temporary glitch for some reason [10:24] it's building, there are plenty of free builders etc. [10:25] ogra_: is the phablet-click-test-setup expected to work with the RTM images? [10:25] ogra_: ssh_exchange_identification: Connection closed by remote host [10:27] sil2100, can i get an answer on the spreadsheet question? [10:27] brendand: what's up? [10:27] sil2100, i was wondering why some silos don't have any MPs associated [10:27] sil2100, line 48 for example [10:28] brendand: these are RTM silos so we do them as source-package only [10:28] brendand: so we only push source-package copies there [10:28] (no MRs are involved in this) [10:28] sil2100, it makes it difficult to know what we're actually testing [10:29] brendand: you need to check the "Additional source packages to land" for a list of what to test [10:29] brendand: yeah, sadly, the package changelog should give info on what has changed [10:29] Mirv, awesome, thx! [10:30] sil2100, yeah i guess i can look at the diff [10:30] bzoltan, nothing changed between rtm or utopic images in that regard [10:30] shoudl function exactly the same [10:30] sil2100, it's not as easy but oh well [10:31] ogra_: all right.. it stopped working after i flahes rtm image after 207 [10:31] bzoltan, did you use --bootstrap ? [10:31] ogra_: not [10:31] (to get an up to date recovery) [10:32] ogra_: phablet-click-test-setup --wipe seems to help [10:33] bzoltan: ssh_exchange_identification during a click-setup means bzr (if using over ssh, most likely case) has errored [10:33] sergiusens: I figured that ... [10:43] sergiusens: I git this earler and I got it now too -> http://pastebin.ubuntu.com/8158275/ [10:43] bzoltan: update the clock app [10:43] bzoltan: that''s the same reason everything broke in ci [10:44] sergiusens: I see [10:44] sergiusens: could the phablet-click-test-setup just skip the app and carry on with rest of tests instead of just failing? [10:45] bzoltan: not by default; this is more of a ci tool; we don't want silent fails [10:46] sergiusens: it does not need to be silent... but it should not fail. And it is not just a CI tool. We have no other way to verify landings before going to the CI. [10:47] bzoltan: well pitti has been working on it's replacement for autopackage tests [10:47] bzoltan: in that respect; you just have a broken image; your verification would be incomplete [10:47] bzoltan: ask balloons about adt for clicks when he gets up [10:48] sergiusens: my verification takes 8-10 hours ... i could live that single 10 minutes app test to the end [10:49] sergiusens: anyway, how to update the ubuntu-clock-app? [10:49] bzoltan: system settings, check for updates? [10:50] === trainguard: IMAGE 210 DONE (finished: 20140827 10:50) === [10:50] sergiusens: ahh.. UI [10:50] === changelog: http://people.canonical.com/~ogra/touch-image-stats/210.changes === [10:50] there we go [10:50] bzoltan: or install that image ^ [10:50] * psivaa goes and kick a run [10:50] sergiusens: is there an RTM image with the fix? I should test anyway on the latest image. [10:50] psivaa, rtm should be ready in about 1h [10:51] bzoltan: wrt ogra_ would know [10:51] no idea, what is that fix you are looking for ? [10:51] https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-August/thread.html has all rtm landings [10:51] ogra_: some clock app update what will unbreak the phablet-click-test-setup [10:52] bzoltan: anyway; I don't do click testing anymore; log a bug and someone from the ci team will look; or do like most of us and prepare an MP [10:52] bzoltan, ah, yeah, thats the reason why we do all thae manually triggerd image builds atm [10:52] you can watch the rootfs building if you are bored :) https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch [10:52] sergiusens: All right, thanks for your help. [10:53] (still takes about 45min til it becomes a system-image after it built though ... and another 20-30 for krillin to pick up on it) [10:54] ogra_: i think I will go with the manual update :) [10:57] ogra_: ack, was going to start krillin tests, will do once 210 appears in utopic-proposed then [11:03] ogra_, do you know who'd be suitable to look at the add-apt-repository bug? it's really slowing down silo testing [11:03] ogra_, cjwatson is at debconf or something, right? [11:07] brendand, it needs launchpad changes first ... and afaik wgrant is looking into that (cjwatson told me) [11:08] for now you need to hack up the sources.list.d entry i fear [11:08] ogra_, yes - we're doing that [11:08] Well, the trivial thing to do would pretty much be to just s/ubuntu/ubuntu-rtm/ in python3-software-properties' ppa.py in ubuntu-rtm. [11:08] I hadn't realised citrain used add-apt-repository anywhere. [11:08] everywhere :) [11:08] well, not the train but the testers and tools === jgdx_ is now known as jgdx === MacSlow is now known as MacSlow|lunch [11:30] sergiusens: I flashed the #8 rtm image, updated the clock app. Still the phablet-click-test-setup fails [11:30] bzoltan, why did you flash the 8 image ? [11:30] you want 9 once it has built [11:31] 8 is old [11:34] ogra_: that is what i got when I flashed with --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed [11:34] yes, because thats the latest [11:34] read the backlog rtm will still take a while [11:35] about 45min to 1h after the rootfs has built it becomes a system image ... for mako ... [11:35] then it takes another 30min or so for krillin [11:36] aaadn ... #8 for mako just showed up [11:36] * sil2100 lunch o/ [11:36] *aaand even [11:36] err [11:36] #9 for mako [11:36] bzoltan, if you test on mako, you can now flash again [11:37] ogra_: nice, the 9 is coming [11:37] :) [11:40] is jibel around? [11:40] or, who can I contact for QA sign off? [11:50] asac`, looks like rtm #9 for krillin is ready ... happy testing [11:51] psivaa, ^^^ [11:52] psivaa, also one mako doesnt seem to be so happy in rtm testing [11:52] http://ci.ubuntu.com/smokeng/utopic/touch_stable/mako/20140827%20%3F/9984/ [11:53] looks like a bzr ssh issue on the server or so [11:54] ogra_: yea, i restarted a few of those bzr ssh ones. let me take a look at this [11:54] and will kick the krillin off now [11:54] default and install-and-boot seems ot have failed on one device ... funnily other devices (or at least one) seems to run its tests just fine [11:55] the versioning on the dashboard seems to have been messed up by that appraently [11:59] ogra_: yes, i dash_ignored the touch ones, not touch_stable jobs. done and restarted those jobs too. things should look ok in a little bit [12:02] ogra_: sil2100: so the lp:ubuntu-clock-app bzr versioning wasn't fixed in 210? [12:03] sil2100: hmmm so it looks like the current rtm image might of got in some of the fixes from the ubuntu line a lot of the issues I was having are no longer affecting me, but it might be the unity8 silo I'm testing that is making it all smoother ;) I'll keep an eye on things and let you know though [12:07] hmm weird.. http://q-jenkins.ubuntu-ci:8080/job/utopic-touch-mako-smoke-daily/786/console failed on clock click setup [12:07] bzoltan: hmm, it looks like webbrowser would need similar unblocking, now that didn't get in to #209 [12:08] Mirv: hmm... yes, it was cjwatson who unblocked the uitk [12:09] bzoltan: I'm asking generally over there, since I believe he has finally went to sleep === MacSlow|lunch is now known as MacSlow [12:34] psivaa, it wass supposed to ... we only built the images for this issue [12:34] and looking it seems that 210 is just fine on both arches [12:35] err, sorry 9 rtm that is === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cprov | CI Train Status: #203 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: queuebot has temporarily lost the ability to read from the spreadsheet. This means you must manually ping trainguards when requesting a silo or wanting a silo to be published. === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): Ursinha | CI Train Status: #203 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: queuebot has temporarily lost the ability to read from the spreadsheet. This means you must manually ping trainguards when requesting a silo or wanting a silo to be published. [13:33] sil2100: looks like a failure occured publishing rtm silo 3, do I just need to resync trunk with telephony-service branch? looks like a new version got released in ubuntu since the silo request [13:34] bfiller: what failure happened? [13:34] Something is missing? [13:34] sil2100: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-003 [13:35] Let me take a look at that [13:36] bfiller: you used separate rtm branches for those, right? [13:36] Like, bzr branches [13:36] yay, I'll keep making edits to the comments until it gets assigned :-P [13:36] err, description [13:37] sergiusens: ;) One moment [13:38] sil2100: it was more of a joke :-) [13:38] sil2100: yes [13:38] sil2100: I still want a silo though :-P [13:38] sil2100: there are separate rtm branches [13:38] bfiller: so, yeah, it seems that there was some release happening to ubuntu-rtm directly... most probably re-syncing that branch with trunk should do it [13:38] bfiller: and then just rebuilding telephony-service should do the trick [13:39] sil2100: ok, will do [13:39] sergiusens: of course, you want an RTM counterpart as well, right? :) [13:41] sergiusens: both assigned! [13:56] Wellark: https://code.launchpad.net/~jpakkane/thumbnailer/embedded-album-art/+merge/231207 not approved [13:56] Wellark: unping, wrong To: [13:56] thostr_, your silos are being tested [13:58] thostr_, 007 and 008 [14:00] sil2100, please make sure to let people know about the trello board today [14:00] sil2100, and update the spreadsheet with a link [14:06] robru, hey with some change that you did recently for citrain device-upgrade, I have to apt update before I can install unity8-autopilot [14:07] robru, otherwise I get: http://pastebin.ubuntu.com/8159757/ [14:07] robru, is that expected/feature/bug? [14:11] brendand: sure thing :) [14:13] thostr_, there is this trello board we have as well: https://trello.com/b/AE3swczu/silo-testing [14:13] thostr_, for more detail status on what we're doing [14:20] brendand: ah, good to know. wasn't aware of this, was waiting for a ping as described by asac [14:21] thostr_, yes - and sorry about that not happening [14:21] brendand: can you try to do those pings? helps a lot keeping transparency up etc. [14:21] thanks [14:21] at least initially until folks have gotten a feel how this works and that they won't be forgotten :P [14:22] asac`, yes i think it's okay to do initially [14:23] asac`, but as with all manual processes it can be forgotten so i do feel it's a bit error prone [14:23] asac`, but until we find a better way [14:24] brendand: well, what i learned is that this is just hard to start; after peer encouraging folks for a few days it will become natural procedure [14:24] and wont be an issue at all [14:24] heh [14:24] anyway, yes, there can be misses, and hence i encouraged folks to ask early [14:24] rather than wait if they feel something isnt moving [14:25] asac`, yes people should be able to pull the info too [14:25] asac`, i feel the trello board once everyone is aware of it will serve that purpose best [14:25] right [14:25] asac`, but we can do proactive pings to landers as well [14:26] trainguards: can I get a silo for line 55 of the spreadsheet? It would help reviewers to have easier testing [14:26] brendand: can the trello board show who is in charge of coordinating in case there are questions? [14:26] asac`, yeah absolutely [14:27] mterry: you have not marked it as ready [14:27] Mirv, thanks, fixed [14:28]