[02:05] <imgbot> [03:30] <imgbot> [03:30] <imgbot> [09:32] <sil2100> Mirv: wait for the authorization error
[09:32] <sil2100> Mirv: afterwards sound is back
[09:33] <sil2100> jibel: meeting!
[09:35] <popey> cihelp: jenkins seems unwell http://91.189.93.70:8080/job/generic-mediumtests-utopic/2349/console via https://code.launchpad.net/~carlos-mazieri/ubuntu-filemanager-app/samba-browsing-11/+merge/252982
[11:17] <fginther> popey, look like the jenkins slave was temporarily disconnected. The job is restarted and looking better now.
[11:17] <popey> thanks fginther
[12:38] <bzoltan_> Mirv:  would you reconf the silo13 please? I have just added there a browser fix MR
[12:45] <Mirv> bzoltan_: sure
[12:54] <bzoltan_> Mirv:  danke
[13:49] <sil2100> dobey: ping, did you see ToyKeeper's +1 on the payui?
[13:50] <dobey> sil2100: yes, i'm moving it the rest of the way through now
[13:50] <sil2100> dobey: excellent, give me a sign once it's published
[13:50] <dobey> sil2100: i'll update the spreadsheet status  when it's done
[13:52] <sil2100> Thanks
[13:56] <rvr> bfiller: Silo 2 is now approved.
[13:56] <bfiller> rvr: thanks
[14:15] <om26er> ralsina, Hi!
[14:15] <ralsina> hi om26er
[14:15] <om26er> ralsina, How can I verify the memleak fix for silo 16 ?
[14:15] <ralsina> om26er: there's no way to verify it directly :-P
[14:16] <ralsina> Running the test plan ensures that it's not triggering a crash
[14:16] <ralsina> it was a very slow memory leak, so it's not really noticeable
[14:16] <om26er> ralsina, hmm, test plan is quite simple, not sure of the level of its coverage
[14:17] <ralsina> om26er: it's a very simple package
[14:17] <om26er> ralsina, how about some kind of automated test for the leak ?
[14:18] <ralsina> om26er: I can give you a shell script that will trigger the formerly-leaking code
[14:18] <om26er> ralsina, yeah, that would be nice
[14:18] <ralsina> om26er: ok, give me a few minutes and I'll send it to you
[14:47] <bregma> hmm, the spreadsheet seems to be giving me grief, telling me what I do causes a fatal error
[14:47] <sil2100> bregma: ugh
[14:48] <sil2100> bregma: what are you trying to do?
[14:48] <bregma> I added a line
[14:48] <sil2100> huh
[14:48] <bregma> any updates I do give me the error
[14:48] <sil2100> Ok, I see the spreadsheet is in agony right now
[14:48] <bregma> still seems to work, it just complains a lit
[14:48] <bregma> *lot
[14:48] <sil2100> I get error notifications on every 5 minute update interval :|
[14:49] <bregma> kill it with fire
[14:49] <sil2100> Let me stop the auto-refresh scrips for a moment and let it settle
[14:49] <om26er> ralsina, any update on the script ?
[14:50] <ralsina> om26er: almost there
[14:54] <ralsina> om26er: I have a click app that has a button. When you click that button, it will call the leaking functions 10K times. That shows that the fix doesn't introduce any new crashes. Sadly, the leak was so small that even when calling it like that it's not noticeable :-P
[14:54] <om26er> ralsina, wow, nice. :)
[14:55] <ralsina> om26er: mailing you the click now :-)
[15:00] <om26er> ralsina, nothing, crashes, I'll give it a +1
[15:00] <ralsina> om26er: awesome, thanks!
[15:00] <ralsina> om26er: and sorry about fixing invisible stuff ;-)
[15:00] <om26er> heh.
[15:23] <om26er> rsalveti, Is there any test plan for hybris
[15:24] <rsalveti> om26er: not yet, because it's a core piece, if it gets broken, the UI will not even start
[15:24] <rsalveti> so we covered it with exploratory tests before
[15:24] <rsalveti> and it depends entirely on the hardware
[15:25] <om26er> rsalveti, by exploratory testing you mean general checking the sanity of things ?
[15:25] <rsalveti> om26er: yeah
[16:28] <bzoltan_> om26er_: do you know what is the situation with the UITK in the silo13?
[16:30] <jibel> bzoltan_, we'd like to wait the verdict on Qt 5.4.1
[16:32] <jibel> sil2100, I won't attend the landing meeting, from the list this morning, only 5 is remaining, everything else landed.
[16:32] <sil2100> jibel: ok, excellent
[16:32] <sil2100> No worries
[16:32] <jibel> sil2100, landed or testing is in progress
[16:33] <om26er_> bzoltan_, not really, I see jibel made a comment there.
[16:33] <om26er_> jibel, if I understand correctly, you don't want to land UITK till qt5.4.1 lands ?
[16:34] <bzoltan_> jibel: I thought that Mirv wants the UITK to land first on Vivid ... the silo was built against the
[16:34] <jibel> Mirv, ^ ?
[16:35] <bzoltan_> jibel: Mirv: i am confused .. I though that the Qt landing is blocked by the UITK and not the other direction
[16:37] <bzoltan_> jibel:  the silo13 UITK was built against the 5.4.0 Qt
[16:37] <bzoltan_> jibel:  Mirv: I do not fully understand why it would be blocked by the newer Qt
[16:38] <bzoltan_> Mirv:  or do you want to hold all landings what depend on Qt and the rebuild all of them with 5.4.1?
[16:38] <sil2100> bzoltan_: I think what jibel has in mind is that they want to first assess Qt 5.4.1 as it is now - if they sign-off UITK they might need to re-build the 5.4.1 silo and re-test
[16:47] <sil2100> huh
[16:47] <robru> heh
[16:47] <sil2100> Ok, I see the spreadsheet again ate some data (probably)
[16:48] <sil2100> hm, let me compare with the backups
[16:48] <robru> sil2100: dashboard looks sane, I think queuebot just barfed.
[16:49] <sil2100> robru: I just got an error in the spreadsheet and probably saw some data getting lost, so I want to double-confirm
[16:50] <robru> fair
[16:50] <sil2100> phew, no, it's just my local spreadsheet instance was busted
[16:52] <sil2100> Ok, but I still can't assign silos
[16:53] <sil2100> robru: can you try assigning a silo through the spreadsheet?
[16:53] <sil2100> I don't want to infinitely do this manually
[16:53] <robru> sil2100: which one?
[16:54] <sil2100> robru: any of the ones ready for a silo
[16:54] <robru> sil2100: ah, no I get fatal error
[16:54] <robru> sil2100: I like how the "details" window gives the same message verbatim without a single extra piece of info on that failure.
[16:55] <sil2100> Yeah, and the spreadsheet seems b0rken really badly
[16:55] <robru> sil2100: what other symptoms are you seeing?
[16:56] <dobey> cihelp: can you please upload https://jenkins.qa.ubuntu.com/job/generic-click-builder-14.09-armhf/16/artifact/output/com.canonical.payui_15.01.113_armhf.click to the store? thanks
[16:57] <cprov> dobey: let me find out how to do it
[16:57] <dobey> cprov: usually it's plars or fginther who do it
[16:58] <Ursinha> cprov: https://wiki.canonical.com/UbuntuEngineering/CI/Playbook#Uploading_a_click_app_to_the_click_store
[16:58] <cprov> Ursinha: thanks
[16:59] <sil2100> robru: it seems the spreadsheet is encountering fatal errors in various seemingly random places of the refreshSilosStatus function
[17:00] <robru> hm
[17:00] <sil2100> robru: I tried debugging it now and I got the error in 2 different places on 2 different runs
[17:00] <robru> sil2100: seems like some kind of transient/load issue with google servers. maybe just try turning the sheet off (eg, disable all scripts) for a couple hours?
[17:01] <om26er_> rsalveti, Hi!
[17:01] <sil2100> robru: I already turned the triggers to 30 minutes like a few hours ago
[17:01] <sil2100> Didn't help
[17:01] <robru> buh
[17:01] <sil2100> I turned them back to 5 minutes
[17:01] <robru> sil2100: well, that's it then. I'll start training the carrier pigeons.
[17:01] <sil2100> Ok, it seems google has issues in overall
[17:02] <sil2100> Since I again have HO problems
[17:02] <sil2100> The same authorization thing, I can't see or hear anyone
[17:02] <om26er_> rsalveti, while testing libhybris silo I found that sound in recorded videos is broken/robotic
[17:02] <cprov> dobey: done, please check if everything looks correct.
[17:03] <sil2100> om26er_: is it ok without the silo installed?
[17:03] <om26er_> sil2100, yes, rvr verified
[17:03] <cprov> dobey: i.e. -> The new version is being reviewed. Please check again at a later time.
[17:04] <dobey> cprov: yeah i can't see until it gets approved and is available as an update :)
[17:04] <cprov> dobey: uhm, who is responsible for the reviews ?
[17:06] <dobey> cprov: i'm not sure who all has privs for that. popey does, beuno and probably others on his team.
[17:07] <popey> hmm?
[17:07] <dobey> popey: you can review packages in the store no?
[17:07] <popey> doing payui now
[17:07] <cprov> popey: thanks
[17:07] <dobey> great, thanks
[17:08] <popey> done
[17:20] <rsalveti> om26er_: which device, which image?
[17:21] <om26er_> krillin, vivid-proposed 147
[17:21] <om26er_> rsalveti, ^
[17:25] <rsalveti> om26er_: and that only happens with the new libhybris? first testing with RTM now
[17:26] <om26er_> rsalveti, yes, I found the issue with the silo and rvr verified on vivid-proposed without silo
[17:30] <dobey> hmm, actually it might not show up as an update on my phone
[17:31] <rsalveti> om26er_: yup, found a bug, nice, could also reproduce on RTM
[17:31] <rsalveti> om26er_: will investigate, thanks for the feedback, will make sure to write down a wiki page describing what to be tested
[17:31] <rsalveti> and adding this one to the list
[17:31] <om26er_> rsalveti, thanks
[17:35] <dobey> oh, my mako shows it, cool
[17:41] <dobey> sil2100: so pay-ui is "landed" now. i tried to change the status in the spreadsheet to "Landed" but i am not sure if it actually saved it and did the magic
[17:42] <Mirv> bzoltan_: jibel: no strong opinion whether to land uitk first not not. qt silo can rebuild it if it lands.
[17:42] <Mirv> uitk is a no-change rebuild in the qt silo
[17:43] <robru> dobey: what magic? nothing gets triggered by setting the spreadsheet to 'landed'
[17:43] <Mirv> so it's only what matters to testing (both) silos that counts
[17:44] <dobey> robru: doesn't some script move things that are "Landed" to the archive page?
[17:44] <robru> dobey: when we run it manually, yeah. it doesn't get triggered by the status changing to "Landed"
[17:45] <dobey> robru: sure, there are way too many green boxes for it to be automatic. i just presumed there was a cron job somewhere
[17:46] <robru> dobey: nah we do that by hand. I just thought you were expecting something really magical to happen. if it says 'Landed' it's fine.
[17:46] <Mirv> jibel: bzoltan_: so, last week I was thinking that maybe uitk should just go in before QA starts testing Qt silo. now that they've been testing it since Friday evening, I guess they indeed may want to finish that properly before entering into new silos.
[17:51] <sil2100> robru: ok, seems like Steve removed the later meeting, I guess that means I can go to sleep after I'm done with work here ;)
[17:51] <robru> sil2100: sweet, time for breakfast then ;-)
[17:51] <dobey> robru: nah, i was just saying google was being fickle about me typing "Landed" in the status cell :)
[17:51] <sil2100> robru: hah, have fun ;)
[17:52] <robru> dobey: oh yeah the spreadsheet is a bit borked at the moment, google servers are just crapping all over it or whatever. if it's not saving your changes just try again later.
[17:53] <dobey> robru: ah ok. well sil2100 told me to ping him when it was done, so i was doing that too :)
[17:53] <dobey> anyway, go have some proper USian bacon or something
[17:53] <robru> hehe
[18:03] <om26er_> Kaleo, Hi!
[18:03] <om26er_> Kaleo, Looking here: https://code.launchpad.net/~fboucault/qtvideo-node/fix_rotate_z_order/+merge/252265
[18:04] <om26er_> seems the newly added tests are disabled ?
[18:09] <Kaleo> om26er_, yes
[18:09] <Kaleo> om26er_, can't get them to work on jenkins
[18:09] <Kaleo> om26er_, and it would not be much value: they only fail on device
[18:09] <Kaleo> om26er_, but at least the test exists
[18:09] <Kaleo> om26er_, and can be run manually
[18:10] <Kaleo> om26er_, and a corresponding manual test was added to the camera test plan
[18:10] <om26er_> Kaleo, hmm, it would be nice to have the automated test work
[18:10] <om26er_> Kaleo, did you get help from the CI guys ?
[18:10] <Kaleo> om26er_, I know, spent enough hours on it though
[18:10] <Kaleo> om26er_, some
[18:11] <om26er_> Kaleo, hmm, ok. Can you please report a bug to track that, so that we could track it
[18:11] <Kaleo> om26er_, track that the test is disabled?
[18:12] <om26er_> Kaleo, yes, so that we could enable it at some point
[18:13] <Kaleo> om26er_, https://bugs.launchpad.net/ubuntu/+source/qtvideo-node/+bug/1432766
[18:13] <Kaleo> done
[18:13] <bzoltan_> Mirv: jibel: so what is the verdict ... the silo13 is there for a week waiting for QA validation. I had time to update it, so it has all fixes what I had on my backlogs for the last week.
[18:13] <om26er_> super
[18:21] <robru> dobey: https://code.launchpad.net/~unity-api-team/unity-scopes-shell/scope-harness/+merge/250612 has this mp changed since your 'needs fixing' review? can't publish it until it's approved...
[18:22] <dobey> the mp hasn't changed
[18:22] <robru> hm
[18:23] <dobey> the other mp which adds the symbols changed, but i'm not happy with the "fix" that was done there either really, as it doesn't really fix the problem
[18:27] <robru> dobey: no worries, I won't publish. too bad pstolowski isn't on to get poked about that
[18:27] <dobey> yeah, nor is pete
[18:27] <dobey> hopefully michi will be on soon, and i can at least discuss with him about it
[18:34] <rsalveti> om26er: found the issue, will push another update in a few
[18:58] <om26er> rsalveti, great, can you share the diff
[19:12] <rsalveti> om26er: just reverting the change that caused this: http://paste.ubuntu.com/10611435/
[19:12] <rsalveti> om26er: just pushed a new package to the ppa
[19:13] <rsalveti> om26er: also started https://wiki.ubuntu.com/Process/Merges/TestPlan/libhybris
[19:14] <robru> mterry: kenvandine: anybody around for a packaging ack? https://ci-train.ubuntu.com/job/ubuntu-landing-018-2-publish/lastSuccessfulBuild/artifact/qtvideo-node_packaging_changes.diff/*view*/ got some new deps
[19:15] <om26er> rsalveti, that's good to see :)
[19:16] <mterry> robru, sure seems fine
[19:19] <robru> mterry: thanks
[19:44] <ToyKeeper> robru: Where do you keep the citrain bot code?  I'm trying to figure out the right place to put the qa silo bot code...
[19:45] <rsalveti> om26er: mind checking latest packages from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-004 ?
[19:45] <om26er> rsalveti, yes, I can start on it.
[19:45] <robru> ToyKeeper: lp:queuebot and it's controlled by stgraber. I'd advise against putting a lot of effort into that because I've started a port to a different bot but that stalled a bit
[19:46] <rsalveti> om26er: thanks
[19:48] <ToyKeeper> robru: This is an independent bot, but it's related...  Mostly, I'm looking for the right logical place to put it on Launchpad.  :)
[19:48] <davmor2> john-mcaleely: device tarball is good marked it so and then the spreadsheet went awol :)
[19:48] <davmor2> sil2100: ^
[19:48] <robru> ToyKeeper: oh just start a new project I guess.
[19:49] <ToyKeeper> That would explain why I haven't been able to find a central place for this stuff.
[19:52] <robru> ToyKeeper: well lp:queuebot is actually a new thing, stgraber used to just store that in a +junk branch and I couldn't even MP against it for a while.
[19:52] <ToyKeeper> robru: That's exactly what I'm fixing.  :)
[19:58] <robru> bfiller: https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/fix-1421411-uncrisscross/+merge/252789 just need this merge approved
[19:59] <robru> ToyKeeper: what irc bot framework do you plan to use for your irc bot?
[19:59] <bfiller> robru: done
[19:59] <robru> bfiller: thanks
[19:59] <ToyKeeper> robru: It's not an IRC bot.  I was hoping we could add features to queuebot if necessary.
[20:00] <robru> ToyKeeper: oh you said it was an independent bot
[20:00] <ToyKeeper> robru: For now, I'm just adding stuff to the silo/trello bot QA uses.
[20:01] <robru> ToyKeeper: yeah I'm not a fan of queuebot, it's ostensibly modular but you have to write a lot of your own threading boilerplate to make it work. I found a new bot framework called willie that seems to allow a significantly easier plugin architecture, but I only ported some of the plugins, and then the work got deprioritized.
[20:09] <ToyKeeper> Woot, we already have a project for misc qa tools.  Seems like a good place for it.
[20:12] <robru> alright, I'm off for lunch
[20:12] <robru> ToyKeeper: feel free to ping me if you have any questions about queuebot, I wrote the plugins specific to the train, stgraber wrote the larger framework.
[21:46] <rsalveti> robru: please don't yet land the new libhybris, want to coordinate the landing with the next image
[21:46] <robru> rsalveti: sure, i saw your name on it and assumed you'd land it
[21:47] <popey> cihelp bug 1431365 - see latest comment from carla - is there a firewall issue ?
[22:34] <fginther> popey, I recorded your issue, someone will probably have a look tomorrow