[02:03] <imgbot> [03:23] <imgbot> [03:23] <imgbot> [06:35] <robru> Mirv: good god qtbase takes forever to build. remind me never to use that for testing citrain changes ever again ;-)
[06:36] <Mirv> robru: it might be just the worst possible choice, yes :)
[06:36] <Mirv> robru: oxide-qt might be slightly worse still, try that next time ;)
[06:37] <Mirv> robru: armhf build of qtbase will take around 4.5 hours
[06:37] <robru> Mirv: oh god
[06:37] <robru> ok, cancelling ;-)
[06:38] <Mirv> excellent choice!
[06:39] <robru> Mirv: so I didn't deploy anything to production yet, but when my shift starts monday morning I'm gonna deploy a ton of fun new stuff ;-
[06:39] <robru> ;-)
[06:48] <Mirv> robru: exciting times! ;)
[08:06] <sil2100> o/
[08:07] <sil2100> ogra_: hey! The landing gates are still closed?
[08:08] <Mirv> sil2100: o/
[08:08] <Mirv> sil2100: yes
[08:08] <sil2100> Mirv: o/
[08:08] <Mirv> sil2100: just catch up with emails, no hurry :)
[08:09] <Mirv> the gates are even tighter closed now!
[08:09]  * sil2100 is worried about this e-mail catch-up
[08:09] <sil2100> Need to wait for all the filters to do their magic
[08:09] <Mirv> sil2100: well you know, once you catch up with the most important lists, you've the big picture anyhow
[08:09] <Mirv> well that too
[08:10] <Mirv> sil2100: refreshed?
[08:10] <Mirv> sil2100: ogra_ can offer you some landing tea he started brewing last week
[08:11] <sil2100> Mirv: a little bit, yes :) Although I just recently understood that 2-months of vacation when one was a student was the perfect length for holidays!
[08:12] <Mirv> sil2100: yes, exactly :) although most of those I spent doing summer work to have some experience + money.. so it never quite works "optimally" :)
[08:12] <Mirv> there was this one summer though, no work, just play, 3-4 months... phew
[08:13] <sil2100> Mirv, robru: any news of the spreadsheet replacement?
[08:14] <Mirv> I haven't heard. robru keeps on cleaning CI Train code though (next big deployment when he wakes up in 9h)
[08:17] <sil2100> Thunderbird is slow with it's filters, for now it's 3k of unfiltered e-mail
[08:20]  * popey hands sil2100  some procmail rules
[08:20] <popey> welcome back
[08:20] <sil2100> popey: o/
[08:38] <tvoss> o/
[08:41] <Mirv> tvoss: o/
[08:46] <sil2100> The filters still didn't do their job, but I see news of a second image promotion last week
[08:46] <sil2100> Good job everyone!
[08:49] <sil2100> ogra_: so the MilestoneSchedule has been +1'ed by olli and the product team?
[08:49] <sil2100> That would be great
[08:55] <ogra_> sil2100, well, we are running by it  ... not sure it needs additional +1 ing :)
[08:55] <sil2100> As long as people were properly informed, I guess it's ok - and we're anyway concentrating on a limited list of top-blockers anyway
[08:55] <sil2100> -anyway
[08:56] <ogra_> right, 3 or 4 this week, the remaining of the 6 next week
[08:56] <brendand> ogra_, sil2100 - i'm off today btw, so won't attend the landing meeting
[08:57] <sil2100> Actually I see this plan got a +1 from Pat so that's all I wanted ;)
[08:57] <sil2100> brendand: ok! Do you know who will be available from QA today for EU? Since Dave is on holidays too, right?
[08:57] <ogra_> brendand, yeah, i know
[08:57] <ogra_> sil2100, jibel takes over
[08:59] <brendand> sil2100, not a lot of people :)
[08:59] <brendand> sil2100, jibel, vrruiz
[08:59] <sil2100> brendand, ogra_: thanks ;)
[08:59] <brendand> sil2100, om26er later
[09:00] <sil2100> Well, we only target topblockers, so I suppose there won't be too many silos
[09:00] <ogra_> right
[09:00] <ogra_> and we are only letting 4 of them in anyway
[09:01] <ogra_> (and the fs corruption one will actually be a *lot* of fun to test :P (not sure how to test it at all))
[09:02] <sil2100> ogra_: but does it have a fix already?
[09:03] <sil2100> I didn't see any merges associated with it, but on the other hand not sure if it has any bzr-controllable projects related
[09:12] <ogra_> sil2100, most of the bits are in place, it is in android (recovery), initramfs-tools ... and adbd
[09:13] <ogra_> as i said, fun to test :)
[09:16] <jibel> sil2100, and rhuddie
[09:16] <rhuddie> jibel, hey. just catching up on what
[09:16] <rhuddie> I am doing this week :)
[09:31] <Mirv> sil2100: meeting :)
[09:31] <Mirv> sil2100: there you are..
[09:34] <Mirv> jibel: rhuddie does either of you want to join follow https://plus.google.com/hangouts/_/canonical.com/landing-meeting ?
[09:34] <jibel> Mirv, joining
[09:34] <Mirv> excellent. ogra_ is currently just summing up latest things to sil2100
[10:11] <sil2100> ogra_, Mirv: btw. do you guys know if all the CPU-hogger bugs have been fixed? i.e. the location-service spinning 100% CPU etc.?
[10:15] <Mirv>  sil2100: in theory yes, unless something yet uncovered lurks somewhere
[10:16] <sil2100> tvoss: ping!
[10:16] <tvoss> sil2100, hey there
[10:17] <tvoss> sil2100, for the cpu hogging: we still haven't identified the root cause for dbus-daemon spinning.
[10:17] <sil2100> tvoss: ok, so this one thing still remains - but it's not happening too frequently, right?
[10:17] <sil2100> tvoss: since I don't see it as a topblocker right now
[10:17] <tvoss> sil2100, nope, that's part of the problem in tracking it down :)
[10:18] <sil2100> tvoss: ok, thanks o/
[10:18] <tvoss> sil2100, o/
[10:22] <seb128> speaking of cpu hogging, I had a few weird issues this w.e on the phone (running current rtm image)
[10:22] <seb128> like it wouldn't turn out of suspend
[10:22] <seb128> I hammered a bit the power button and got the reboot dialog but the buttons were not reacting to click
[10:22] <seb128> and the screen would turn off again after like 10 seconds
[10:23] <seb128> it sort of acted like it was busy and slooow to react to action
[10:23] <seb128> waiting some 30 seconds I managed to get the unlock/reboot
[10:23] <seb128> did that like 2 or 3 time over the w.e, first time I've such issues
[10:24] <seb128> did anyone experience/report issues like that before?
[10:27] <Mirv> jibel: so, it'd be useful to start testing networking in general for bug #1357321 using the rtm-022 silo that fixes 3G usage for at least scopes image loading.
[10:28] <Mirv> jibel: I've just added a new section "Testing networking code in Qt Base" to the test plan, summarizing some of the tips discussed in the bug report
[10:28] <Mirv> I should have a new build also by EOD, since Lorn was still awake pushing fixes and they may again fix remaining unit tests issues
[10:29] <Mirv> and if not all unit tests are fixed, I'll disable them again and build a newer to-be-tested build
[10:35] <Mirv> I had forgotten I already had a test silo from last week, I don't need three silos..
[11:37] <jibel> Mirv, rvr will start testing silo 22.
[11:38] <ogra_> seb128, well, you might have hit exactly the bug sil2100 was mentioning
[11:38] <ogra_> there is another one where the UI stops taking input completely
[11:49] <Mirv> jibel: rvr: ok. I just pushed the next build and explaining in the bug report.
[11:54] <Mirv> cihelp jenkins is trying to erronously fetch upstream sources with wrong url. it should first check whether the sources are available in the archives like they now already are https://code.launchpad.net/~bzoltan/kubuntu-packaging/qt5-qmake-cross-armhf/+merge/241568
[11:54] <Mirv> and the url is wrong because the orig tarball has dfsg changes
[11:56] <Mirv> note that the Qt jenkins runs are mostly done to get code coverage numbers from what I've understood, since all the unit tests are run at the build time anyway
[12:10] <bzoltan> Mirv:  geez, what is that ^
[12:20] <Mirv> bzoltan: you being too hasty :) I was going to run the watch_only build at the right moment. you're not supposed to run "real" build over there.
[12:21] <bzoltan> Mirv:  ahh... I am sorry dude
[12:22] <Mirv> bzoltan: no problem. CI Train does the correct thing now even with you commanding it to build it "normally" - it actually just watches it, and now it's watchable as it's Published instead of Pending
[12:27] <sil2100> Phew, almost up-to-date with e-mail
[12:27] <sil2100> Time for lunch o/
[12:35] <rvr> Mirv: Hi. I'm trying to reproduce "video scope fails when using only 3G" without installing silo packages: only 3G connection activated, cache directory deleted, go to video scope and pull to refresh. Result: it loads the images.
[12:42] <Mirv> rvr: hmm, maybe that is not completely enough to see the problem. can you try rebooting with wifi disabled while I try to reproduce the problem again?
[12:43] <rvr> Mirv: I rebooted the phone with wifi disabled, and removed the cache before rebooting and after too.
[12:44] <ogra_> oh, damn
[12:45]  * ogra_ forgot to start an image build ... 
[12:45] <ogra_> let me do that now then :P
[12:48] <imgbot> [12:53] <Mirv> rvr: I did not initially manage to reproduce the problem after downgrading, but now again I managed. the test case needs more exact steps and I'm not sure yet of the steps.
[12:53] <Mirv> rvr: try 1. boot with 3g + wifi enabled, 2. disable wifi 3. rm -rf .cache/unity8-dash 4. go to video scope and refresh
[12:54] <rvr> Mirv: Checking
[13:08] <Mirv> I'd really like know something _else_ than the scopes that misbehave. messing with the scopes' cache and updating them seems always a bit hit and miss
[13:17] <Mirv> updated the test plan, it seemed I could reproduct this procedure and then see it fixed after updating.
[13:24] <rvr> I could reproduce it once
[13:25] <rvr> Problem that I have is data connection seems to be flaky here
[13:28] <Mirv> rvr: flaky scopes + flaky data connection makes for hard testing :)
[13:29] <rvr> Meh, the images load almost all the times
[13:34] <Saviq> trainguards ↑ please :)
[13:44] <Mirv> Saviq: done.
[13:45] <Saviq> Mirv, thank you
[14:00] <rvr> Mirv: I tested in another room with better data connection, and haven't been able to reproduce the problem :(
[14:01] <rvr> Mirv: I'll begin testing the silo, anyway
[14:03] <imgbot> [14:03] <imgbot> [14:11] <jibel> silo 3 contains also a fix for bug 1389767. I thought it was clearly said only topblockers? did some one accepted this fix?
[14:12] <seb128> jibel, pat said it was ok to land the other day iirc
[14:12] <Mirv> rvr: ok :( note vrtm~4 will be there to update to now in around 1h
[14:13] <seb128> jibel, http://irclogs.ubuntu.com/2014/11/12/%23ubuntu-touch.html#t15:44
[14:13] <Mirv> om26er: do you have any tips to rvr on how to best reproduce the original problem in bug #1357321?
[14:14] <rvr> Mirv: So, do silo packages will be updated soon? Then better to wait to test those, right?
[14:15] <ogra_> jibel, nothing but the provided list lands ... but things should go into silos and be signed off
[14:16] <jibel> ogra_, it's in the same silo than topblocker bug 1336715. So we either land both or none
[14:16] <ogra_> none then ... it needs to be split in two
[14:16] <plars> did something ugly happen with the mako image recently? all our makos in the lab are unresponsive right now, and even having trouble coming back with the relays
[14:16] <jibel> seb128, ^^
[14:17] <ogra_> plars, we noticed that in todays landing meeting ...
[14:17] <ogra_> psivaa, wanted to inspect that ... but if he didnt tell you anything i guess he didnt find anything either
[14:17] <seb128> jibel, ogra_, shrugh, I've nothing to do with that, Pat said it was ok to land if it's not talk to him not me
[14:17] <ogra_> theoretically there should be nothing wrong with the images
[14:17] <seb128> or land none
[14:17] <ogra_> seb128, not pats decision (nor mine)
[14:18] <seb128> ogra_, not mine either
[14:18] <ogra_> i'm just the messenger
[14:18] <seb128> why is Pat saying ok to things if he's not allowed to?
[14:18] <seb128> anyway, politics
[14:19] <seb128> as far as I'm concerned feel free to not land any of the fixes or do whatever suits the rules-of-the-day best
[14:19] <ogra_> i'll bring it up at the bug review meeting
[14:19] <psivaa> ogra_: plars: image 23 was not flashed on the devices that are being offline. and image 22 was fine. i dont *think we have any issue with the images
[14:20] <plars> psivaa: I'm almost wondering if something that drained the power completely
[14:21] <seb128> kenvandine, hey
[14:22] <seb128> kenvandine, seems like you need to redo silo 3 without the title fix, jibel and ogra_ don't like having 2 bugs fixed in one landing
[14:22] <ogra_> lol
[14:22] <kenvandine> bummer... pat told me to include it
[14:22] <kenvandine> i can remove it
[14:22] <ogra_> not my choice, really
[14:22] <jibel> seb128, it is not a matter of me liking or not liking. The rule is only topblockers
[14:22] <ogra_> kenvandine, when did he tell you ...
[14:22] <seb128> jibel, why is Pat approving things then?.
[14:22] <kenvandine> jibel, last tuesday
[14:23] <ogra_> the plans of all of us were changed friday late afternoon
[14:23] <kenvandine> it's been tehre a week
[14:23] <kenvandine> there
[14:23] <jibel> seb128, I don't know. I don't see any comment from him on the bug report, his only action is to downgreade the priority from critical to medium
[14:23] <kenvandine> he said to go ahead and land that too
[14:23] <ogra_> lets wait for pat  and olli and see what we can do here ... before you invest huge amounts of work into splitting that
[14:24] <kenvandine> jibel, it was on the wish list for rtm and they approved it
[14:24] <kenvandine> he told me to go ahead and land it too
[14:24] <seb128> jibel, shrug, I pointed the IRC log, no it was not on the bug comment
[14:24] <seb128> jibel, http://irclogs.ubuntu.com/2014/11/12/%23ubuntu-touch.html#t15:44 in case you didn't see it before
[14:24] <kenvandine> jibel, someone from QA verified it with pat as well
[14:25] <ogra_> the rules changed :/
[14:25] <sil2100> ogra_, seb128: well, I just know that Pat mentioned in his e-mail that we only can land topblocker fixes
[14:25] <sil2100> kenvandine: when did that happen?
[14:25] <kenvandine> sil2100, ogra_: yeah, this was expected to land before the last image
[14:25] <kenvandine> sil2100, that was tuesday i think
[14:25] <seb128> wednesday
[14:25] <sil2100> Ok, then we need to split it out... there were some top-management decisions made
[14:25] <kenvandine> it just took ages for qa verification
[14:26] <kenvandine> yeah
[14:26] <jibel> seb128, I saw the link. But I think you all received the list of 7 bugs to accept this week too
[14:26] <popey> bfiller: I flash my phone clean last week and added google accounts to it, I'm seeing no contacts synced in the contacts all at all...
[14:26] <popey> bfiller: i have the tickbox ticked in my google accounts
[14:26] <seb128> jibel, I'm unsure what do think when top managers give different instructions via IRC and emails, but whatever
[14:27] <ogra_> kenvandine, seb128, we'll have a bug review meeting later today with pat and olli, lets see what they say ... worst case you need to unbundle it tomorrow ...
[14:27] <kenvandine> jibel, this was meant to land in last thursdays image
[14:28] <bfiller> popey: are you on wifi?
[14:28] <jibel> kenvandine, and it missed the window. as other apps / fixes did. This is something to discuss with the management. If they tell us to accept this fix, I'm happy to continue with silo 3 as it is now.
[14:28] <popey> bfiller: yes
[14:28] <popey> bfiller: want me to file a bug and get logs?
[14:29] <bfiller> popey: yeah, specifically .cache/upstart/sync-monitor.log
[14:29] <kenvandine> jibel, lets see what it says
[14:29] <bfiller> renatu: ^^^^
[14:29] <ogra_> jibel, right, we need input from olli and pat here
[14:29] <popey> bfiller: what do you want the bug filed against?
[14:29] <bfiller> popey: were you prompted when you started address-book app to create a google account?
[14:29] <bfiller> popey: sync-monitor
[14:30] <popey> bfiller: i think i had already setup my google account before I opened address-book
[14:31] <renatu> popey, does the sync button appear on the address-book-app header?
[14:32] <popey> renatu: http://popey.mooo.com/screenshots/device-2014-11-17-143151.png that button next to search?
[14:32] <renatu> popey, yes, whats happen if you hit it?
[14:32] <renatu> popey, please send me you sync-monitor log file
[14:32] <popey> it greys out
[14:33] <Mirv> rvr: yes, maybe better at this point to wait. I
[14:33] <renatu> syncing
[14:33] <popey> do you want all of the zipped ones renatu
[14:33] <popey> because the latest one is pretty short
[14:33] <renatu> could you paste the last one
[14:33] <popey> http://paste.ubuntu.com/9057008/
[14:33] <Mirv> rvr: 'd estimate the armhf packages would be published to the PPA archive in around 40mins or so. but indeed the packages still aren't final since we're waiting/hoping for more unit test fixes, but it'd be good to start getting idea that at least there wouldn't be regressions.
[14:34] <renatu> popey, yes this looks ok, you should get your contacts now
[14:34] <renatu> popey, yeah I will need to old ones
[14:34] <popey> i hit refresh 30 mins ago
[14:35] <popey> hah, now they appear!
[14:35]  * popey suspects renatu has root on my phone
[14:35] <renatu> :D
[14:35] <popey> do you still need the logs? seems to be okay now I pressed the damm button
[14:36] <renatu> popey, yes please report a bug, we need to investigate why this does not sync when you create the account
[14:36] <renatu> popey, btw did you create the account after flashing it?
[14:36] <renatu> popey, or the account was already there
[14:37] <popey> renatu: it was a --wipe flash, so there were no accounts, I had to create them
[14:37] <rvr> Mirv: I cannot reproduce the bug with current silo, either ;)
[14:37] <renatu> popey, did you created the account on wifi or 3g?
[14:38] <Mirv> rvr: so, you agree that the PPA may definitely do something. great! :)
[14:38] <popey> probably wifi, i rarely leave the house ☻
[14:40] <rvr> Mirv: As I haven't been able to reproduce it without the silo, right now I agree that the PPA at least doesn't break that :PP
[14:41] <renatu> popey, ok I will need to investigate it to understand whats happen, please report a bug and if possible send me your log files
[14:42] <popey> renatu: https://bugs.launchpad.net/ubuntu/+source/sync-monitor/+bug/1393433 has the full log attached
[14:42] <renatu> popey, thanks
[14:42] <kgunn> Mirv: sil2100 so what is the current thinking, that we are going to have QA test the Qnam patchset and potentially land ? or no landing until we fix the unit tests ?
[14:42] <popey> np
[14:42] <ogra_> sil2100, FYI https://code.launchpad.net/~canonical-platform-qa/camera-app/fix-ap-tests/+merge/241965
[14:43] <Mirv> rvr: yeah. if you read the bug origins, you'll notice that people haven't ever had a very specific test case other than "unoptimal behavior". then the first fix proposals broke more things and there were messaging about that, and now the latest fixes bring it back to that now the original problem would be testable, as soon as a proper test ase would be there.
[14:43] <sil2100> kgunn: so, currently we asked QA to start the testing now, but I would prefer not to land it before the unit tests are fixed - but if we don't make it in time, I would let it pass through the gates anyway
[14:43] <Mirv> kgunn: well first of all we'd need a good test case that actually shows the problem. rvr for example has problems reproducing the original problem, partially because the scopes themelves are flaky.
[14:45] <kgunn> ok, sil2100 i agree, i would rather withhold landing until the unit tests pass...seems there are so many in qt, does anyone really know if it's even safe to
[14:45] <kgunn> let it pass at all?
[14:45] <rvr> Mirv: Ack
[14:45] <kgunn> (e.g. if we run out of time)
[14:46] <sil2100> kgunn: all seems to work ok from the user POV and from what Mirv mentioned the unit tests didn't really test much before in the past because things were anyway b0rken, so it's not such a big deal... but the very thought of releasing something with disabled unit tests sounds a bit juvenile
[14:47] <kgunn> right
[14:47] <kgunn> did anyone double check what lorn said about them passing locally ?
[14:47] <Mirv> kgunn: sil2100: even with unit tests passing, we'd need a better test case for the problem. I've done my best at https://wiki.ubuntu.com/Process/Merges/TestPlans/Qt#Testing_networking_code_in_Qt_Base but rvr still doesn't succeed in reliably reproducing the actual problem without the PPA so he could validate the PPA fixes the issue
[14:48] <kgunn> Mirv: sil2100 i know om26er was able to repro quite easily
[14:48] <kgunn> as he was kind enough to test maybe the 2nd or 3rd ppa we had
[14:49] <kgunn> ...again, did anyone build/run unit tests locally ? i see lorn said they were passing on his phone
[14:49] <Mirv> kgunn: note that there was intermediate problem with the earlier version of the fix, and on the bug report he mostly reports he was reliably able to reproduce the regression in the earlier fix, not that he could reliably reproduce the originally reported bug.
[14:49] <om26er> sil2100, yes, I faced the disconnect issue
[14:49] <Mirv> om26er: ^ the disconnect issue was the regression, not the original problem
[14:49] <rvr> om26er: Do you remember the steps required to reproduce the problem?
[14:49] <kgunn> Mirv: ah, i see...right...regression vs original roaming issue
[14:49] <om26er> Mirv, yes and the original bug where I don't have thumbnails in remote scopes over 3G
[14:49] <om26er> I have seen that forever.
[14:50] <Mirv> kgunn: no I haven't tried locally, I guess it'd need a full build on a phone. it's understandable though, since the remaining unit test failures are likely because network-manager is tried to be used from Qt while builders don't have network-manager installed. earlier there was the generic plugin in use by unit test that didn't interact with network manager.
[14:50] <rvr> om26er: I'm not able to reproduce it with the test case in the wiki
[14:51] <Mirv> om26er: can you then guide rvr better to reproduce the original problem, and maybe update the test case https://wiki.ubuntu.com/Process/Merges/TestPlans/Qt#Testing_networking_code_in_Qt_Base to be something that is really step-by-step?
[14:51] <kgunn> om26er: or...even test the latest ppa :) associated with solving that bug
[14:52] <kgunn> https://bugs.launchpad.net/indicator-network/+bug/1336715
[14:52] <kgunn> oops not that one
[14:52]  * Mirv launches one build in the experimental PPA with network-manager in build dependencies... that might get better unit test results
[14:52] <ogra_> we want that fixed too though :)
[14:52] <kgunn> https://bugs.launchpad.net/savilerow/+bug/1357321
[14:52] <kgunn> Mirv: ta
[15:13] <rvr> Mirv, kgunn: om26er is not able to reproduce the bug anymore in 161
[15:13] <ogra_> heh
[15:15] <sil2100> ;/
[15:15] <om26er> could be the network status fix, fixed this issue as well.
[15:16] <Saviq> sil2100, hmm, no descriptions in citrain dashboard?
[15:16] <sil2100> Saviq: uh oh!
[15:16] <om26er> citrain says: /usr/bin/citrain: 45: .: Can't open /usr/share/phabletutils/shell-adb-common.sh
[15:16] <om26er> help ?
[15:16] <sil2100> SOmething must have broken it
[15:16] <Saviq> om26er, apt-cache policy phablet-tools
[15:16] <Saviq> ?
[15:16] <ogra_> looks a lot cleaner at least :P
[15:17] <om26er> Saviq, not installed
[15:17] <Saviq> om26er, sounds like phablet-tools-citrain's missing a runtime dep on phablet-tools
[15:17] <ogra_> file a bug please
[15:17]  * Saviq clicked /usr/share/... from om26er... firefox landed me in http://www.usr.com/share/phabletutils/shell-adb-common.sh
[15:17] <Saviq> WTF
[15:17] <sil2100> Saviq: checking if your big description b0rk it (just in case)
[15:18] <Saviq> BIG? that's a big description?
[15:18] <sil2100> But it still seems missing...
[15:18]  * sil2100 investigates
[15:19] <sil2100> Damn, there's a lot of errors on this page, but not sure if those aren't some old ones
[15:22] <Mirv> rvr: om26er: :/ which network status fix?
[15:26] <om26er> Mirv, bug 1386109 but I might be wrong, its a guess.
[15:31] <rvr> Mirv: What do you think?
[15:32] <Mirv> rvr: I don't know. I jumped in only when there was a supposed fix, and then battled with getting the regression going away. I thought from the start that the scopes are a bit hard way to reproducing the original problem, and again today thought that I was able to see the problem (with the now updated test case in the wiki) - I rebooted twice with the old version, with wifi on, did the test and it failed. then updated to the PPA and it didn't fail 
[15:32] <jhodapp> sil2100, can you please reconfigure vivid silo 1
[15:33] <sil2100> jhodapp: sure, what changed?
[15:33] <jhodapp> sil2100, added the qtubuntu-media MR to it
[15:33] <jhodapp> sil2100, but go ahead and rebuild everything
[15:33] <Mirv> rvr: I'll let QA decide what to do with the original bug an supposed fix, while I try concentrate on getting the unit tests situation clear for the possibility of landing the new network manager backend that actually works unlike the current one.
[15:33] <Mirv> if nothing else, Qt 5.4 will have super improved network manager bearer backend thanks to Lorn's work :)
[15:35] <sil2100> jhodapp: reconfigured
[15:35] <jhodapp> sil2100, thanks
[15:36] <Mirv> mzanetti: if there's a possibility the current 3G connection scopes problem is somehow gone/workarounded already, can you give kgunn/om26er/rvr some sort of idea what _other_ problems we may be currently facing with the broken network manager bearer plugin that we're currently using, or can we just do without it?
[15:37] <Mirv> s/without it/without the new fixed backend/
[15:38] <Mirv> I never really understood how the problem lead to the images not loading but web otherwise working, so the bug description would enjoy more accurate wording too
[15:39] <mzanetti> Mirv: I couldn't reproduce the roaming issue any more with your ppa
[15:39] <mzanetti> Mirv: on details about other issues I'd have to redirect you to lpotter
[15:39] <Mirv> mzanetti: the thing is that om26er and rvr now claim they can't reproduce it anymore without the PPA either
[15:39] <rvr> mzanetti: And without the silo?
[15:40] <mzanetti> need to test again to be sure
[15:40] <rvr> mzanetti: om26er and me can't reproduce it in 161
[15:41] <om26er> mzanetti, yes, I am not able to reproduce that issue today with 3G.
[15:42] <Mirv> kgunn: om26er rvr: I finished one more build and updated https://bugs.launchpad.net/savilerow/+bug/1357321/comments/87 - feel free to find ways to help with a) test case, b) validating what om26er/rvr are seeing without the PPA, c) bug description about what was the original problem exactly and how it related to us needing the fixed Network Manager backend... phew..
[15:42] <ogra_> Mirv, with or without silo ... we are sure the fix is the right thing to do in general ... no ?
[15:44] <Mirv> ogra_: well I guess a working NM backend in Qt sounds good, so that Qt's network status information would reflect what's actually happening in network manager. so in general yes it's the correct thing to fix, but I don't know what are the problems we're actually facing with staying with the current broken backend, if even this problem is gone.
[15:44] <sil2100> Saviq: the dashboard is acting strange, it seems to have problems fetching info from the SS
[15:45] <ogra_> Mirv, right
[15:49] <pmcgowan> ogra_, I thought we decided to land silo 3 as it was to avoid make work
[15:50] <ogra_> pmcgowan, well, i dont know what was decided after the bug meeting on friday
[15:50] <pmcgowan> we discussed here in the channel with brendan
[15:50] <ogra_> all i know is that it was decided that nothing but topblockers can land from now on
[15:51] <ogra_> if we are fine with the bundled silo (which IMHO we should) that needs to be said so :)
[15:51] <pmcgowan> that silo was already tested and just missed the previous deadline
[15:51] <pmcgowan> I am fine to land it
[15:51] <ogra_> me too
[15:51] <ogra_> olli, ?
[15:51] <pmcgowan> he also +1 on fri
[15:51] <ogra_> land it then :)
[15:51] <kenvandine> we need QA to mark it as verified :)
[15:51] <ogra_> sil2100, silo3 can go in once verified
[15:52] <ogra_> seb128, ^^
[15:52] <rvr> rhuddie stopped testing silo 3 until its status was clear
[15:52] <kenvandine> rhuddie, ^^^
[15:53] <pmcgowan> Mirv, if we cannot reproduce that qnetwork issue with the latest NM fixes, we should probably defer that landing
[15:53] <ogra_> we shoulldnt throw it away though
[15:53] <pmcgowan> indeed
[15:54] <ogra_> since we are sure it is the right thing to do
[15:54] <rvr> pmcgowan: ogra_: So do we block silo 22 for now?
[15:55] <pmcgowan> rvr, I would if the symptoms no longer reproduce
[15:55] <olli> yeah
[15:55] <ogra_> rvr, well, unless om26er finds a way to repro the issue i guess we have to
[15:55]  * olli waves goodbye
[15:56] <om26er> ogra_, the issue is: the problem was never difficult to reproduce. The bug was just there, for example opening the Ubuntu Store would not show icons of the apps but today its working just fine.
[15:57] <ogra_> right
[15:57] <om26er> maybe lets ask victorp if its fixed for him as well ?
[15:57] <ogra_> yeah
[15:57] <rhuddie> rvr, kenvandine, jibel, yes. testing on silo 3 was stopped until we had a clear direction.
[15:58] <rvr> rhuddie: Ok, we can test it now "safely" :)
[15:58] <kenvandine> it was stopped for several times last week, never really knew why...
[15:58] <kenvandine> rhuddie, rvr:  thanks
[15:59] <pmcgowan> om26er, iit does seem to be working
[16:00] <rhuddie> kenvandine, rvr, jibel, Ok, I'll start with silo3 again
[16:26] <rhuddie> kenvandine, on silo 3 I am seeing incorrect sync on flight mode state between u-s-s and network indicator. This wasn't mentioned in http://pastebin.ubuntu.com/8967576/
[16:26] <rhuddie> kenvandine, is this still expected?
[16:26] <kenvandine> what do you mean by incorrect?
[16:27] <kenvandine> it still looks a little wonky imo
[16:27] <kenvandine> but the state stays consistent for me
[16:27] <rhuddie> kenvandine, well, u-s-s says flight mode is enabled, but the indicator says it is disabled
[16:29] <kenvandine> that stayed in sync for me when i tested it
[16:29] <rhuddie> kenvandine, it started doing that after a couple of attempts of switching flight mode on/off and unlocking the sim
[16:30] <kenvandine> i didn't do anything with unlocking the sim
[16:30] <kenvandine> so maybe that triggered a problem in the indicator
[16:30] <kenvandine> now i can't install from the silo!
[16:30] <kenvandine> i flashed this morning, so lost the silo
[16:30] <kenvandine> W: Failed to fetch http://ppa.launchpad.net/ci-train-ppa-service/landing-003/ubuntu-rtm/dists/devel/main/binary-armhf/Packages  403  Forbidden
[16:31] <ogra_> i think there was a comment in the bug about the fliht mode switch
[16:31] <ogra_> (and that it is speacial and slower)
[16:31] <cwayne1> ogra_: btw spanish image should now be setup as gated
[16:32] <kenvandine> ogra_, any idea why i'm getting 403 errors from the ppa?
[16:32]  * ogra_ hugs cwayne1 
[16:32] <ogra_> kenvandine, s/devel/14.09/
[16:32] <kenvandine> oh, is the citrain tool broken?
[16:33] <ogra_> kenvandine, LP drawback ... if you use the correct channel and add-apt-repo does the right thing and use the channel name ... LP cant resolve that to 14.09
[16:33] <kenvandine> ah
[16:33] <kenvandine> sigh
[16:33] <kenvandine> i shouldn't have flashed :)
[16:33] <ogra_> iirc cjwatson had opened a bug for that
[16:34] <sil2100> ogra_, pmcgowan: ACK
[16:34] <sil2100> Let me mention that in the landing
[16:34] <sil2100> Although the dashboard seems to be a bit mean today
[16:34] <kenvandine> rhuddie, i toggled it twice, each time it took at least 5 seconds but they stayed in sync
[16:35]  * kenvandine tries a few more times
[16:35] <rhuddie> kenvandine, hmm, it didn't take long for me to see the problem.
[16:35] <kenvandine> rhuddie, i think the switch in the indicator is a little buggy
[16:35] <kenvandine> it moves then moves back
[16:35] <kenvandine> and moves again when the state really changes
[16:35] <rhuddie> yeah I saw that too
[16:35] <cjwatson> ogra_,kenvandine: it's not that it can't resolve it - it shouldn't need to
[16:36] <kenvandine> i'm waiting long enough for the state to really change.. maybe if i rush it :)
[16:36] <cjwatson> ogra_,kenvandine: the problem is that there's a wrong .htaccess somewhere on the server side that's incorrectly denying access
[16:36] <cjwatson> and I keep forgetting to track that down at some point when the right people are around
[16:37] <sil2100> robru: the dashboard seems to have now completely stopped showing silo descriptions
[16:37] <kenvandine> rhuddie, ok, i reproduced that
[16:37] <cjwatson> I didn't file a bug, though I did ask Ted to file one
[16:37] <sil2100> robru: you have any idea what's up? I didn't have time to investigate that properly
[16:38] <kenvandine> rhuddie, but the state is right and staying in sync with what's in settings
[16:38] <kenvandine> the indicator isn't always staying in sync
[16:38] <kenvandine> rhuddie,  but you're right, i didn't hit it until i changed it a few times
[16:39] <kenvandine> i doubt that's a regression, the flight mode switch in indicator-network has been buggy
[16:42] <kenvandine> rhuddie, it's worse without silo 3 :)
[16:42] <kenvandine> so not a regression
[16:42] <kenvandine> got out of sync on the first try for me without the silo
[16:43] <rhuddie> kenvandine, yes. agreed. do we have a bug for the network indicator issue?
[16:46] <kenvandine> rhuddie, not sure, there have been a number of bugs filed related to this
[16:46] <kenvandine> rhuddie, i just tried it in vivid and i can't reproduce it in vivid
[16:46] <kenvandine> so maybe indicator-network or urfkill has a fix in vivid that hasn't been backported yet?
[16:46] <kenvandine> don't know
[16:47] <rhuddie> kenvandine, could you update your testing notes http://pastebin.ubuntu.com/8967576/ to reference the issue?
[16:47] <rhuddie> at least then it is logged with all the other issues
[16:48] <kenvandine> i need to head out for an appointment, lets just reopen the indicato-network rtm task for bug 1336715
[16:48] <kenvandine> or ask dednick to weigh in
[16:48] <kenvandine> dednick, please read the scrollback there
[16:49] <kenvandine> dednick, basically we can still get flight mode out of sync in indicator-network in rtm
[16:49] <kenvandine> but it's only the indicator getting out of sync, settings is staying in sync with the actual state
[16:49] <kenvandine> and i can't reproduce it in vivid
[16:49] <kenvandine> dednick, so maybe indicator-network bug?  do you know if we already have a bug for that?
[16:50]  * kenvandine heads out, bbiab
[16:50] <rsalveti> cjwatson: hey, quick question for you, tried to update the android package, but got stuck in proposed with 'android-emulator/amd64 unsatisfiable Depends: ubuntu-emulator-images'
[16:50] <rsalveti> cjwatson: android-emulator is 'all'
[16:51] <rsalveti> and nothing changed from the previous upload I had
[16:51] <rsalveti> ubuntu-emulator-images is indeed i386 only
[16:51] <rsalveti> which explains the message, but why is that an issue now?
[16:53] <rsalveti> android-emulator is an old transitional package, and can probably be removed if needed
[16:53] <cjwatson> rsalveti: give me a few minutes to investigate
[16:53] <rsalveti> cjwatson: sure, thanks
[16:53] <cjwatson> it might have been forced in before
[16:55] <cjwatson> rsalveti: oh, it would have worked before because architecture-all packages previously only had dependencies checked on i386; now they only have dependencies checked on amd64, to match the nominatedarchindep changes
[16:56] <rsalveti> cjwatson: oh, right then
[16:57] <rsalveti> should I just drop this package then for now? or is there anything else that can be done?
[16:57] <cjwatson> rsalveti: I have told proposed-migration a suitable lie which should make this problem go away
[16:57] <cjwatson> rsalveti: specifically http://bazaar.launchpad.net/~ubuntu-release/britney/britney1-ubuntu/revision/270
[16:57] <rsalveti> oh, cool then
[16:57] <rsalveti> cjwatson: got it, thanks so much
[16:58] <cjwatson> no problem
[17:01] <plars-sprint> ogra_: sil2100: at a sprint this week so I don't know if I'll easily be able to make it to hangouts, but I'll be around on irc mostly so if you need anything please ping me here. We have those makos in a better state now, so I'll have them back up and running jobs soon
[17:02] <sil2100> plars-sprint: ok, so are all those devices up now?
[17:03] <dednick> kenvandine: is this not related to the the battery using libnm directly maybe?
[17:05] <dednick> kenvandine: it's possibly a indicator-network bug. i hanvent seen it out of sync with the wifi settings in uss.
[17:05] <dednick> not since the uss updates anyway
[17:09] <ogra_> popey, soooo ... you can land the music app ... but please well coordinated with QA and the smoke testing guys ;)
[17:10]  * ogra_ just came out of a meeting :)
[17:10] <popey> thanks!
[17:10] <plars-sprint> sil2100: no, but they will be soon, it's mostly just mako and flo that were affected I think. Krillin seems ok
[17:15] <om26er> jdstrand, Hi! regarding silo-002 is any anything using the newly added functionality ?
[17:15] <jdstrand> om26er: no. the stuff to use it is for ota-1, but we want these changes now to avoid a policy recompile as part of ota-1
[17:18] <plars-sprint> psivaa: sil2100: ogra_: to me, it looks like starting with image 132 on mako, it started being uninstallable
[17:18] <bzoltan> sil2100: may i ask for quick silo? I could build a release candidate for the Chinese fellows for early morning tests
[17:18] <plars-sprint> I think I just killed two more devices with the latest, so I'm trying vivid now
[17:19] <plars-sprint> sil2100: wasn't 132 promoted also? that could explain why the latest stable image we flash is also broken
[17:20] <ogra_> plars-sprint, the promoted image was definitely sanity tested on mako
[17:20] <plars-sprint> ogra_: with --bootstrap?
[17:20] <ogra_> plars-sprint, that you would have to ask davmor2 :)
[17:21] <plars-sprint> ogra_: look at 132 in the ci runs, for 3 devices, none of them even booted
[17:22] <plars-sprint> and 134 looks to have the same problem
[17:23]  * ogra_ taps foot waiting for the dashboard 
[17:24] <jdstrand> win 14
[17:25] <jdstrand> meh
[17:27] <ogra_> plars-sprint, well, no android changes and http://people.canonical.com/~ogra/touch-image-stats/rtm/160.changes (132) and http://people.canonical.com/~ogra/touch-image-stats/rtm/161.changes (133) ...
[17:27] <ogra_> plars-sprint, i dont see how anything could have broken it
[17:27] <plars-sprint> ogra_: if not, then we just had a LOT of devices simultaneously fail
[17:27] <plars-sprint> ogra_: what about something that could have broken adbd?
[17:27] <ogra_> nope
[17:28] <plars-sprint> ogra_: the image is booting from the sounds of it, but we don't see it
[17:28] <ogra_> notihing than the above changed last week
[17:28] <ogra_> we were hard frozen from wed. early monring on
[17:28] <plars-sprint> ogra_: I'm flashing vivid on one that just failed twice in a row with the latest rtm, so we'll see what happens
[17:29] <ogra_> k
[17:29] <ogra_> there is really nothing that could have broken it on the image side
[17:33] <plars-sprint> ogra_: yep, confirmed... mako-14 just failed 2 times in a row, (more if you count the previous failures), but with vivid it works fine
[17:33] <ogra_> well, not sure what to say
[17:34] <ogra_> nothing in the image changed that could even remotely cause this
[17:35] <plars-sprint> ogra_: well I know 132 failed, I know the stable image 8 fails, and I know the latest image 134 fails, but vivid works fine. So until it's sorted, we can either test on rtm and watch it kill all the makos, or we can turn that off
[17:35] <ogra_> and i know that davmor2 definitely tested 133
[17:35] <bzoltan> trainguards: could any of you help me out with a vivid silo what would release in 12 hours?
[17:36] <ogra_> plars-sprint, did ubuntu-device-flash get updated on the server or some such ?
[17:36] <plars-sprint> ogra_: not since early last week
[17:36] <plars-sprint> well before this I believe
[17:36] <ogra_> i see there was a landing for it in vivid on thu
[17:36] <ogra_> but that should not even touch touch
[17:37] <ogra_> (was for ubuntu-core)
[17:37] <ogra_> but that would be my only explanation
[17:38] <plars-sprint> well, on the 13th, but I would think there were tests between that and the one on friday that failed. iirc that one wasn't there early in the day when I looked
[17:38] <robru> bzoltan: what kind of help do you need?
[17:39] <bzoltan> robru: I could use a silo :)
[17:39] <robru> bzoltan: sure, what spreadsheet row?
[17:39] <bzoltan> robru:  56
[17:39] <ogra_> well, it landed in vivid at Thu, 13 Nov 2014 19:10
[17:39] <plars-sprint> davmor2: do you have a working mako at home you could try this with? (flashing latest rtm with --bootstrap)
[17:39] <ogra_> plars-sprint, he is off this week
[17:39] <plars-sprint> sadly, my mako has a busted battery
[17:39] <plars-sprint> ah, someone else in qa then maybe?
[17:39] <ogra_> (half of QA is)
[17:41] <robru> bzoltan: ok you get to be my guinea pig for some changes I just landed in citrain production ;-) https://ci-train.ubuntu.com/job/ubuntu-landing-022-1-build/23/console building with DEBUG enabled!
[17:41] <bzoltan> robru:  wow :) it is a privilege
[17:42] <plars-sprint> sergiusens_: any chance this could be the same issue we saw with krillin last week and the latest ubuntu-device-flash?
[17:42]  * ogra_ feeds bzoltan some carrots and seeds
[17:43]  * bzoltan knows that in some cultures the guinea pig is considered as food
[17:43] <robru> hehee
[17:43] <ogra_> yup, we used to have peruvian colleagues :)
[17:44] <bzoltan> but you are German, right? So I am safe..
[17:44] <ogra_> haha, yeah
[17:44]  * bzoltan lets the bratwursts to be scared
[17:45] <sergiusens_> plars-sprint: which one, sorry, missing context
[17:46] <rhuddie> kenvandine, I will be leaving shortly, but om26er will continue testing on silo 3
[17:46] <plars-sprint> sergiusens_: on mako latest rtm images boot, but can't be seen from adb on mako and flo with the latest ubuntu-device-flash
[17:46] <plars-sprint> sergiusens_: (with --bootstrap)
[17:47] <bzoltan> ogra_:  where do I find the u-s-c logs?
[17:47] <ogra_> bzoltan, i guess in some lightdm log ...
[17:47] <ogra_> bzoltan, best to ask mterry, he knows that bpart of the system in and out
[17:47] <sergiusens_> plars-sprint: hmmm, I didn't change anything... but, rsalveti did the e2fsck stuff get in? plars-sprint can we check it's not stuck on broken fs?
[17:48] <ogra_> sergiusens_, no, it didnt
[17:48] <ogra_> sergiusens_, this is rtm only
[17:48]  * rsalveti reading
[17:48] <bzoltan> ogra_:  there is a unity-system-compositor.log under /var/log/lightdm
[17:48] <rsalveti> oh, yeah, the fsck stuff is vivid only
[17:48] <ogra_> sergiusens_, mvo changed something for ubuntu-core though
[17:48] <rsalveti> not yet fully landed
[17:48] <sergiusens_> rsalveti: did the "bug" fix for recovery make it to rtm?
[17:48] <ogra_> but that also looks unrelated
[17:48] <rsalveti> sergiusens_: not yet
[17:48] <sergiusens_> ogra_: that's harmless
[17:48] <plars-sprint> sergiusens_: I can't physically see the device, but I was told it was sitting at the  "Hi! Welcome to Ubuntu." screen, but we couldn't see them with adb
[17:48] <ogra_> sergiusens_, nope, there were no android uploads to rtm in quite some time
[17:49] <sergiusens_> ogra_: then it's missing the recovery fix; plars-sprint you said you didn't update u-d-f since, right?
[17:49] <ogra_> nor were there any changes to adb or adbd
[17:49] <sergiusens_> plars-sprint: rsalveti I'm referring to the emails we exchanged a while back
[17:49] <plars-sprint> sergiusens_: I'm talking about the s/set_adb_onlock/adb_onlock thing
[17:50] <plars-sprint> sergiusens_: it did get updated the day before, not sure if there was anything that happened in between
[17:50] <ogra_> thats not used yet
[17:50] <sergiusens_> plars-sprint: yes; but you said you rolled back?
[17:50] <ogra_> and wont be til ota-1
[17:50] <sergiusens_> plars-sprint: keep it rolled back until the rtm adb fix makes it to rtm if someone released a device tarball that doesn't really work...
[17:50] <rsalveti> sergiusens_: but I believe that also didn't land on rtm
[17:51] <sergiusens_> rsalveti: ogra_ oh, if nothing landed in rtm it is not that
[17:51] <ogra_> rsalveti, but perhaps in the phablet-tools ppa
[17:51] <ogra_> sergiusens_, right, i was more looking for possible server side issues plars-sprint could have here
[17:51] <sergiusens_> ogra_: no, I'm talking about recovery.img here
[17:51] <ogra_> since there were no actual changes to the image either when the devices started failing
[17:51] <robru> ogra_: where do we find the records for LP rejecting PPA uploads? do we know where the ps-jenkins mail goes?
[17:52] <sergiusens_> ogra_: if none of the adb work entered there, then it's fine; if something slipped in, the all is wrong and the adb fix needs to either go in or rolled out from rtm from recovery.img
[17:52] <ogra_> robru, uh, no, i dont know ... usually it should go to the MP approver, no ?
[17:53] <ogra_> sergiusens_, nothing changed in the images ... we were hard frozen when mako started failing
[17:53] <robru> ogra_: no, not related to MPs.
[17:53] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/rtm/160.changes and http://people.canonical.com/~ogra/touch-image-stats/rtm/161.changes
[17:53] <ogra_> it started failing with the first one ...
[17:53] <sergiusens_> ogra_: mako on rtm?
[17:53] <ogra_> sergiusens_, lol
[17:53] <sergiusens_> ogra_: so krillin is fine and mako isn't?
[17:53] <ogra_> on mako rtm
[17:53] <ogra_> right
[17:54] <sergiusens_> ogra_: this is what happens with $name ^^
[17:54] <plars-sprint> sergiusens_: correct, and I believe flo is broken also
[17:54] <ogra_> :)
[17:54] <sergiusens_> nothing is clear a that point ;-)
[17:54] <plars-sprint> but I haven't checked that one specifically
[17:54] <ogra_> obviously davmor2 was also able to install and test the image before promotion
[17:54] <ogra_> (on mako)
[17:55] <ogra_> and i belive he uses --bootstrap
[17:55] <sergiusens_> plars-sprint: ogra_ so ubuntu-device-flash touch --channel ubuntu-touch/ubuntu-rtm --bootstrap --password 0000 --developer-mode and it doesn't work?
[17:55] <sergiusens_> on mako
[17:55] <ogra_> for plars-sprint it doesnt, right
[17:56] <plars-sprint> sergiusens_: correct, that's producing something to me that I can't adb into
[17:56] <sergiusens_> ogra_: and the e2fsck stuff not the adb work (none of it) has landed in rtm?
[17:56] <sergiusens_> ogra_: adb in the android package
[17:56] <ogra_> sergiusens_, neither has landed
[17:57] <robru> fginther: https://launchpad.net/~ps-jenkins do you have access to ps-jenkins bot mail? can you check for a PPA upload rejection mail?
[17:57] <ogra_> https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-November/thread.html
[17:57] <ogra_> thats all rtm landings
[17:57] <ogra_> for this month
[17:57] <fginther> robru, chcking
[17:57] <robru> fginther: thanks
[17:57] <sergiusens_> ogra_: yeah, for rtm, I don't really trust the tools anymore given all the issues we'd had ;-)
[17:57] <ogra_> last android landing was nov 6th ... for new hybris ... no changes
[17:58] <fginther> robru, can you narrow it down to a package?
[17:58] <ogra_> sergiusens_, thats why i use the rtm-changes ml as master ;)
[17:58] <robru> fginther: qtcreator-plugin-ubuntu from the last few minutes
[17:58] <ogra_> old tools are still most reliable ;)
[17:59] <fginther> robru, I see no upload rejections
[17:59] <robru> bah!
[18:00] <robru> fginther: thanks for looking. figures I'd test this all weekend and then the first production deployment would just explode.
[18:02] <cjwatson> robru: What package name?
[18:03] <cjwatson> Oh you said
[18:03] <sergiusens_> ogra_: rsalveti plars-sprint https://launchpad.net/ubuntu-rtm/+source/android/20141104-2240-0ubuntu2 I just check the orig tarball there and it has the broken adb logic
[18:03] <cjwatson> robru: 2014-11-17 17:44:33 INFO    Failed to parse changes file '/srv/launchpad.net/ppa-queue/incoming/upload-ftp-20141117-174412-014889/~ci-train-ppa-service/ubuntu/landing-022/qtcreator-plugin-ubuntu_3.1.1+15.04.20141117-0ubuntu1_source.changes': GPG verification of /srv
[18:03] <sergiusens_> ogra_: so the changelog is indeed wrong ;-)
[18:03] <cjwatson> /launchpad.net/ppa-queue/incoming/upload-ftp-20141117-174412-014889/~ci-train-ppa-service/ubuntu/landing-022/qtcreator-plugin-ubuntu_3.1.1+15.04.20141117-0ubuntu1_source.changes failed: Verification failed 3 times: ["(7, 9, u'No public key')", "(7, 9, u'No public ke
[18:03] <cjwatson> y')", "(7, 9, u'No public key')"]
[18:03] <cjwatson> robru: i.e. looks like it was unsigned
[18:04] <sergiusens_> ogra_: and you would need this https://code-review.phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=commit;h=ab1d4747d5581cdbbf233eaedbf3e38cf324efef
[18:04] <ogra_> sergiusens_, well, but that landed on the 6th ... images stopped working on the 13th
[18:04] <robru> cjwatson: can this be some kind of temporary glitch? https://ci-train.ubuntu.com/job/ubuntu-landing-022-1-build/23/console shows it being signed and the signature being good
[18:04] <plars-sprint> sergiusens_: ogra_: so I could revert the ubuntu-device-flash again, or we can fix it there.
[18:04] <cjwatson> robru: It's possible.  There have been acceptances since then
[18:04] <cjwatson> The keyserver is occasionally flaky
[18:04] <ogra_> plars-sprint, try it ...
[18:04] <cjwatson> robru: Is it reasonably straightforward for you to retry?
[18:04] <robru> cjwatson: yeah
[18:04] <sergiusens_> ogra_: well I don't know, the code doesn't lie; the broken adb landed in source on Oct 30
[18:05] <ogra_> sergiusens_, right and in binary on nov 6th
[18:05] <ogra_> but images failed only on the 13th+
[18:05] <sergiusens_> ogra_: oh, because plars-sprint told me he'd keep the old u-d-f until further notice
[18:06] <ogra_> sergiusens_, hmm, you held back u-d-f from the PPA ... i wonder if mvo tried to be a good citizen and copied it over after his stuff landed
[18:06] <ogra_> without knowing that he shouldnt
[18:06] <sergiusens_> ogra_: plars-sprint I can disable this with one line removal from u-d-f
[18:06] <sergiusens_> ogra_: I did it; as plars-sprint told me they manually updated u-d-f
[18:06] <ogra_> or plars-sprint can just roll back
[18:06] <plars-sprint> sergiusens_: no, until that fix went in, which it did. I tested it on krillin and thought it had already been tested on mako. So we will revert again. At some point we need the update though because of some further changes you have planned right?
[18:07] <plars-sprint> I'm rolling it back right now
[18:07] <plars-sprint> to 0.4+14.10.20140929-0ubuntu1
[18:07] <ogra_> plars-sprint, right, that requires full coordination actross all images and all devices :)
[18:07] <ogra_> that will be a lot of fun to land :P
[18:07] <sergiusens_> plars-sprint: ogra_ I'll do a revert on u-d-f of the one line rule; it sucks that such a dumb fix can't land in rtm
[18:14] <robru> cjwatson: retried and it worked. thanks for checking
[18:15] <robru> bzoltan: https://launchpadlibrarian.net/190564701/buildlog_ubuntu-vivid-amd64.qtcreator-plugin-ubuntu_3.1.1%2B15.04.20141117-0ubuntu1_FAILEDTOBUILD.txt.gz Error looks like a missing dependency. Did you add a new dependency without adding it to debian/control?
[18:15] <cjwatson> robru: good, sorry for the inconvenience
[18:16] <bzoltan> robru:  No, I do not think so... but let me check what zbenjamin has done ...
[18:17] <bzoltan> zbenjamin:  robru: libudev1
[18:17] <rsalveti> sergiusens_: changelog is fine
[18:18] <rsalveti> sergiusens_: so it's a combination of latest u-d-f and the broken adb logic
[18:18] <rsalveti> that would explain
[18:19] <sergiusens_> rsalveti: yes; and broken telephone (the game) :-)
[18:19] <rsalveti> sergiusens_: yeah, easier to use the older u-d-f until we update android for RTM
[18:20] <rsalveti> indeed annoying
[18:21] <mterry> bzoltan, ogra_: sorry, was afk for gym.  There's a question about usc?
[18:21] <ogra_> mterry, bzoltan was looking for explicit usc logs
[18:21] <bzoltan> mterry:  working out is healthy :)
[18:22] <bzoltan> mterry: since than i figured out the problem
[18:22] <mterry> bzoltan, awesome.  Glad I could help  ;)
[18:22] <bzoltan> mterry:  you guru :)
[18:23] <ogra_> and he doesnt even have long hair and a beard !
[18:24] <ogra_> sil2100, FYI ... i found the ML archive shows the landing mail within minutes *if* you sort by date (there is a selection at the top of the page to sort by thread or date)
[18:24] <sil2100> UUuggh
[18:24] <sil2100> ogra_: ok, thanks!
[18:24] <ogra_> :)
[18:24] <ogra_> by default you indeed get "by thread" ...
[18:25] <sil2100> Yaay, no more waiting for hours \o/
[18:25] <ogra_> yeah
[18:25] <ogra_> worked fine for me last week
[18:25] <bzoltan> robru:  something must have changed in vivid ...
[18:26] <robru> bzoltan: vivid does that ;-)
[18:26] <bzoltan> robru:  it said that "Project ERROR: libudev development package not found" when we do depend on libudev-dev
[18:27] <sil2100> grrr, and now I'm having problems with sending e-mails, wth
[18:27] <robru> bzoltan: maybe the structure of libudev packages changed in vivid? not sure, I'm unfamiliar with udev
[18:27] <bzoltan> robru:  me too
[18:28]  * bzoltan goes and makes a vivid cowbuilder
[18:29] <sil2100> Moo
[18:35] <rsalveti> ogra_: will trigger another vivid image
[18:35] <robru> sil2100: yeah I don't have a clue what's wrong with the dashboard. the spreadsheet doesn't seem to be missing info (the usual cause of missing dashboard info). also the fact that just some work and some don't is bizarre.
[18:36] <ogra_> rsalveti, go wild
[18:36] <rsalveti> ogra_: done :-)
[18:36] <ogra_> :)
[18:38] <imgbot> [18:39] <robru> sil2100: all my troubleshooting skills say "look at the couple silos that do work and compare them to the rest" and I don't see any difference.
[18:39] <sil2100> robru: at first I thought that some description might have caused the issue by having some strange malformed syntax in it, but I think it's not the case
[18:40] <sil2100> robru: my original culprit was the unity8 silo, but all looks ok there
[18:40] <ogra_> https://lists.launchpad.net/ubuntu-phone/msg10521.html
[18:40] <ogra_> hah
[18:40] <ogra_> minutes :)
[18:41] <Saviq> trainguards, I can has silo 14 published, please (/me hates the dashboard for not reading the status out of the SS)
[18:41] <robru> Saviq: please direct your hatred at the spreadsheet. I'm pretty sure it caused WW2 and has been plotting evil schemes ever since.
[18:42] <Saviq> robru, ok /me hates SS then...
[18:42] <Saviq> hmmm
[18:42] <Saviq> I think that should be built into my polish self anyway
[18:42] <ogra_> robru, did you just invoke godwins law here ?
[18:42] <Saviq> </bad nazi joke>
[18:43] <robru> ogra_: well I didn't mention anybody by name...
[18:43] <ogra_> heh
[18:49] <bzoltan> robru:  that error just does not make sense to me ... the libudev-dev package is available in Vivid and according to the logs it is installed to the builder too
[18:50] <sil2100> bzoltan: did you try in a cowbuilder/pbuilder ?
[18:51] <robru> bzoltan: yeah I dunno. hang on I'll hit retry, maybe today is a day for transient issues
[18:56] <bzoltan> robru: it faild on vivid cowbuilder too ...
[18:57] <robru> bzoltan: yeah the retry failed in the ppa as well, same failure
[18:57] <robru> bzoltan: great news, if you reproduced it locally you're one step closer to fixing it ;-)
[18:58] <kenvandine> rvr, any word on silo 3?
[18:58] <kenvandine> ah, he said om26er_
[18:58] <kenvandine> om26er_, any word?
[18:59] <om26er_> kenvandine, I am working on silo2, will work on 3 afterwards. rhuddie was working on it, he went away.
[18:59] <kenvandine> om26er_, ok, thx
[19:00] <bzoltan> robru:  we have this PKGCONFIG += libudev glib-2.0
[19:01] <robru> bzoltan: try libudev1 maybe? that's the binary package name
[19:01] <bzoltan> robru:  hmmm... wait a second... this is the first time we try to land somethinga since qt5.3.2
[19:03] <robru> bzoltan: looks like pitti was the last person to touch systemd in vivid, worst case maybe ask him if anything about libudev changed since utopic
[19:04] <bzoltan> robru:  I am afraid that it is not about libudev ... but about Qt and the pkgconfig of the qtcreator-plugin-ubuntu project
[19:05] <robru> bzoltan: something you can fix? i'm not familiar with any of that stuff ;-)
[19:05] <robru> bzoltan: i'm just glad this issue isn't caused by my new citrain code ;-)
[19:05] <bzoltan> robru:  I will need Mirv for that
[19:05] <bzoltan> robru:  your CI train code is safe here :)
[19:06] <robru> bzoltan: hehe thanks
[19:19] <pmcgowan> ogra_, popey how does music app get silod/tested
[19:20] <ogra_> pmcgowan, i imagine popey gives the click to QA
[19:20] <popey> pmcgowan: I have created a set of manual tests to perform, we have candidate click.
[19:20] <popey> I am happy to throw at QA, but who? some people are on vacation?
[19:20] <pmcgowan> was just trying to figure that out
[19:21] <popey> I want to do a load more testing before giving to QA
[19:21] <popey> intended to hand to QA tomorrow morning, but if someone in US TZ can test on my overnight then that would be preferable.
[19:22] <ogra_> popey, talk to jibel, he should be able to point you at someone
[19:22] <popey> jibel: yo!
[19:23] <pmcgowan> popey, lets get a trello card for it so its queued up
[19:26] <popey> pmcgowan: got a link to the trello board? I don't seem to be subscribed to it.
[19:26] <ogra_>  https://trello.com/b/AE3swczu/silo-testing
[19:27] <pmcgowan> popey, need QA to update it I suspect https://trello.com/b/AE3swczu/silo-testing
[19:29] <pmcgowan> ogra_, you so fast
[19:30] <ogra_> heh
[19:31] <popey> jfunk: are you able to add a trello card to the QA board for testing the music app for me?
[19:33] <jdstrand> olli, pmcgowan: fyi, the apparmor-easyprof-ubuntu changes (rtm silo 002) is awaiting qa signoff. I'm just waiting on that to then coordinate with cwayne to push to rtm
[19:34] <robru> Saviq: well, dashboard seems to be back. I didn't fix anything. I guess it's just a transient issue with google or something. no idea
[19:34] <pmcgowan> jdstrand, looks like om26er_ is testing now
[19:35] <om26er_> pmcgowan, yes, tests are running, taking a long time
[19:35] <jdstrand> ok, cool
[19:35] <pmcgowan> thanks
[19:35] <jdstrand> the apparmor-easyprof-ubuntu image tests takes a while
[19:39] <bzoltan> robru:  The qtc plugin MR got a quick facelift ... somehow the vivid builders have different packages .. .like pkg-config and libglib2.0-dev was missing
[19:39] <bzoltan> robru:  I triggered a new build with debug info
[19:39] <robru> bzoltan: cool thx
[19:50] <jfunk> popey: is it not going to be tested as part of silo?
[19:51] <ogra_> jfunk, clicks are never siloed
[19:51] <ogra_> there were plans at the sprint to make that possible ... but not implemented yet afaik
[19:52] <jfunk> ack
[19:52] <ogra_> for some of the apps we have desktop packages (i.e. gallery9 there we can have debs in silos for testing ... but not for click only ones
[19:52] <jfunk> popey: sure we can do that, when do you need it by?
[19:52] <ogra_> for this milestone would be good
[19:53] <ogra_> (before wed. evening EU TZ)
[19:53] <ogra_> so it gets a week of testing before the golden milestone
[19:53] <ogra_> (like ... enduser testing ... for the weird guy that has 15632 albums of only one artist etc :) )
[19:59] <ogra_> kenvandine, you broke it :P
[20:00] <ogra_> heh, funny seems they all built on all arches ...
[20:01] <ogra_> so the bot lies ...
[20:06] <kenvandine> 2014-11-17 19:57:21,296 ERROR Expected {'indicator-power': set(['12.10.6+15.04.20141103~rtm-0ubuntu1']), 'powerd': set(['0.16+15.04.20141031.2~rtm-0ubuntu1']), 'ubuntu-system-settings': set(['0.3+15.04.20141112.1~rtm-0ubuntu1']), 'upower': set(['0.99.1~rtm-3'])}+[u'upower', u'powerd', u'indicator-power', u'ubuntu-system-settings'] in PPA but found {u'indicator-power': set([u'12.10.6+15.04.20141103~rtm-0ubuntu1']), u'ubuntu-system-settings
[20:06] <kenvandine> ': set([u'0.3+15.04.20141113.1~rtm-0ubuntu1']), u'upower': set([u'0.99.1~rtm-3']), u'powerd': set([u'0.16+15.04.20141031.2~rtm-0ubuntu1'])}. Perhaps uploads failed?
[20:08] <ogra_> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-016/+packages
[20:08] <ogra_> the ppa looks fine
[20:08] <kenvandine> yeah, it does lie :)
[20:08] <imgbot> [20:08] <imgbot> [20:09] <ogra_> rsalveti, ^^^ yours
[20:09] <rsalveti> ogra_: thanks
[20:12] <robru> kenvandine: looks like unexpected version of u-s-s in the ppa...
[20:13] <robru> kenvandine: yeah, your sync attempted to upload 1112.1 but 1113.1 was already in the PPA. I guess you'll need to bump the version manually
[20:14] <robru> kenvandine: easiest thing I guess would be to free the silo and start over in a different silo. then the 1112.1 upload would succeed
[20:14] <robru> kenvandine: either that or change it from a sync silo to a manual source silo and then just do all the uploads yourself with copypackage
[20:16] <robru> kenvandine: ogra_: bot doesnt lie, it's reporting what the build job tells it to. build job failed because the version in the PPA is not the version that the build job uploaded
[20:16] <robru> kenvandine: apologies that raw data structure dump is totally unreadable, I should fix that
[20:19] <kenvandine> robru, i can fix it :)
[20:19] <kenvandine> thx
[20:23] <robru> I gotta grab lunch, please ping me if anything explodes.
[20:28] <popey> jfunk: sorry, was afk
[20:29] <popey> jfunk: ask ogra_ says, asap really. We haven't used silos before for the community click apps. We'd ordinarily just push the click under test to the phone and go through the usual manual tests
[20:30] <popey> jfunk: left a comment on the trello card with the link to the click which needs testing
[20:30] <pmcgowan> popey, seems nuclearbob waslooking for you on that
[20:31] <popey> super
[20:31] <jfunk> popey: ack thx
[20:32] <nuclearbob> popey: do you have the test plan handy?
[20:32] <popey> kinda, working on it right now.
[20:32] <popey> this is a bit new to me ☻
[20:46] <iahmad> popey, is there some design doc/functional spec for new music app?
[20:46] <popey> iahmad: yup
[20:47] <iahmad> popey, would you please point me to that
[20:47] <popey> iahmad: https://docs.google.com/a/canonical.com/presentation/d/1L3eGhOe-0eEmKtUurthpUEaweFradSFb3t6W-KiIZMU/edit#slide=id.g4d67bb613_11
[20:47] <iahmad> +?
[20:47] <popey> does that link work for you?
[20:48] <iahmad> popey, it did, thanks
[20:48] <popey> no problem
[20:59] <robru> kenvandine: ah sorry this time it's my fault. I'm working on a fix for that bug already. WATCH_ONLY might be able to workaround that for now
[20:59] <iahmad> popey, what is the lp project for new music app?
[20:59] <popey> lp:music-app
[21:08] <kenvandine> robru, ok
[21:21] <robru> *phew* ;-)
[21:24] <kenvandine> :)
[21:24] <kenvandine> now if i can figure out how to install powerd from that ppa :)
[21:25] <kenvandine> ogra_, ideas?
[21:25] <kenvandine>  unable to make backup link of `./usr/share/powerd/device_configs/config-default.xml' before installing new version: Invalid cross-device link
[21:34] <robru> kenvandine: oh I saw instructions for that once forever ago. you have to like, copy the files into the rootfs while in recovery mode or something.
[21:35] <om26er> kenvandine, I had a system-settings crash, not sure if its related to the change in the silo.
[21:35] <om26er> https://errors.ubuntu.com/oops/5b9b2d7c-6ea1-11e4-bce8-fa163e4ccdf2
[21:36] <kenvandine> om26er, doubtful, what were you doing when it crashed?
[21:36] <kenvandine> like what panel?
[21:37] <om26er> kenvandine, after toggling many settings, I came to the main screen and tapped on 'Brightness'  panel and app freezed and eventually crashed.
[21:37] <kenvandine> robru, but how do you actually update the package?
[21:38] <kenvandine> ok, that isn't different
[21:38] <kenvandine> known issue :)
[21:39] <kenvandine> s/isn't/is/
[21:41] <robru> kenvandine: can't remember, sorry.
[21:42] <kenvandine> robru, thx anyway
[21:42] <robru> kenvandine: there should be a wiki for it somewhere. does it not mention installation instructions in the test plan?
[21:43] <robru> kenvandine: http://paste.ubuntu.com/8224550/ here you go
[22:00] <jdstrand> cwayne1: can you ping me when you are ready for me to push apparmor-easyprof-ubuntu?
[22:09] <cwayne1> jdstrand: will do
[22:09] <jdstrand> cwayne1: also, if I go eod, feel free to ask trainguards to do it without me
[22:09] <robru> jdstrand: do what now?
[22:10] <jdstrand> robru: we like to coordinate the apparmor-easyprof-ubuntu publication with the custom tarball
[22:10] <robru> jdstrand: you got a silo ready to be published?
[22:11] <jdstrand> robru: since, apparmor-easyprof-ubuntu is ready and signed off, I was just saying that if I wasn't around, cwayne1 didn't have to wait on me
[22:11] <jdstrand> robru: and could ask one of you to press the publish botton
[22:11] <jdstrand> robru: yes, rtm silo 002
[22:11] <robru> jdstrand: ah ok. thought you might need me to upload something into a silo, which I'm not prepared for. but I can publish silos when needed ;-)
[22:11] <jdstrand> hehe, no, silo is completely ready :)
[22:38] <nuclearbob> trainguards: com.ubuntu.music-2.0.744.all should be ready to land, there's no silo associated since it's a click package
[22:44] <popey> nuclearbob: balloons can upload to store
[22:44] <popey> (if he's around)
[22:44] <nuclearbob> let's see if he is
[22:45]  * balloons floats
[22:45] <popey> \o/
[22:45]  * popey hugs balloons 
[22:46] <balloons> yay! music!
[22:46] <nuclearbob> woo music!
[22:46] <popey> balloons: the click is linked from the trello card for it
[22:48] <balloons> pushed, popey, review time
[22:53] <nuclearbob> woo!
[22:56] <popey> balloons: i dont see it
[22:56] <popey> assume it passed
[22:57] <popey> oh, now i do
[22:57] <popey> odd
[22:57] <popey> uh, we need to speak to martin tomorrow, there's some inconsistencies in the store.
[22:58] <popey> Thanks nuclearbob balloons ☻
[22:58] <nuclearbob> :)
[23:00] <nuclearbob> and now, eod
[23:01] <popey> \o/
[23:01] <ogra_> is it in ?
[23:04] <balloons> popey, ack
[23:04] <popey> yes
[23:05] <ogra_> hmm, my phone doesnt think so
[23:08] <popey> bet i busted the store by rolling back
[23:09] <popey> yeah, i think i broke the store
[23:09] <popey> balloons: you still about?
[23:11] <popey> i think i need to file a bug for this...
[23:23] <balloons> popey, awesome
[23:23] <popey> yeah, not ☻
[23:23] <balloons> popey, what would you like me to do?
[23:24] <popey> balloons: my theory was that we should apporove the broken 2.0.738 then try and upload 2.0.744, but I fully expect that to fail
[23:24] <popey> because you already uploaded 2.0.744
[23:24] <popey> so rather than that I'm gonna file a bug and send a mail to phablet about it
[23:24] <popey> because the store is basically broken
[23:24] <popey> so nothing required for you to do
[23:27] <balloons> popey, ah that does make sense
[23:27] <balloons> no bueno bueno
[23:27] <balloons> bah, I failed
[23:33] <popey> bug 1393606
[23:33]  * popey emails phablet
[23:47] <om26er> trainguards please rebuild ubuntu-rtm/landing-006
[23:49] <robru> om26er: done
[23:50] <om26er> robru, thanks.
[23:50] <robru> om26er: you're welcome
[23:51] <ogra_> robru, for rtm 2 there is a coordinated landing with a custom tarball needed (for which we do not yet have QA) ... so dont land it :)
[23:51] <robru> ogra_: yeah was waiting for a ping from cwayne1 on that one
[23:51] <ogra_> cool
[23:52] <ogra_> we will need to coordinate that with an image build too
[23:52] <ogra_> (stop the importer, wait for rootfs, start importer with rootfs and custom tarball in place)