[00:31] <elopio> fginther: sorry, internet died here for a long time.
[00:31] <elopio> more investigation sounds correct, thanks.
[01:05] <mterry> What is the best way to reproduce a jenkins environment like it runs unity8 qmltests in?
[02:05] <imgbot> [03:35] <imgbot> [03:35] <imgbot> [09:05] <Saviq> cihelp, hey, I talke to ev a day or two back about https://code.launchpad.net/~unity-team/unity8/shellRotation/+merge/248400 not getting unity8-ci's attention
[09:05] <Saviq> apparently kgunn wasn't whitelisted for the job, but even after he was added, job is still boring?
[09:30] <ev> Saviq: if you're okay to wait until America wakes up, josepht will look into it as our vanguard today. Sorry that my fix didn't take.
[09:30] <Saviq> ev, sure, nw, not pressing - just want to get this resolved
[09:31] <ev> absolutely, as do I :)
[09:31] <sil2100> jibel, ogra_: internet problems
[09:31] <sil2100> Much ping, many latency
[09:31] <ogra_> lovely
[09:45] <sil2100> Robotic
[10:44] <sil2100> davmor2: yeah, so I checked the channel config and it might be non-trivial to put my test tarball to 14.09-proposed-customized
[10:45] <davmor2> \o/
[10:45] <sil2100> davmor2: I would have to modify the config for that as it's currently pulling those out of jankins
[10:45] <sil2100> So I prefer not to touch that
[10:45] <davmor2> saves the hassle of reverting
[10:53] <Chipaca> what's the right format for listing two bugs as closed in a single changelog entry? is this machine parsed at all?
[11:01] <Chipaca> trainguards, i can haz silo for row #55 plz?
[11:08] <Ursinha> Saviq: jenkins is being lazy in general, it seems, other people are reporting it as well, I'll talk to CI vanguard today about it and see how can we conduct proper investigation
[11:08] <sil2100> Chipaca: suar
[11:09] <sil2100> Chipaca: and yes, it's machine parsed but there's not one single best format
[11:09] <sil2100> Chipaca: sometimes people use (LP: #number, LP: #number2)
[11:09] <Chipaca> sil2100: I went for “(LP: #1426418, LP:1427702)”, here's hoping that works :)
[11:09] <Chipaca> oh, i just noticed that's self-inconsistent
[11:09] <sil2100> I would say the second one needs a # as well ;)
[11:09] <Chipaca> oh dear
[11:10] <Chipaca> fixed: now “(LP: #1426418, LP: #1427702)”
[11:11] <robru> sil2100: Chipaca http://bazaar.launchpad.net/+branch/cupstream2distro/view/head:/tests/unit/test_branchhandling.py#L211 here is the test code showing how bugs are parsed. it's pretty fast&loose.
[11:11] <robru> (also I am so not here right now)
[11:12] <Chipaca> robru: thanks :)
[11:13] <robru> Chipaca: you're welcome!
[11:13] <Chipaca> so it would've worked before too :)
[11:13] <robru> Chipaca: oh and it's also case-insensitive on top of the mostly-lowercase examples shown there
[11:14] <Chipaca> sil2100: i'm afraid i was pointing at the wrong merge (got an lp lock failure on that one, pushed to a different one, but bzr had already 'remembered' the first one, and i didn't notice)
[11:14] <Chipaca> sil2100: could you rejigger it?
[11:15] <sil2100> Chipaca: hm, ok, let me re-assign
[11:15] <Chipaca> thanks
[11:19] <Chipaca> sil2100: thank you again :)
[11:19]  * Chipaca builds
[11:19] <sil2100> The spreadsheet acts funny
[12:47]  * sil2100 goes to lunch
[13:09] <ricmm> sil2100: hey, could I get a silo for line 56 please
[13:10] <ricmm> or someone :)
[13:21] <ricmm> Mirv: maybe you could give me a hand with line 56
[13:21] <Saviq> ricmm, they're all responding to "trainguards" ;)
[13:21] <ogra_> just not if the bot says it
[13:22]  * ricmm summons trainguards
[13:22] <ricmm> no lightning and explosions :(
[13:26] <bzoltan_> om26er:  please feel free to check with me if you have questions related to the UITK landing.
[13:35] <om26er> bzoltan_, thanks, I am going to start with verifying the bug fixes and then do some general testing for things
[13:47] <bzoltan_> om26er:  it fixes 26 bugs :) so enjoy
[13:58] <om26er> bzoltan_, do you know if bug 1425470 is desktop specific ?
[13:59] <om26er> t1mp, I was looking for you :) is bug 1425470 for the desktop ?
[13:59] <bzoltan_> https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1425470
[14:00] <bzoltan_> om26er: it is a desktop specific
[14:00] <om26er> bzoltan_, great, thanks
[14:08] <om26er> bzoltan_, clock app crashes after setting up an alarm and then trying to edit it.
[14:08] <om26er> found that while verifying fix for https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1401883
[14:09] <om26er> the crash is 100% reproducible.
[14:09] <nik90> om26er, bzoltan_: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1422693/comments/1
[14:10] <om26er> nik90, ah, its your crash ?
[14:10] <om26er> phew!
[14:10] <nik90> om26er: well it appeared after the SDK fix for the bug you linked https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1401883
[14:11] <nik90> om26er: so it could be due to the SDK change since in RTM I cannot reproduce the crash
[14:11] <om26er> oh
[14:11] <nik90> om26er: however zsombor said that it could be due to API changes in vivid that clock app may not be adjusted for, but I havent looked into it yet
[14:12] <josepht> Saviq, kgunn: are you guys okay with all of the LP team 'unity-team' being able to land MPs?
[14:13] <Saviq> josepht, it's just -ci, we're landing through the CI train anyway, so really anything targeting lp:unity8 should trigger...
[14:14] <josepht> Saviq: unfortunately users/teams have to be whitelisted even for -ci
[14:14] <sil2100> ricmm: on it!
[14:14] <josepht> Saviq: afaiui at least
[14:14] <sil2100> ricmm: I was on lunch, and right now I'm the only trainguard around sadly :)
[14:15] <Saviq> josepht, if there has to be a team... I'd be fine with ~contributor-agreement-canonical
[14:15] <Saviq> which kinda makes sense
[14:15] <sil2100> ricmm: with the spreadsheet it would be painful to implement, but I hope once we have a working replacement we should be able to add some auto-assignment functionality in conditions when there are many free silos and no conflicts
[14:16] <Saviq> sil2100, silo *assignment* shouldn't care for conflicts IMO
[14:18] <sil2100> Saviq: in theory yes - we would have to implement some nice things that would inform the lander that the silo conflicts with silo x,y,z, since without that it could waste precious testing time of landers
[14:19] <sil2100> The current bot is not enough as not too many people notice its messages
[14:20] <Saviq> sil2100, yeah, xchat-gnome doesn't highlight my name for the bot msgs...
[14:20] <Saviq> sil2100, anyway, I'm sure that's solvable
[14:21] <josepht> Saviq: for the time being I've added unity-team.  I'll discuss with my team to see if adding ~c-a-c is acceptable.  I'm not certain that we can limit that just to lp:unity8 MPs
[14:22] <Saviq> josepht, sure, thanks
[14:29] <ricmm> sil2100: thanks!
[15:16] <jibel> sil2100, is there anything to discuss at the landing meeting today?
[15:16] <sil2100> jibel: I think with the current velocity no
[15:16] <jibel> sil2100, lets cancel it then?
[15:16] <sil2100> popey: just poke me once reminders is ready for a re-rest
[15:17] <sil2100> jibel: yeah, I think my todays connection would anyway interfere
[15:17] <sil2100> With robotic sounds and such
[15:17] <sil2100> popey, jibel, robru, ogra_, rvr, davmor2: no evening meeting today
[15:17] <ogra_> fine with me
[15:17] <rvr> Ack
[15:17] <ogra_> specifically on a friday :)
[15:17] <sil2100> davmor2: could you maybe cancel the todays one? ;) Since you're the owner!
[15:17] <davmor2> \o/ parties for the rest of the day
[15:18] <davmor2> sil2100: nope :P
[15:18] <popey> sil2100: okay, will be monday
[15:18] <ogra_> sil2100, as if your phone calendars would sync that :P
[15:18] <ogra_> *our
[15:21] <davmor2> sil2100: your the owner now buddy boy :D
[15:22] <sil2100> Uh oh!
[15:23] <sil2100> I'm teh owner!
[15:24] <sil2100> davmor2: thanks ;)
[15:24] <davmor2> sil2100: so erm feel free to cancel the meeting any time ;)
[15:24] <sil2100> Iz canzeld
[15:25] <om26er> nik90, is there a branch for the fix for bug 1422693 ?
[15:26] <nik90> om26er: that bug was also fixed by the SDK MP https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/alarm-regression-fix/+merge/251096
[15:27] <nik90> om26er: To be more clear, both https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1401883 and https://launchpad.net/bugs/1422693 were fixed by that MP
[15:28] <om26er> nik90, hmm, well I found that crash while I was testing a silo that contained the above branch. So the issue is still happening
[15:29] <nik90> om26er: When I tested that MP, I was able to enable/disable alarms that were saved before
[15:30] <nik90> om26er: But I noticed clock app crashes when trying to create a new alarm sometimes
[15:30] <om26er> nik90, hm, the crash that I am seeing happenes when you try to edit the alarm
[15:30] <nik90> om26er: does it also crash when you try to enable/disable an alarm?
[15:31] <om26er> nik90, doesn't seem to crash while enabling/disabling
[15:31] <om26er> nik90, I found the crash while testing the fix for #1401883
[15:34] <nik90> om26er: can I ask if it crashes after trying to save an old alarm? Or when trying to open an alarm itself?
[15:34] <nik90> om26er: I will have to flash my phone back to ubuntu-vivid to test this out
[15:35] <om26er> nik90, I create a new alarm, it appears in the alarm list. When I try to tap the alarm list item to edit it, the app crashes.
[15:35] <om26er> It happens for both old and new alarms.
[15:35] <om26er> nik90, stacktrace here (if you can open that page): https://errors.ubuntu.com/oops/ab1b4b58-c409-11e4-8065-fa163e4aaad4
[15:36] <nik90> om26er: ooh that's bad..I will look into it and coordinate with zsombor
[15:37] <nik90> yeah I am able to open the page
[15:38] <om26er> bzoltan_, Hey!
[15:38] <bzoltan_> om26er:  here
[15:38] <om26er> bzoltan_, the silo causes a crash in clock app. ^
[15:39] <bzoltan_> om26er: Does the clock app have autopilot test for it?
[15:39] <dobey> slangasek: oh sorry, i didn't realize there was a new lib package too in the other MP. it's not my landing but i need it for work we're doing in the click scope, so i was just poking to get a review. thanks. i'll bug the devs
[15:40] <nik90> bzoltan_: there is a QML test for it
[15:41] <nik90> bzoltan_: http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.0/view/head:/tests/unit/tst_alarm.qml#L292
[15:41] <bzoltan_> nik90: AP test is the test
[15:43] <nik90> bzoltan_: there isnt a AP test for it. This is also why the QML test are also run by jenkins on every MP merge
[15:44] <bzoltan_> nik90: QML test is not a functional test. We must have AP tests for all critical functions
[15:44] <zsombi> nik90: let me check what do you have in the app
[15:44] <bzoltan_> zsombi: om26er just left the ch .. I guess he will be back
[15:45] <nik90> zsombi: I am checking as well, here's the stack trace log https://errors.ubuntu.com/oops/ab1b4b58-c409-11e4-8065-fa163e4aaad4
[15:47] <bzoltan_> nik90:  please do not replace AP with QML tests... AP testing is the only ways to prevent integration caused regressions like this.
[15:47] <zsombi> nik90: give me the file name which lists the alarms
[15:47] <bzoltan_> nik90:  because we have unit tests for editing alarms :) and that passed.
[15:47] <nik90> zsombi: http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.0/view/head:/app/alarm/EditAlarmPage.qml
[15:48] <nik90> bzoltan_: because it is becoming really difficult to maintain AP, QML units tests and manual tests just by myself..I am trying to unify the test suite for clock app
[15:49] <zsombi> nik90: do you by any chance unload the page which contains the AlarmModel when teh edit page is opened?
[15:49] <bzoltan_> nik90:  it is fine to make QML unit tests... but those are not functional tests and so teh UITK test plan can not run them
[15:50] <nik90> zsombi: 1 sec, let me check
[15:50] <bzoltan_> nik90:  not to mention that the clock app AP test requires manual input to accept the policy
[15:50] <nik90> bzoltan_: which policy?
[15:51] <bzoltan_> nik90:  the first time the clock app is deployed it asks for access
[15:51] <bzoltan_> nik90:  and that makes _all_ autopilot tests fail
[15:51] <nik90> zsombi: no I dont unload the page that contains the alarmmodel. the laarm model is loaded by mainview essentially
[15:51] <zsombi> nik90: how about using teh new ListItem in the list?
[15:51] <nik90> bzoltan_: I agree but I cannot do anything about it. That's an upstream bug which was recognized by QA
[15:52] <nik90> zsombi: Well the SDK is currently running clock app tests from the trunk branch which is for RTM
[15:53] <zsombi> nik90: ok
[15:53] <nik90> zsombi: Also I cannot switch to the new listitems without having multiselect feature which hasn't landed in vivid yet. I was planning to transition the alarm listitem after it lands :)
[15:53] <bzoltan_> nik90:  who is maintaining the clock app's AP tests? :) I thought it is you
[15:54] <zsombi> nik90: I am checking the way you get the alarm data when you change the alarm...
[15:54] <bzoltan_> nik90:  This ongoing UITK landing has the ListItem... what is now blocked by the clock app :D :D
[15:54] <nik90> bzoltan_: I do..but in the case of the location prompt issue, I got the help from QA to fix that issue in https://code.launchpad.net/~brendan-donegan/ubuntu-clock-app/disable_location_prompt/+merge/242682
[15:55] <nik90> bzoltan_: but if you check the last few comments in that MP, you will see that it requires patches upstream as well
[15:55] <nik90> before it can be fixed in the clock app
[15:55] <nik90> zsombi: do you want to do this in a hangout, would be much easier to point out the relevant parts of the code
[15:55] <zsombi> nik90: ehh... I cannot get any closer... to me seems the get() function is crashing somehow...
[15:56] <zsombi> nik90: let's try one quick
[15:57] <zsombi> nhave an URL?
[15:58] <zsombi> nik90: have an URL?
[15:58] <nik90> zsombi: https://plus.google.com/hangouts/_/guud6q3hb2mop34ybehpg7k7wqa
[16:04] <greyback_> sil2100: hey, I want to land rtm silo12, which fixes https://bugs.launchpad.net/ubuntu-rtm/+source/qtmir/+bug/1423787 - am I blocked unless the priority is bumped to critical?
[16:05] <sil2100> greyback_: hey
[16:06] <sil2100> greyback_: hm, looking at it, it looks like it's a good thing to land
[16:06] <sil2100> It's milestoned for ww13-ota
[16:06] <greyback_> sil2100: hold off for one sec, I need to confirm something
[16:06] <sil2100> And it's a battery fix...
[16:06] <greyback_> yeah
[16:06] <bzoltan_> om26er:  zsombi and nik90 are working on that issue. It is not clear yet for me if it is an app bug what the new landing just oncovered or a regression. Would you please carry on with the validation and revisit this issue in an hour or so?
[16:07] <om26er> bzoltan_, ok, sure.
[16:07] <om26er> bzoltan_, I have verified the bugs that could be tested manually, other I believe are covered by unit tests.
[16:08] <om26er> bzoltan_, now just fiddling around here and there to see if the silo broke something.
[16:08] <ahayzen> greyback_, o/ just to double check the if you are playing music and the music-app is not in the foreground and the screen is off... the app still has a wakelock to keep it awake so it can tell media-hub of the next track to play right?
[16:09] <greyback_> ahayzen: correct, the app itself (actually pulseaudio) will have its own wakelock to keep the device awake
[16:09] <ahayzen> greyback_, and our process isn't cut due to the lifecycle exception ?
[16:09] <greyback_> ahayzen: also correct
[16:09] <ahayzen> greyback_, awesome thanks just wanted to double check :)
[16:09] <greyback_> ahayzen: understood :)
[16:14] <zsombi> bzoltan_: we couldn't detect the root cause, we agreed with nik90 that he is gonna make some changes on the app, and if still crashes, then he tries to provide a simple app so I can work on it
[16:15] <zsombi> bzoltan_: but it can be that we cannot fix earlier than Monday
[16:16] <bzoltan_> zsombi: nik90: just to be precise... this issue is holding up the most important and final 15.04 reelase of the UITK. SO I really would like to hear something real super quickly :)
[16:17] <bzoltan_> nik90:  and yes... if the app would have AP coverage then this issue would have been captured on Wednesday ... so no, I am not happy with QML test only unit tests.
[16:19] <nik90> bzoltan_: alrite I will convert all of QML *functional tests* as well to AP I guess
[16:20] <nerochiaro> greyback_: hi, did you see my messages from yesteday ?
[16:21] <greyback_> nerochiaro: I did, and I managed to repro it on my device
[16:21] <greyback_> then had to blast it away to work on something else
[16:21] <greyback_> but at least I can repro, so now I can investigate
[16:22] <Saviq> ogra_, got 124 on your mako by any chance?
[16:22] <bzoltan_> nik90:  I do not ask you to overdo it :) but he critical functions should be AP covered.
[16:22] <nerochiaro> greyback_: excellent
[16:23] <greyback_> nerochiaro: also confirmed that there are not 2 camera-app process running at any stage
[16:23] <bzoltan_> nik90: all in all, it s a good example that QML tests do not replace AP tests < Saviq ;)
[16:23] <ogra_> Saviq, my mako is out of battery since 2 months or so
[16:23] <Saviq> bzoltan_, I never said they do
[16:24] <Saviq> ogra_, k nvm
[16:24] <nerochiaro> greyback_: and camera did not crash during previous tests, right ?
[16:24] <greyback_> nerochiaro: feck, forgot to look
[16:24] <bzoltan_> Saviq: I know, but it worth to keep in mind
[16:24] <nerochiaro> greyback_: it did not in my case
[16:24] <bzoltan_> nik90:  but now let's hope you can fix the app , please keep me posted.
[16:25] <nik90> bzoltan_: yeah will do
[16:25] <greyback_> nerochiaro: ok. Monday I'll be giving this my full attention
[16:26] <nerochiaro> greyback_: feel free to poke me too. I am off now. have a great weekend
[16:26] <greyback_> nerochiaro: will do, thanks and have a good one!
[16:32] <zsombi> bzoltan_: nik90: It crashes in the QHash
[16:33] <bzoltan_> zsombi:  wth?
[16:33] <zsombi> bzoltan_: good question...
[16:35] <zsombi> bzoltan_: nik90: feels like there's some race condition... the get() function dies, the model works well
[16:35] <zsombi> bzoltan_: nik90: but the get() dies only if I do it like the Clocka app does...
[16:35] <nik90> zsombi: hmm
[16:36] <nik90> zsombi: so If I passed the alarm object as we discussed, would that fix it?
[16:36] <zsombi> nik90: let me stretch it a bit
[16:36] <nik90> zsombi: also how does get() die when it is inside the edit alarm page
[16:37] <zsombi> nik90: yes, it dies then...
[16:37] <zsombi> nik90: and it works if I do PageStack.push("AlarmEdit.qml", {tempAlarm: model})
[16:38] <zsombi> nik90: or {tempAlarm: alarmModel.get(index)}
[16:38] <nik90> zsombi: oh!
[16:39] <zsombi> nik90: remember, you don't even need to use get() if you open teh alarm by tapping on teh item, you hav ethe model role =on your disposal
[16:39] <zsombi> nik90: the crash I reproduced with the test app I made
[16:39] <zsombi> from teh toolkit
[16:40] <nik90> zsombi: yeah I understand. Let me confirm the fix. I just finished flashing vivid. if it does fix the crash, then this is a app issue and the UITK can proceed with the final vivid release
[16:40] <nik90> zsombi: agree? ^^
[16:41] <bzoltan_> nik90:  he does :D
[16:41] <bzoltan_> om26er: ^^^
[16:41] <nik90> bzoltan_: awesome
[16:41] <om26er> coolio
[16:47] <bzoltan_> zsombi:  thank you very much dude .. and now get lost from here
[16:53] <bzoltan_> nik90:  I am happy that there is a solution. Thank you for taking this ball.
[16:54] <nik90> bzoltan_: well zsombor found out the mistake + I need those new listitems badly :P
[17:00] <ogra_> sil2100, just FYI my phone just notified me about the meeting :) didnt really help to cancel the event from the calendar
[17:00] <sil2100> :|
[17:01] <ogra_> (as i had expected, i doubt it updates regulary)
[17:01] <ogra_> popey, ^^ is that expected to work ?
[17:01] <bzoltan_> nik90:  you will get them today if all goes well...
[17:02] <popey> it should sync, if it doesn't file a bug
[17:02] <bzoltan_> nik90:  actually I have an idea... you do not have to invest your time too much in AP tests if you regularly test your app with the staging UITK
[17:02] <ogra_> popey, on what fequency ... the meeting was only canceled 1.5h ago
[17:03] <popey> i also got the reminder on my phone
[17:03] <popey> it should sync in the background imo.. bfiller ? sync-monitor - what triggers it?
[17:03] <popey> only the sync button in calendar?
[17:03] <ogra_> and when :)
[17:04] <bfiller> popey: sync happens if you modify or add a new google calendar event in the calendar app
[17:04] <bzoltan_> nik90: from here https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/staging
[17:04] <popey> right, has to be done in the app
[17:04] <ogra_> bfiller, so it doesnt pick up changes from gcal ever ?
[17:04] <bfiller> popey: changes made on the google side are not sync'd to the app automatically, that's what the refresh button is for. we get no push notifications
[17:04] <bfiller> ogra_: at startup
[17:04]  * ogra_ wouldhave thought at least once a day
[17:05] <ogra_> at startup of the phone ?
[17:05] <bfiller> ogra_: of the app
[17:05] <bfiller> I believe
[17:05] <ogra_> ah, i never start it
[17:05] <bfiller> not 100% sure on that
[17:05] <ogra_> i manage my calendar via the desktop
[17:05] <ogra_> the phone is only used for the notifications ...
[17:05] <ogra_> we should have a sync shedule
[17:05] <bfiller> basically we have no push notification from google for calendar events
[17:05] <bfiller> ogra_: we didn't want to poll
[17:06] <ogra_> well, we kind of have to to keep the calendar updated
[17:06] <ogra_> at least optionally with a setting in the calendar app or some such
[17:06] <bfiller> ogra_: could be done yes
[17:07] <bfiller> ogra_: now there is a manual sync button you can press in the app
[17:07] <nik90> bzoltan_, om26er: I confirm that the crash was due to the code in clock app. I have a patch ready to fix it in the clock app and tested it on vivid image 124 Mako. You can go ahead with the UITK landing.
[17:07] <om26er> nik90, bzoltan_ \o/
[17:07] <nik90> bzoltan_, om26er: If you so wish, I can provide the MP link for you guys to try it if you want.
[17:07] <ogra_> bfiller, sure ... but only if i actually know something changed :)
[17:08] <bfiller> ogra_: we really want push notifications but until we have that your way could work
[17:08] <om26er> bzoltan_, I think we need some kind of sanity test suite for the UI-toolkit, a list of test cases to be checked manually, stuff that cannot be automated.
[17:14] <nik90> bzoltan_, zsombi: https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-alarm-crash/+merge/252150
[17:15] <nik90> bzoltan_: hmm I could do that (testing clock app with staging uitk regularly). We'll see. I don't want to take on more responsibility than I already do..if every other project like i-dt, sdk, eds etc run clock AP tests to check for regressions, then I rather convert to AP and forget about it.
[17:24] <sil2100> Ok, I go lay down now for a few moments
[17:24] <bzoltan_> om26er: In my opinion we do not need to invent a substitute of autopilot for the cases where the app has no autopilot coverage :D The solution is to have proper autopilot tests
[17:24] <sil2100> robru should be around in case any trainguard-related things are needed
[17:25] <om26er> bzoltan_, autopilot cannot cover visual issues for example
[17:29] <bzoltan_> om26er:  that is true... I do basic sanity check, but only basic. Releasing the UITK is by far the most test covered and most time consuming releasing process, I woul be happer to make it shorter and not longer
[17:30] <om26er> bzoltan_, You need to hire a release manager :)
[17:31] <om26er> bzoltan_, anyways, this landing is good to go.
[18:05] <bzoltan_> om26er:  hiring a release manager would make me half unemployed :D
[18:05] <ogra_> hire two ... then they need a manager
[18:05] <bzoltan_> om26er: Thank you for the validation.
[18:06] <bzoltan_> ogra_: errr.. I have walked that floor before :)
[18:06] <ogra_> heh
[18:14] <robru> kenvandine: can I get you to do a packaging ack? https://ci-train.ubuntu.com/job/ubuntu-landing-003-2-publish/ thanks
[18:14] <kenvandine> robru, sure
[18:14] <robru> thanks
[18:15] <bzoltan_> robru:  any chance to hold that silo3 for a sec?
[18:15] <robru> bzoltan_: yes there is ;-)
[18:18] <kenvandine> robru, ok ack
[18:18] <om26er> Chipaca, Hi! How long does it normally take for a push notification to appear ? is there a fixed refresh interval ?
[18:18] <bzoltan_> robru:  OK, good to go
[18:18] <robru> kenvandine: thanks
[18:18] <robru> bzoltan_: sure thing
[18:18] <bzoltan_> robru:  I ws just confused by the state of a branch what was proposed to the landing branch
[18:19] <robru> bzoltan_: yeah the diff looked a little weird with rtm changelog entries being proposed into the vivid branch, but that's not harmful by itself...
[18:58] <robru> infinity: cjwatson: https://ci-train.ubuntu.com/job/ubuntu-landing-017-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-app-launch_0.4+15.04.20150305.1-0ubuntu1.diff new binary package needs an ack if you have  a sec
[19:06] <infinity> robru: Looking.
[19:06]  * tedg can answer questions on that too
[19:06] <robru> infinity: thanks
[19:08] <infinity> tedg: So, ubuntu-app-test builds on all arches, but only links libmirwhatever on arches where it exists?
[19:09] <tedg> infinity, It doesn't build the binary, it uses a shell script that says "nope, sorry"
[19:09] <infinity> Oh, heh.
[19:09] <infinity> tedg: You could just not build the package at all.
[19:09] <tedg> infinity, I didn't want to mess up other people who want to dep on it.
[19:09] <infinity> tedg: Fair enough.
[19:10] <infinity> tedg: Not a criticism of the packaging, but the upstream (since the packaging moves things to the right spot), but a subdir in /usr/bin, really?
[19:11] <infinity> tedg: Not only is that icky, but I generally think it's sane when an upstream "make && make install" lands things in more or less the same spot as the packaging would.
[19:11] <tedg> infinity, Yeah, I wanted to use "*" for the bins in both of the packages.
[19:11] <tedg> infinity, Otherwise I'd end up listing them
[19:11] <tedg> Is there another way to do that?
[19:12] <infinity> tedg: Anyhow, as an archive guy, I don't care, since the debs are right, just an "ew".
[19:12] <tedg> I didn't want to explode the .install files
[19:12] <om26er> Chipaca, ping, need some help with 'poke'
[19:13] <Ursinha> popey: hello :) are you still around?
[19:14] <infinity> tedg: And, no, .install files don't support any real fancy regexes or anything, so probably hard to do what you're after.
[19:14] <tedg> Bummer, I didn't think so. Hoping it was a secret :-)
[19:16] <infinity> tedg: If ubuntu-app-test is just one or two binaries, you can override_dh_install to install those two by hand, then wildcard the other package, that's about as clean as you can get while still shipping it all in bin (other than having it all listed in the install files, as you noted)
[19:16] <infinity> Well, s/install/move/ since you don't want it in both places.
[19:17] <infinity> So, yeah.  Whatever.  Your solution works, just sucks for using upstream Makefiles.
[19:18] <tedg> Hmm, yeah. I might play with that, see if something nicer comes out.
[19:18] <robru> infinity: so that's an ack?
[19:19] <dobey> tedg: how many binaries do you have?
[19:19] <infinity> robru: Yeah, it's good enough.  If ted wants to fix how he installs things upstream, that's not relevant to Ubuntu.
[19:19] <robru> infinity: thanks!
[19:19] <tedg> dobey, ~10
[19:19] <infinity> tedg: Oh.  When you said "explode", I was thinking dozens.
[19:20] <dobey> tedg: they're all things that should be run directly by people on the command line?
[19:20]  * tedg is a small player
[19:20] <infinity> tedg: If it's just 10, list them all, and use --fail-missing to make sure you don't screw up and forget to add new ones when they happen.
[19:20] <tedg> dobey, Yeah, they're mostly tools for figuring out what's wrong with Unity 8 ;-)
[19:21] <infinity> robru: adconrad, not infinity
[19:21] <dobey> tedg: ah, bummer
[19:21] <robru> infinity: heh, thanks
[19:21] <tedg> robru, Instead of infinity try nan
[19:21] <infinity> (But good to see it failing)
[19:21] <infinity> tedg: ITYM Batman.
[19:22] <tedg> Thanks infinity and robru!
[19:22] <robru> tedg: you're welcome
[19:22] <dobey> no no, thank you
[19:23] <dobey> now i might be able to get these autopilot tests working in jenkins on mako/emulator
[19:24] <robru> Saviq: you around? what packages do you work on that use 'X-Auto-Uploader: no-rewrite-version'?
[19:29] <rsalveti> ogra_: Writing Boot Image /dev/disk/by-partlabel/boot
[19:29] <rsalveti> ogra_: Processing triggers for initramfs-tools-ubuntu-touch (0.83) ...
[19:29] <rsalveti> ogra_: on arale, after dist-upgrade
[19:29] <rsalveti> it seems flash-kernel is trying to flash the kernel in there
[19:29] <rsalveti> and makes the device to become dead
[19:29] <ogra_> lovely
[19:30] <ogra_> lets put FLASH_KERNEL_SKIP=true into /etc/environemnt ...
[19:30] <rsalveti> ogra_: yeah
[19:52] <popey> Ursinha: ya
[19:54] <Ursinha> popey: hi :) we have modified https://wiki.ubuntu.com/Touch/Testing with the instructions to run smoke testing locally as close to as CI does, do you mind having a look to see if that looks okay?
[19:54] <Ursinha> please :)
[19:55] <Ursinha> there is also http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
[19:56] <popey> Ursinha: will take a look
[19:56] <Ursinha> popey: thanks
[20:11] <Chipaca> om26er: pong
[20:11] <om26er> Chipaca, poke is giving me hard time
[20:12] <Chipaca> om26er: it's not particularly user-friendly i'm afraid
[20:12] <Chipaca> om26er: how can i help?
[20:12] <ogra_> rsalveti, http://paste.ubuntu.com/10552444/ ... but that will require you to call flash-kernel explicitly on nexus devices indeed
[20:12] <om26er> Chipaca, I need to test silo 2, and need to create fake notifications with poke it says:
[20:12] <om26er> Something went wrong: Please ensure the token filename's directory is readable only by you.
[20:13] <Chipaca> om26er: chmod 0700 ~/.config/poke; chmod 0600 ~/.config/poke/token
[20:14] <rsalveti> ogra_: yeah, that's fine
[20:15] <om26er> Chipaca, if I do "./poke -t Hi -b "there asagd"" is it supposed to show me something ?
[20:16] <om26er> ...on the device
[20:16] <om26er> it does print "200 {"ok":true}"
[20:16] <Chipaca> om26er: yes
[20:16] <om26er> Chipaca, hm, no notifications for me
[20:17] <Chipaca> om26er: how's your network? :)
[20:18] <om26er> Chipaca, its good
[20:18] <om26er> Chipaca, I restart the device and I can see the notification
[20:23] <Chipaca> om26er: at some point i'd like to sit down with you and debug logs and see what's going on, because it's not the first time i've seen weirdness with you and push
[20:30] <ogra_> rsalveti, uploaded
[20:31] <rsalveti> ogra_: lovely, thanks!
[20:33] <Chipaca> om26er: did it continue receiving notifications such that you could test?
[20:33] <om26er> Chipaca, yes, its good now. I am able to test it fine.
[20:33] <Chipaca> om26er: excellent
[20:47] <rsalveti> kenvandine: rebuilding your silo now
[20:47] <rsalveti> robru: will trigger a new rtm image after silo 12 gets published
[20:48] <kenvandine> rsalveti, thx
[20:50] <robru> rsalveti: cool
[21:05] <dobey> cihelp: hi, a new package is in vivid now "ubuntu-app-test" which should enable us to test pay-ui properly on devices, but the way tests are being run in jenkins, it doesn't get installed on the devices there. how can we get it installed on the device to run our tests?
[21:06] <josepht> dobey: I'll add a task and see what needs to happen\
[21:07] <dobey> josepht: thanks. i'm guessing once the tests are actually being run with adt-run in this scenario, it won't be an issue (but i don't know when that is going to happen)
[21:15] <imgbot> [21:16] <om26er> Chipaca, if you are still around, can you tell a way to force update to get latest gmail notifications ?
[21:16] <om26er> instead of waiting 5 minutes
[21:16] <Chipaca> om26er: yes, give me a moment
[21:17] <Chipaca> gdbus call --session -d com.ubuntu.AccountPolld -o /com/ubuntu/AccountPolld -m com.ubuntu.AccountPolld.Poll
[21:17] <Chipaca> om26er: ^
[21:17] <om26er> Chipaca, super, thanks
[21:19] <om26er> Chipaca, I have found a bug where gmail notifications won't appear in the menu, only the notification sound is heard.
[21:19] <om26er> good thing is its not related to the new silo
[21:19] <om26er> I'll report a bug now.
[21:19] <Chipaca> om26er: wow
[21:19] <Chipaca> om26er: turn on debug logs for push
[21:19] <Chipaca> om26er: attach push and poll logs to bug
[21:19] <Chipaca> om26er: thanks :)
[21:20] <om26er> Chipaca, how to turn debug on ?
[21:20] <Chipaca> om26er: debug logs for push: if device is writable, sed -i -e 's/info/debug/' /etc/xdg/ubuntu-push-client/config.json
[21:20] <Chipaca> om26er: and restart ubuntu-push-client
[21:20] <Chipaca> om26er: logs for push are in ~/.cache/upstart/ubuntu-push-client.log
[21:21] <Chipaca> om26er: logs for poll are in ~/.cache/upstart/account-polld.log
[21:40] <om26er> Chipaca, bug 1429276
[21:40] <om26er> Chipaca, it happens when screen gets locked.
[21:42] <Chipaca> om26er: niiice
[21:42] <Chipaca> i think i'll be chasing that next week
[22:25] <imgbot> [22:25] <imgbot> [22:52] <josepht> dobey: that change has landed for the pay-ui ubuntu-app-test package
[22:52] <dobey> great thanks
[22:53] <josepht> np