[03:41] <veebers> cihelp is anyone able to answer for me if a specific project is run in automated CI at all? I'm looking at the stock-ticker app
[03:42] <doanac> veebers: we aren't running it in daily image testing.
[03:42] <veebers> doanac: ok, thanks for the confirmation :-)
[03:48] <veebers> doanac: this may be a silly question, is there a why I can tell if a project is designed/intended to be built as a click package?
[03:49] <doanac> veebers: i don't have a good way. i just change our code when sergiusens tells me. Our list is maintained here: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/jenkins/testconfig.py
[03:49] <doanac> if an APTest has no "pkgs" then its basically a click-test
[03:49] <veebers> doanac: cool, thanks for the info
[08:20] <sil2100> Morning!
[08:37] <Mirv> helo sil2100
[08:44] <vila> sil2100, Mirv: hi
[08:44] <vila> sil2100, Mirv: what's up with waitonstacks jobs ?
[08:44] <sil2100> The stacks are spinning I see
[08:45] <sil2100> vila: it's a barrier to make sure the dependent stacks are built first
[08:45] <Mirv> vila: just normal builds
[08:45] <vila> sil2100: but they are red no ? http://10.97.0.1:8080/
[08:45] <sil2100> vila: so basically right now most of the stacks are waiting for qa and platform
[08:45] <Mirv> vila: when all stacks are started at the same time (like I did), the later stacks wait for the earlier stacks to complete
[08:45] <vila> oh, ok so, expected
[08:45] <sil2100> vila: well, don't look at the blinking states, those are old ones
[08:45] <Mirv> vila: the color of the blob is not updated until the whole stack's jobs are finished
[08:46] <vila> I'm asking because I
[08:46] <vila> meh
[08:46] <vila> I'm asking because I'm about to re-provision qa-radeon-7750 and don't want to do that at the wrong time
[08:46] <Mirv> I'm trying to restore normal order of things, for the hopeful near future when landing starts to be normal again
[08:47] <Mirv> vila: now it's not, 40mins ago would have been quiet :)
[08:47] <sil2100> ;)
[08:47] <Mirv> it'll take 3-4h to finish
[08:48] <vila> Mirv: am I wrong to think the only related jobs are http://10.97.0.1:8080/job/autopilot-trusty-daily_release/ and http://10.97.0.1:8080/job/autopilot-trusty-setup_otto/ ?
[08:48] <Mirv> vila: you may be entirely correct, but since I don't personally know I tend to be cautious.
[08:48] <Mirv> vila: I mean, redeploying stacks while they're running
[08:49] <vila> uh oh, qa-nvidia-gtx660 is de-provisioned from http://10.97.0.1:8080/job/autopilot-trusty-daily_release/configure too ??
[08:49] <Mirv> vila: since you need to add to the apmachines of every stack and redeploy
[08:49] <Mirv> vila: trusty uses autopilot-nvidia
[08:49] <vila> Mirv: oooooh, wait a sec, do you mean I should not touch the nodes in the job descriptions because you'll regenerate those ??
[08:50] <Mirv> vila: yes
[08:50] <Mirv> vila: so update lp:cupstream2distro-config instead
[08:50] <vila> Mirv: nah, I'd rather let you do that since I've never deployed those jobs and I'm likely to break something else at the wrong time ;)
[08:51] <Mirv> vila: that's ok, but it needs to be done when everything is calm
[08:51] <vila> Mirv: on the other hand, if you could point me to where the nodes are affected to the jobs for my own enlightenment ?
[08:53] <Mirv> vila: maybe approve as well :) https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/add_qa-radeon-7750_back/+merge/194465
[08:53] <vila> Mirv: something doesn't match... I've put a comment at http://10.97.0.1:8080/job/autopilot-trusty-setup_otto/ so presumably affecting nodes is done in jenkins so that job is not generated  ?
[08:53] <sil2100> Mirv: is it safe to re-add radeon now ;) ?
[08:53] <Mirv> sil2100: vila wouldn't be re-provisioning it otherwise? ;)
[08:54] <Mirv> sil2100: at least the previous glamor problem is fixed
[08:54] <Mirv> vila: I only know of this cuupstream2distro-config update way of provisioning, and it has been enough before
[08:54] <vila> sil2100, Mirv: yup, the glamor problem is fixed but I kept qa-radeon-7750 to debug/fix the kernel issue
[08:54] <Mirv> vila: is the kernel issue resolved now?
[08:55] <vila> Mirv: yes, so some other hosts (in my notes) will need to be upgraded to the newer trusty kernel too, I'll do that once we're done on that one
[08:56] <sil2100> :)
[08:56] <sil2100> \o/
[08:56] <sil2100> Mirv: I'll also review your branch if you don't mind!
[08:57] <Mirv> vila: excellent news!
[08:57] <Mirv> sil2100: I certainly don't mind
[08:57] <Mirv> I just need to remember to deploy it in the afternoon
[08:57] <vila> Mirv: ok, so that mp of yours is for http://10.97.0.1:8080/job/autopilot-trusty-daily_release. jibel may know about whether http://10.97.0.1:8080/job/autopilot-trusty-setup_otto is generated or not ?
[08:58] <vila> and this job also needs to stop using magners-orchestra IP address, let me find the right name to use
[08:59] <Mirv> vila: that's true, the setup otto job may be a different story
[09:00] <vila> 'q-jenkins' is the name
[09:01] <vila> Mirv: well, I'll update the job again on the assumption that you did some re-deploy at least to de-provision and that job wasn't touched then (I *did* update it manually at the time)
[09:01] <vila> ... more paperwork to keep track of all that ;)
[09:02] <vila> vila: rejoice man, first you document, then you write a test, then it's automated, you spend your whole life doing that  !
[09:02] <jibel> vila, this job is created manually when a new release open
[09:02] <vila> jibel: Thanks !
[09:02] <jibel> vila, it's a copy of the previous release followed by an update of the nodes
[09:03] <jibel> vila, the nodes themselves must be upgraded manually anyway
[09:03] <vila> jibel: double thanks, now that you mention it, I'm pretty sure I have notes about that from when we setup trusty with didrocks
[09:05] <jibel> vila, https://wiki.canonical.com/UbuntuEngineering/CI/NewRelease
[09:05] <vila> Mirv, sil2100: job updated
[09:06] <vila> jibel: hehe, yes ;)
[09:06] <Mirv> vila: thanks!
[09:06] <vila> jibel: that's the notes I was referring to :)
[09:07] <vila> ha ha, and there is a note about "'-proposed' is not enabled for trusty for now, this needs to be revisited in a week or two. "
[09:09] <sil2100> vila: thanks :)
[09:28] <sil2100> Mirv: qa stack check job failed because of a new ibus upload - this seems to be temporary and will probably go away with tomorrow's image
[09:28] <sil2100> Mirv: since it wants to upgrade ibus which is not in packages:
[09:29] <sil2100> Mirv: I guess we could fix that in cu2d-config, but let's remember to remove that later on - or we can modify it directly in jenkins, but we need to remember about it after redeploying the reprovisions
[09:29] <sil2100> I guess adding to cu2d-config is safer not to forget
[09:30] <sil2100> Mirv: I'm doing that if anything
[09:30] <sil2100> Mirv: hangout!
[09:30] <sil2100> ogra_: vila: coming?
[09:30] <sil2100> asac: ?
[09:31] <vila> omw
[09:34] <asac> sil2100: hi
[09:34] <asac> sil2100: coming if you want... do you?
[09:35] <asac> :)
[09:35] <sil2100> asac: I don't know! Not much to say today! ;)
[09:52] <sil2100> Mirv: https://code.launchpad.net/~sil2100/cupstream2distro-config/add_ibus_temporarily/+merge/194472
[09:55] <sil2100> asac: you were breaking up audio-wise a bit ;)
[09:55] <Mirv> sil2100: yep
[10:09] <asac> sil2100: thx :)
[10:10] <asac> sil2100: so on the pad ... who is working on what entry there?
[10:12] <asac> i assume each entry is worked on by an upstream engineer?
[10:12] <asac> sil2100: let me know which ones you feel are not having the needed attention there
[10:13] <sil2100> asac: I think thomi was updating that pad, we would have to probably update it to include which is worked on by which person
[10:16] <vila> sil2100, asac: IIUC, based on his most recent email, thomi is now in vacations and unreachable
[10:50] <vila> Mirv, sil2100: qa-intell-4000 and dx-autopilot-nvidia are now running the up to date kernels
[10:51] <sil2100> \o/
[10:55] <asac> sil2100: right. you have that info?
[10:56] <asac> sil2100: is it the QA team working on those items? if so i can check with jfunk when he is on
[11:05] <Mirv> vila: great!
[13:11] <Mirv> UI Toolkit API breakage fix merged and I built the package now, I can start testing and then pass the ball to robru / kenvandine
[13:16] <sil2100> \o/
[13:16] <sil2100> Mirv: I see the stack got re-run, got me scared for a moment
[13:16] <sil2100> Since I thought the AP jobs are hanged up again, but then I saw it's just a re-run
[13:17] <sil2100> Anyway, stacks starting too look nice, I love the look of yellow on the main view
[13:17] <sil2100> *to
[13:17] <sil2100> Indicators and HUD had some issues, but for instance a re run of indicators might fix some things
[13:17] <sil2100> (I'll do that now)
[13:22] <Mirv> sil2100: yep, me too
[13:22] <Mirv> sil2100: do you know of any app updates/fixes so far?
[13:27] <jdstrand> asac: who do I talk to about a landing ask?
[13:27] <jdstrand> asac: is it still the same group of people?
[13:28] <ogra_> jdstrand, still the same spreadsheet and the same people ...
[13:28] <jdstrand> ok, well, I added an ask yesterday but no comments on it yet
[13:28] <ogra_> though the current word is, only stuff that improves the image to go gree on the dashboard is allowed to enter
[13:28] <ogra_> *green
[13:29] <jdstrand> yeah-- I realize I'm core-dev and have another path, but thought that was the case atm, which is why I added it
[13:29] <seb128> ogra_, what if the updates don't help the image to go green but included fixes the desktop needs?
[13:30] <ogra_> seb128, then it needs to prove it doesnt regress touch and can go in
[13:30] <seb128> k
[13:30] <seb128> so it's not only stuff that help getting green ;-)
[13:30] <seb128> good
[13:30] <sil2100> Mirv: some, yes, for instance we can release mediaplayer-app and it will be green then
[13:30] <jdstrand> that would be true of mine btw
[13:30] <jdstrand> ogra_: does that mean it doesn't need an ask?
[13:31] <ogra_> seb128, well, its "we look out for regressions quite heavily so the image can be green on monday"
[13:31] <seb128> jdstrand, I guess it means you should test the update on the touch image to make sure it keeps working and then upload
[13:31] <ogra_> yeah
[13:31] <ogra_> run the tests with your change installed on a touch image
[13:31] <jdstrand> ok
[13:32] <ogra_> and note down that you did this on the spreadsheet ... that will speed it up
[13:33] <Mirv> sil2100: ok, so are you releasing it then?
[13:33] <asac> jdstrand: today go for sil ... we should work this into vanguard at some point to make it easy
[13:33] <sil2100> Mirv: yesss
[13:33] <asac> ANY question -> vanguard
[13:33] <Mirv> sil2100: if the uitoolkit is fine, ogra_ can probably do a new image build somewhere around your evening meeting
[13:34] <ogra_> yeah, just ping me when everything is ready
[13:34] <Mirv> I'll EOD somewhere during the next hour, but will keep on running AP:s against uitoolkit until then
[13:34] <Mirv> (and update the landing plan)
[13:35] <sil2100> Mirv: thanks!
[13:39] <sil2100> Mirv: strange things happened to the friends stack - the check job failed even though both machines ran all the tests successfully it seems
[13:39] <sil2100> At least I didn't see any test skipped
[13:40] <sil2100> Mirv: absurd, it says that for intel it's: "delta | dtotal:   -1 | tskip:   +0 | dfailures:   +0", even though there's just one test and that one test passed
[13:45] <asac> sil2100: so, did we consider anything beyond AP fixes?
[13:46] <asac> (in the end)
[13:46] <Mirv> sil2100: that's normal
[13:46] <Mirv> sil2100: it means that one test was removed I think?
[13:46] <Mirv> sil2100: we've seen it before
[13:47] <sil2100> asac: only if a given feature is super-tested not to cause any regressions and test failures, but prioritizing releases related to AP
[13:47] <sil2100> Mirv: but only from one machine?
[13:47] <sil2100> Mirv: nvidia is fine, +0, while intel has the same number of tests ran but it says -1 ;)
[13:47] <asac> sil2100: well, i was wondering if we actually ended up DOING any landings beyond AP fixes today :)
[13:47] <sil2100> (maybe the check was aborted on one platform)
[13:48] <jdstrand> thomi: hi! ev asked me to talk to you about including /var/log/syslog in the artifacts. apparmor messages are in /var/log/syslog so including it would be helpful to see if apparmor is causing failures
[13:48] <sil2100> asac: not really, SDK might have something in it beyond AP, but we're not releasing anything else today for now
[13:48] <jdstrand> thomi: is telling you enough? should I file a bug?
[13:49] <fginther> morning
[13:50] <sil2100> Morning
[13:50] <sil2100> jdstrand: it's best if you e-mail him with anything that needs to be done, but AFAIK he's also on holidays from now on
[13:51] <jdstrand> ok
[14:33] <asac> sil2100: cool. nice
[14:33] <asac> sil2100: how many things do we anticipate to be better? any of those PAD components where you haven't heard anything yet?
[14:33] <asac> no sign of progress or non-progress that is :)
[14:34] <asac> ev: do we have a public wiki area for the bigger CI team?\
[14:36] <ev> asac: not yet, I'll get on that
[14:54] <asac> ev: would be nice if you could pick the top level hierarchy so i could start drafting stuff in there
[14:54] <asac> e.g. CI landing practices etc.
[14:55] <asac> would it be wiki.ubuntu.com/CI ?
[14:55] <asac> or CITeam?
[14:55] <asac> or ContinuousIntegrationEngineering ?
[14:55] <ogra_> ContinuousIntegrationEngineeringTeamHomePageOnTheWiki ?
[14:56] <ev> already creating wiki.ubuntu.com/CI :)
[14:56] <ogra_> :)
[14:56] <ev> we're first, so we win the short URL game
[14:57] <asac> guess that means that the concept of CI was underdeveloped in the debian/ubuntu ecosphere
[14:57] <xnox> ev: i like the CIA - CI Airline ;-)
[14:57] <asac> lol
[14:57] <asac> thats a good one
[14:58] <Mirv> kenvandine: robru: are you up?
[15:00] <ogra_> asac, i think you should discuss that with the Name Space Approval team under wiki.ubuntu.com/NSA
[15:00] <ogra_> :)
[15:00] <kenvandine> Mirv, i am, but in a meeting
[15:01] <ev> asac: http://wiki.ubuntu.com/CI - edit away :)
[15:05] <sil2100> Need to change locations, brb
[15:13] <Mirv> kenvandine: robru: ok passing the ball to you, please check Landing Plan. all UI Toolkit + all but 1 AP tests look fine, and I've an ack from seb_128 too. I've difficulties with ubuntu-filemanager, so can you test you get the same results with and without upgrading UI Toolkit? I can't seem to match the dashboard results, but that may be because they execute tests differently.
[15:14] <Mirv> kenvandine: robru: if/when you're satisfied, please release ui-toolkit from cu2d
[15:15] <kenvandine> Mirv, ok, thanks
[15:15] <kenvandine> i can't test today... my mako is out of commission :/
[15:15] <kenvandine> but maybe robru can
[15:15] <Mirv> ok, robru then, and/or ping sil2100 when he's back online
[15:16] <Mirv> the fix is important anyhow, to fix settings panels (and others), so I doubt even if file manager would have some small problem it's worth not publishing
[15:16] <Mirv> it's more likely you'll find out that you get same results with and without upgrading but just that the tests are shaky enough to not get similar results than at dashboard
[15:16] <kenvandine> my usb cable got hooked on the arm of my chair, i turned to get up and boom... it got pulled off my desk and happened to hit the bottom of the chair instead of the soft carpet :(
[15:17] <Mirv> kenvandine: :S
[15:17] <kenvandine> and my android phone had a dead battery... hadn't used it in a month now :)
[15:18]  * popey removes kenvandine's geek credentials for having only one usb cable
[15:18] <kenvandine> ha... i have dozens!
[15:19] <kenvandine> popey, you've broken a few phones... are they fixable?
[15:19] <kenvandine> n4
[15:19] <popey> hah
[15:19] <popey> thanks for reminding me
[15:19] <kenvandine> it's a tiny crack... but top half the screen doesn't work at all... and right edge swipes don't work
[15:19] <popey> yes, I have had my n4 repaired by an official LG service centre
[15:20] <popey> cost $$$
[15:20] <kenvandine> is it worth the repair? or replacement is better?
[15:20] <popey> the process of having a google lg phone repaired has made me a) never want to buy a google product again, b) never want to buy an LG product again
[15:20] <popey> other than that, it's fixed
[15:20] <popey> well, this was some months back, cost me £120, whatever that is in your monopoly money I don't know
[15:21] <kenvandine> haha
[15:21] <kenvandine> of course now you can't buy an n4... but a month ago they costed $200
[15:21] <popey> To the ebays!
[15:21] <kenvandine> ah, so the repair was nearly $200 ... not worth iut
[15:21] <kenvandine> it
[15:22] <kgunn> kenvandine: cracked screen right edge swipe not working....reminds me of a bug i got years ago when i was audio guy "put phone underwater, now i can't hear my ringtone" :)
[15:22] <kenvandine> haha
[15:23] <kenvandine> it's really hard to use ubuntu touch without edge gestures
[15:23] <kenvandine> oh, and i can't get the bottom edge swipes either
[15:23] <kenvandine> which is weird
[15:23] <kenvandine> because it does get the touches there
[15:23] <kenvandine> just not edge swipes
[15:26] <seb128> whoever does images validation, while the current daily ubuntu-ui-toolkit update fixes some of the issue over the trusty version, it still has regressions
[15:26] <seb128> just filed bug #1249386 (that makes the ringtone selection screen being empty)
[15:27] <kenvandine> seb128, is that a new regression?
[15:27] <seb128> kenvandine, define "new", it's a regression from saucy
[15:28] <seb128> kenvandine, the previous trusty version had the api incompat change that I can't say if that bug was there
[15:28] <seb128> kenvandine, in fact it's not listitem specific, it was already buggy with the current trusty version
[15:28] <seb128> it displays those
[15:29] <seb128> QML Flickable: Cannot anchor to an item that isn't a parent or sibling.
[15:29] <seb128> Binding loop detected for property "contentHeight"
[15:29] <seb128> no such warning with the saucy toolkit
[15:29] <seb128> it might be my code being stupid but I'm not sure what is wrong is there...
[15:33] <kenvandine> ok
[15:38] <tedg> Can we turn on ddebs for this PPA?  https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages
[15:39] <cjwatson> I believe that if you do that you'll break copying into the archive
[15:39] <cjwatson> But check with somebody who's dealt with this before; it's delicate
[15:39] <tedg> Do we copy into the archive from there?
[15:39] <cjwatson> (infinity might remember)
[15:39] <cjwatson> We sure do
[15:39] <cjwatson> Lots and lots
[15:39] <tedg> Ah, I didn't realize that was the same PPA.
[15:40] <tedg> I just viewed it as "a place where the package are actually up-to-date" :-)
[15:40] <asac> tedg: (unfortunately) it is both
[15:41] <tedg> asac, We could kill the asinine "landing plan" and then we could separate them!  \o/
[15:47] <cjwatson> Well, also unfortunately ddebs are delicate.  ddebs-in-LP will fix this, once we're happy the librarian can scale to it
[15:47] <cjwatson> (I also might be wrong about exactly how delicate they are - I just remember something like this breaking previously)
[15:50] <kenvandine> seb128, i confirmed that regression that broke the sounds page was in image 15 too
[15:50] <seb128> kenvandine, "good"
[15:50] <kenvandine> so landing what we have is at least an improvement
[15:51] <kenvandine> seb128, it was really hard to test that...
[15:51]  * kenvandine is frustrated
[15:51] <kenvandine> damn touch screen!
[15:52] <asac> kenvandine: did someone else regress you? or was it yourself?
[15:52] <kenvandine> upstart-app-launch to start it, then turn to landscape so i could navigate to the sound page
[15:52] <asac> e.g. is it self-frustration? :)
[15:52] <kenvandine> asac, no... busted mako
[15:52] <ogra_> cracked screen ?
[15:52] <asac> kenvandine: what bustage on mako?
[15:52] <kenvandine> the usb cable got hooked on the arm of my chair... and when i turned to stand up it pulled the phone off my desk :/
[15:53] <kenvandine> tiny crack...
[15:53] <asac> ah ok so its micro/self-frustration :)
[15:53] <kenvandine> but half the screen doesn't work
[15:53] <ogra_> the N5 is so much better HW wise ...
[15:53] <kenvandine> and no edge swipes
[15:53] <asac> thats pretty good. i never had a half working screen
[15:53] <ogra_> not like a raw egg
[15:53] <asac> only all or nothing :)
[15:53] <kenvandine> ha
[15:53] <kenvandine> it barely looks broken!
[15:53]  * ogra_ still have the half working one upstairs 
[15:54] <kenvandine> it happened to hit the bottom of my chair, near the wheels
[15:54] <ogra_> sadly its only the top of the screen that works on mine
[15:54] <kenvandine> 1/4" to the side and it would have hit the soft carpet
[15:54] <kenvandine> it is very hard to use ubuntu touch without edge swipes :(
[15:54] <ogra_> yeah
[15:54] <asac> thats always how it happened... usually you try to catch it and just give it the kick in the air
[15:54] <kenvandine> and i can't expand installed apps in the shell :)
[15:54] <asac> that made it not go 1/4" further to the right
[15:54] <ogra_> asac, ++
[15:56] <asac> kenvandine: cant you rotate screen by 180?
[15:56] <kenvandine> that was the only way i could get to the ring tones
[15:57] <kenvandine> doesn't help in the shell, since it doesn't rotate
[15:57]  * kenvandine needs to get a replacement quickly
[15:58] <asac> kenvandine: you could also go to a shop and have them replace the screen... usually works pretty well
[15:58] <asac> just dont try on your own (i did that and it turned into a multi-week process :))
[15:59] <asac> cyphermox: hey, can i try the threshold fix for roaming on saucy? or should i go for trusty rather?
[15:59]  * asac ponders just dist-upgrading to the next great thing in the spirit of daily releases
[16:07] <cyphermox> asac: trusty
[16:10] <ogra_> go for it !
[16:10] <ogra_> its great if it works
[16:44] <asac> ogra_: the IF is the question
[16:44] <asac> anyway ... /me has EOD and kicks it off
[16:44] <asac> hmm. should i use update-manasger? or go with raw apt-get?
[16:45]  * asac goes for ue\
[16:45] <asac> om
[16:45] <asac> um
[16:45] <asac> :)
[16:45] <asac> hehe
[16:45] <ogra_> thing
[16:45]  * asac wants system-images for desktop :)
[16:46] <asac> thats for sure
[16:46] <ogra_> that will need a lot of convincing work and good PR
[16:49] <popey> yeah, we're good at PR
[16:49] <ogra_> lol
[16:51] <sil2100> Daaaamn
[16:51] <asac> see i need to first restart because i got a kernel upgrade... only then i can really try a dist-upgrade hoping that nothing new came into -updates
[16:51]  * asac reboots
[16:51] <sil2100> Barely made it for the meeting, phew
[16:51] <sil2100> Traffic on Fridays evening is terrible
[16:58] <robru> sil2100, Mirv, kenvandine: hi, just up. yep my mako is fine and I'm ready to test things
[16:58] <sil2100> robru: morning!
[16:59] <sil2100> Let's do a quick meeting now, just a summary maybe and then continue on releasing/testing
[17:01] <sil2100> kenvandine: meeting!
[17:02] <sil2100> cyphermox: will you be coming as well? Not much we have to say though
[17:40] <xnox> sil2100: not sure if you are around. You know the .zip with armhf debs that jenkins produces?
[17:40] <xnox> sil2100: can we add more steps that include some additional debs into that zip, which are downloaded with "apt-get download" during the build?
[17:52] <kenvandine> sil2100, whoops... missed the meeting
[18:14] <asac> xnox: whats the use-case?
[18:15] <asac> (just curious as always :))
[18:17] <xnox> asac: it needs to include new dependencies, not otherwise available on the image.
[18:18] <sil2100> xnox: which jenkins do you mean?
[18:19] <xnox> sil2100: sorry for not being clear, the upstream-merger job that generated armhf.debs in a zip and posted comment to the merge proposal.
[18:20] <sergiusens> xnox, the zip is just the collection of artifacts from the workspace
[18:20] <sil2100> xnox: ah, let's ask fginther if it's possible, but I guess it's all just a matter of configuration
[18:21] <sergiusens> xnox, something like result/**/*.deb iirc
[18:21] <xnox> sil2100: do you have a pointer to the sources of the job? I'd want to look at what it does.
[18:21] <xnox> sergiusens: ah, i see.
[18:21] <sergiusens> you can , separate more matches
[18:21] <sil2100> xnox: I think it would be safest to ask fginther, and I see sergiusens knows more about this as well
[18:22] <sergiusens> and you can script some logic to collect them if you want
[18:22] <sergiusens> sil2100, I started it ;-)
[18:22] <sil2100> I'm not too much into the upstream-merger :)
[18:22] <sil2100> Oh, so ever better!
[18:22] <sergiusens> sil2100, it was to make MR reviewing easier and for the reviewer to be able to manually test
[18:23] <sergiusens> was one of our good practices for the phablet team
[18:23] <xnox> sergiusens: I see that it fetches the hooks from personal junk branches in the build-log =/ so nobody else can modify a broken hook or add a feature.
[18:23] <sil2100> It is useful indeed, I even asked for enabling that for the u-s-s, since it's really easy to do code reviews then
[18:23] <fginther> xnox, so instead of just the deb files generated by the build, you want the debs that are dependencies?
[18:24] <sergiusens> xnox, personal junk branches? where?
[18:24] <xnox> fginther: well, something specific. If -proposed is enabled, and a given .deb file dependencies are not satifiable with just release pocket, check which dependencies are needed from "-proposed", $ apt-get download those, and include in the artifacts.
[18:24] <xnox> sergiusens: https://jenkins.qa.ubuntu.com/job/ubuntu-keyboard-trusty-armhf-ci/49/consoleText    see that it fetches hooks from +junk
[18:25] <sergiusens> xnox, well that's an fginther temporary thing I would suppose
[18:25] <xnox> fginther: maybe move +junk proposed hook to a more permanent / team managed place.
[18:25] <sergiusens> xnox, all other hooks are in pbuilderjenkins
[18:26] <fginther> xnox, right, that hook needs to be added to pbuilderjenkins
[18:26] <fginther> just needed a quicker fix
[18:26] <sergiusens> xnox, lp:pbuilderjenkins; but you still need someone in ci to enable your hook if it's not used yet
[18:26] <xnox> sergiusens: fginther: right, i'll look at lp:pbuilderjenkins and will check if I can add an extra hook. Thanks a lot.
[18:27] <sergiusens> xnox, http://bazaar.launchpad.net/~private-ps-quality-team/pbuilderjenkins/trunk/files/head:/hooks/
[18:27] <xnox> (proof of concept at least.)
[18:27] <fginther> xnox, If you can create a hook to collect the deb files, then we can just add it to those build configs that need it. That should meet your needs
[18:28] <xnox> sergiusens: why is that owned by a private team?
[18:28] <sergiusens> fginther, are we keeping pbuilderjenkins or is migration to sbuild happening or building on PPAs?
[18:29] <fginther> sergiusens, the plan is to migrate to building in PPAs
[18:29] <sergiusens> xnox, I wish I could answer that; but I don't know
[18:29] <xnox> sergiusens: fginther: do we really have proprietary hooks to jenkin jobs against _public_ projects?!
[18:29] <sergiusens> fginther, how are collecting test result going to be managed? asking out of curiosity
[18:30] <sergiusens> xnox, the answer to that is no
[18:30] <xnox> sergiusens: ok. =)
[18:30] <fginther> xnox, sergiusens, there maybe hooks for accessing private PPAs, I'll check. As a workaround, I can add xnox to the group
[18:30] <sergiusens> xnox, I guess it was just private because the ps quality team was a private one
[18:30] <sergiusens> not much more than that
[18:30] <sergiusens> fginther, there aren't
[18:31] <sergiusens> they are dynamically created
[18:31] <fginther> sergiusens, not even in the bzr history?
[18:31] <sergiusens> with launchpadplugin
[18:31] <sergiusens> fginther, there shouldn't iirc
[18:31] <sergiusens> fginther, that's why we had the extrahoooks directory
[18:32] <sergiusens> fginther, hmmm, I'm wrong now that you mention that
[18:32] <fginther> xnox, you should now have access to that branch
[18:32] <sergiusens> fginther, just regenerate the passwords for all the ppa's ps-jenkins owns; should be fine
[18:34] <fginther> sergiusens, ack, I can do that while the systems are down this weekend
[20:02] <fginther> kgunn, so are you just proposing MPs from the development branch to lp:mir now (instead of using the pull job)?
[20:02] <kgunn> fginther: :)
[20:02] <kgunn> fginther: its like a soap opera...tune in every day for a diff method
[20:03] <kgunn> fginther: so now...yes...we are back to merging
[20:03] <fginther> kgunn, oh, sorry to step into this if it's still changing
[20:03] <kgunn> fginther: however, we are branching from dev branch to capture a specific rev
[20:03] <kgunn> fginther: its not that challenging...just trying to balance all the aspects to make a bunch of different people happy
 didrocks & duflu :)
[20:04] <fginther> kgunn, /me understands
[20:04] <kgunn> fginther: yeah...so now, we branch the dev-branch, then propose that to the trunk
[20:04] <kgunn> rather than a straight up merger from dev-branch to trunk
[20:05] <kgunn> that's where we are at now...
[20:05] <kgunn> pull had some problem with history....didn't fully follow
[20:05] <fginther> kgunn, ok. so now that MPs are being proposed against lp:mir, the normal autolanding machinery should be working
[20:05] <kgunn> but seemed to point to a bug in pull
[20:05] <kgunn> fginther: yeah...we have one up...but didrocks asked that we wait until monday to land them all
[20:07] <fginther> kgunn, ok. no worries, I mainly wanted to check in and make sure that nothing was missing from the CI side
[20:07] <kgunn> fginther: hey now that you ask...
[20:07] <kgunn> fginther: i do have a couple of tests i want to include into our CI runs
[20:08] <kgunn> fginther: the first is just our demo clients which actually do report frame rate
[20:08] <kgunn> fginther: but robotfuel is working on those
[20:08] <fginther> kgunn, right, we've been discussing that
[20:08] <kgunn> fginther: the second tests i'd like to enable are 4 specific integration tests
[20:08] <kgunn> fginther: which are currnetly switched off in the rules
[20:09] <robotfuel> kgunn: I have a branch that packages the integration tests so we can run them in ci
[20:09] <kgunn> fginther: they are 4 tests that could really help to make sure we don't regress...on the specific hw (galaxy, nexus4, nexus7, nexus10)
[20:09] <robotfuel> kgunn: it's in progress :D
[20:09] <kgunn> robotfuel: woohoo
[20:10] <robotfuel> kgunn: they are the tests in /tests/integration-tests?
[20:11] <fginther> kgunn, if anything new comes up, feel free to file a bug to request it.
[20:11] <kgunn> robotfuel: its the one in test/integration-tests/client (akak test_client_render)
[20:11] <robotfuel> kgunn: ok we are on the same page
[20:12] <fginther> kgunn, I can't promise anything quickly due to the planned CI updates, but it's good to know what to plan for
[20:12] <kgunn> robotfuel: and then 3 others in test/integration-tests/graphics/andrioid
[20:12] <robotfuel> kgunn: I was going to run all the integration tests in ci
[20:12] <kgunn> robotfuel: which are test_buffer_integration, test_display_integration & test_internal_client
[20:13] <kgunn> robotfuel: right these are ones that are specifically android/ARM and need to be run on the devices we support
[20:13] <kgunn> robotfuel: devices we support with mir on ARM today are galaxy-nexus & nexus4
[20:13] <kgunn> robotfuel: but....we'll soon include nexus7 & nexus10 to that list
[20:14] <kgunn> robotfuel: ...and we'll _eventually_ (like very soon) drop galaxy_nexus
[20:15] <robotfuel> kgunn: ack, I am working on additions to phablet-test-run as we speak so we can run them. the same thing is needed to run the mir demos
[20:17] <kgunn> robotfuel: excellent - to be clear, on the integration tests, its really those 4 i listed above running on the form factor hw that should be priority (after the demo clients)
[20:17] <kgunn> robotfuel: its not that i don't care about _all_ integration tests...i just care for those 4 a little more :)
[20:18] <robotfuel> kgunn ack
[20:19] <kgunn> robotfuel: thanks man...that'll be great!
[20:50] <kenvandine> Ran 97 tests in 522.959s
[20:50] <kenvandine> OK
[20:50] <kenvandine> robru, uitk with that toolbar branch
[20:51] <kenvandine> ^^
[20:51] <robru> sweet
[20:51] <kenvandine> robru, that branch is approved, but not merged yet
[20:51] <robru> kenvandine, branch is approved, should land soon. i'll build & publish it asap
[20:51] <robru> hehe
[20:51] <kenvandine> thanks
[20:57] <sil2100> \o/
[20:58] <sil2100> robru, kenvandine: thanks for picking this up guys
[20:58] <robru> sil2100, you're welcome!
[20:58] <sil2100> robru, kenvandine: can you poke ogra_ for a new image once you get everything in what you think is needed?
[20:58] <robru> sil2100, ok
[20:58] <robru> ogra_, how much longer you around for?
[20:58] <sil2100> Since I guess notes-app, webbrowser-app and mediaplayer-app are in the archives
[20:59] <kenvandine> sil2100, i'll be heading out in about an hour, better for robru
[20:59] <ogra_> robru, a few hours, i wont monitor IRC but will notice pings on my lappie next to me
[21:00] <robru> ok
[21:00] <ogra_> so once you have your ducks in order just give me a ping
[21:00] <robru> ogra_, will do. should be soon
[21:00] <ogra_> k
[21:01] <sil2100> kenvandine: ok
[21:01] <sil2100> See you next week everyone, have a nice weekend \o/
[22:37] <Kaleo> hi sweethearts
[22:37]  * kenvandine hugs Kaleo
[22:37] <Kaleo> :D
[22:38] <Kaleo> kenvandine, there is one MR happroved for landing that settings needed: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/page-parentage/+merge/194587
[22:38] <Kaleo> kenvandine, other than that everything is landed
[22:38] <kenvandine> awesome
[22:39] <kenvandine> robru was working on getting trunk after the toolbar locked branch landed
[22:39] <kenvandine> we tested that one
[22:39] <kenvandine> but would be nice to get the fix settings needed in too
[22:39] <Kaleo> great
[22:39] <Kaleo> yes
[22:39] <kenvandine> but... i'd rather get the current fixes in regardless
[22:40] <kenvandine> at some point the CI infra is going down
[22:40] <Kaleo> right
[22:40] <kenvandine> for the data center work
[22:40] <Kaleo> let's do it before it goes down
[22:40] <robru> kenvandine, sdk stack is building. can build it again after that one lands i guess
[22:40] <kenvandine> robru, i'd say lets publish it twice
[22:40] <kenvandine> this build then the next one
[22:40] <robru> kenvandine, yeah, to be safe
[22:43] <robru> kenvandine, ooooh, publishing now!
[22:43] <kenvandine> woot
[22:43] <kenvandine> Kaleo, ^^
[22:44] <Kaleo> hehe
[22:44] <Kaleo> how do I TEST
[22:44] <Kaleo> bla blou bli
[22:44] <robru> well it'll take a bit to get into the archive
[22:44] <Kaleo> k
[22:44] <kenvandine> robru, when that next branch merges can you kick off another?
[22:44] <kenvandine> i need to take off
[22:44] <robru> kenvandine, yep
[22:44] <kenvandine> awesome
[22:44] <kenvandine> thx
[22:45] <kenvandine> that'll make seb128 happy
[22:45] <robru> heheh
[22:45] <kenvandine> robru, have a great weekend!
[22:45] <robru> kenvandine, you too!