[00:31] <robru> I'm off for dinner, bbl
[01:58] <dobey> Kaleo: well, when we get mirvfb, the ubuntu-touch-session setup script can probably do all the stuff much nicer. if you're using adt-run run locally under qemu, you can use it to get an xvfb setup to run the tests under.
[02:05] <imgbot> [03:15] <imgbot> [03:15] <imgbot> [05:23] <Mirv> I will not allow myself be turned into framebuffer, even though lately I've seen increasingly highlights about that
[05:26] <robru> Mirv: I think you'd make a great framebuffer!
[06:06] <Mirv> don't vote for me, vote err.. for example sil2100fb sounds good!
[09:32] <sil2100> huh
[09:32] <sil2100> Authentication issues
[10:04] <ogra_> sil2100, we had an unexplainable failure with the emulator with the last image build, i'll kick another vivid image to see if it happens again
[10:05] <sil2100> ogra_: ok, thanks
[10:15] <Mirv> sil2100: I don't find ww13 bugs that would be clearly in Qt (although of course still possible that 5.4.1 would help). From our LP bugs Qt 5.4.1 PPA fixes bug #1430337 (which makes greyback_ happy) and Device Pixel Ratio improvements that mzanetti needs for his SVG work in progress, and then of course any of the crasher/regression/leak/networkdisconnection fixes from https://qt.gitorious.org/qt/qtbase/source/dist/changes-5.4.1 that affect us, whet
[10:16] <Mirv> And then Kubuntu wants a certain text rendering fix, and XCB related fixes.
[10:16] <Mirv> that's about the summary "what it's needed for"
[10:19] <Mirv> oh right and the Qt Wayland support.
[10:20] <imgbot> [10:22] <jibel> rvr, I confirm that I received the notification from gmail but only the indicator changed, no sound, vibration or anything else
[10:22] <rvr> jibel: This is the bug I opened https://bugs.launchpad.net/webapps-core/+bug/1431517
[10:23] <sil2100> Mirv: ok, well, let's try to convince Pat about that it's relatively safe then
[10:24] <sil2100> Although for that I would prefer us to have a QA sign-off already
[10:24] <jibel> dbarth_, can someone havea  look at bug 1431517, it's a potential regression in rtm/256
[10:25] <Saviq> cihelp, hey, any idea why errors.u.c shows only one thread in "Thread Stacktrace"  https://errors.ubuntu.com/bucket/?id=/usr/bin/unity8-dash%3A7%3AtestAndSetRelaxed%3AtestAndSetAcquire%3AtestAndSetAcquire%3AfastTryLock%3AQMutex%3A%3Alock ?
[10:26] <ev> Saviq: so normally that wouldn't be a cihelp ping, but you're in luck that I'm the vanguard today. ;)
[10:26] <ev> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[10:26] <Saviq> ev, ;)
[10:26] <Saviq> ev, well, yeah, but there's only one thread, which seems unlikely?
[10:27] <ev> so it looks like the core file the retracer got was busted. You could argue that maybe if we got one from a different user from the same problem it may well work, so I'd suggest filing a bug against daisy and letting bdmurray know.
[10:27] <ev> well I'm inclined to not trust anything it says when there's corruption
[10:28] <Saviq> ev, there's like 160 reports in https://errors.ubuntu.com/problem/57e495ad9b12ea8e78d0aed997ba70a6e2213dd2 for example, and same situation - just one thread reported
[10:28] <ev> though given that this is a single instance of the crash on armhf, I wonder if we're having problems with gdb again
[10:28]  * Saviq files then
[10:28] <ev> yeah, that one is more convincing :)
[10:29] <ev> Saviq: so we had problems a while back with gdb breaking on armhf. It could be a regression (and frustratingly not something we test for, I think)
[10:29] <Saviq> kk
[10:35] <popey> cihelp can someone fix jenkins building for the core apps ppa, it's pulling the old terminal and not the new one... https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/ubuntu/daily - new is 0.7, old is 0.5
[10:36] <ev> popey: looking
[10:40] <dbarth_> jibel: ok, on it
[10:41] <jibel> dbarth_, it doesn't seem specific to gmail
[10:41] <jibel> dbarth_, thx
[10:41] <dbarth_> jibel: ah but i doubt it's anything webapp related though
[10:41] <dbarth_> i would mostly triage and ask saviq to take a look, as it seems more like a shell problem
[10:41] <jibel> sil2100, who can look at this notification issue?
[10:41] <sil2100> jibel, dbarth_: all in all it's a bit worrying I must say
[10:42] <jibel> dbarth_, np, investigation must start somewhere
[10:42] <dbarth_> Saviq: related to that bug 1431517, what could cause a push notification not to be displayed by the shell?
[10:42] <sil2100> dbarth_: could you take a look if it's indeed not anything on your side? I guess Saviq could help identifying what parts of the shell deal with notificatinons
[10:43] <dbarth_> jibel: right, i looked into this one with rvr yesterday, and there is already a bit of a diagnostic
[10:43] <Saviq> dbarth_, it's the push service that wakes the device and vibrates
[10:44] <Saviq> dbarth_, so you'd have to talk to Chipaca
[10:44] <dbarth_> sil2100: i doubt it is, because the push-helper living in the webapp package is actually called and returns a valid reply to ask for vibration, and display of the notification
[10:44] <dbarth_> right, Chipaca is a good person to annoy at this stage :)
[10:45] <sil2100> I don't see anything landing from ubuntu-push for this release
[10:45] <sil2100> Chipaca: ping
[10:56] <Chipaca> sil2100: pong
[10:56] <Chipaca> hello
[10:59] <Chipaca> dbarth_: read the bug report. missing the push client logs, i can only guess as to what's going on.
[11:00] <Chipaca> dbarth_: but if the bug report is accurate, push client sent the notification to the messaging indicator, and the messaging indicator believes it's showing it (so much so it turns the led on)
[11:00] <Chipaca> dbarth_: if you can reproduce the issue, turn on debug logs in the push client, reproduce the issue, and get me the logs
[11:00] <jibel> Chipaca, attached
[11:02] <ogra_> sil2100, hmm, https://ci-train.ubuntu.com/job/ubuntu-landing-019-0-reconfigure/29/console why is it complaining, is your "reconfigure" different from my "reconfigure" in any way ?
[11:03] <Chipaca> jibel: can you reproduce the issue?
[11:03] <dbarth_> Chipaca: ok i will do that
[11:03] <jibel> Chipaca, yes
[11:03] <dbarth_> Chipaca: i can reproduce the issue as well
[11:03] <jibel> Chipaca, with telegram or gmail
[11:04] <Chipaca> jibel: with *telegram*?
[11:04] <Chipaca> nice
[11:04] <Chipaca> jibel: turn on debug logs, please, reproduce, get me that
[11:04] <Chipaca> but if the led really goes on, it's the indicator, somehow
[11:04] <jibel> Chipaca, how do you turn on debug logs?
[11:04] <Chipaca> jibel: turn on debug logs => either edit /etc/xdg/ubuntu-push-client/config.json, or copy that directory to ~/.config and edit it there
[11:05] <Chipaca> jibel: the edit is basically “sed -i -e 's/info/debug/' /the/file”
[11:05] <ev> popey: sorry this is taking so long - I needed to sort super admin powers on that jenkins
[11:05] <popey> ev: np
[11:06] <Saviq> ogra_, I don't think you can use the reconfigure job to add new components, they use the prepare job for that I think?
[11:06] <ogra_> ouch, ok ... the message should make this distinction then :)
[11:07] <ogra_> telling me that reconfigure failed but telling me that someone else needs to reconfigure is confusin
[11:07] <ogra_> g
[11:09] <Chipaca> jibel: oh, forgot to mention you need to restart ubuntu-push-client for the change to take effect
[11:09] <jibel> Chipaca, that's fine, I rebooted the phone
[11:10] <Chipaca> jibel: that'll do :)
[11:12] <sil2100> ogra_: looking
[11:12] <sil2100> ogra_: yeah
[11:12] <ogra_> ok
[11:12] <sil2100> As Saviq mentioned, right now it's forbidden - let me reconf for you
[11:12] <ogra_> thanks
[11:12] <jibel> Chipaca, https://bugs.launchpad.net/webapps-core/+bug/1431517/+attachment/4344170/+files/ubuntu-push-client.debug
[11:15] <Chipaca> jibel: so, yeah, push is doing is asking for the notification centre entries (and being told they're there)
[11:22] <sil2100> ogra_: ^ done
[11:22] <ogra_> thanks !!
[11:23] <jibel> sil2100 if it is not a problem with the apps and with push client, who can look at the notification?
[11:23] <sil2100> jibel: I'm looking at the changes again, hm
[11:24] <jibel> sil2100, changes from last promotion http://paste.ubuntu.com/10590324/
[11:26] <sil2100> Chipaca: so all is good on the push side?
[11:26] <sil2100> This is absurd
[11:26] <Chipaca> sil2100: from those logs, all seems correct
[11:27] <Chipaca> sil2100: spotted an unrelated issue wrt account-polld and individual message actions, but that's nothing to do with this :)
[11:27] <sil2100> I think we need to get all hands on deck
[11:27] <jibel> davmor2, did you flash stable to confirm the regression with notifications or should I?
[11:28] <sil2100> Saviq: I see some notification-based changes in unity8 - do you think this might cause some problems as we're seeing right now?
[11:28] <davmor2> jibel: next job I think and then I can run the upgrade to 256 then
[11:28] <jibel> davmor2, OK
[11:28] <Saviq> sil2100, you mean in silo 6 or?
[11:29] <sil2100> Saviq: no, in here: paste.ubuntu.com/10590324/
[11:29] <sil2100> In rtm
[11:30] <imgbot> [11:30] <imgbot> [11:30] <sil2100> Saviq: we need someone with knowledge of the whole notification chain helping out triaging this bug
[11:30] <sil2100> As it's a blocker for OTA-2 promotion
[11:30] <ogra_> sil2100, i suspect we'll need more image rebuilds to fix this issue ...
[11:30] <sil2100> ogra_: ACK
[11:31] <Saviq> sil2100, if you're not getting vibration or power, that's not something unity8 is dealing with
[11:31]  * ogra_ starts another one with a more verbose livecd-rootfs 
[11:31] <Saviq> sil2100, I can test that we're displaying all the notifications as they arrive, did that when landing this change, too
[11:32] <Saviq> sil2100, but currently (I know, bad arch) unity8 does not wake screen up or vibrate on notification
[11:32] <ev> popey: it looks like you guys haven't updated debian/changelog to say 0.7 is the new version
[11:33] <ev> in r13 of lp:ubuntu-terminal-app you bumped to 0.7
[11:33] <ev> but debian/changelog is still at 0.5
[11:33] <popey> hm
[11:33] <ev> you can see this in action at http://91.189.93.70:8080/job/generic-land/2942/console
[11:33] <sil2100> Saviq: if push is working fine, who do you think we should poke about the notifications not happening?
[11:33] <popey> ev: well, sorry about that. I'll take a look, thanks.
[11:33] <Saviq> sil2100, and since notification center and notification bubbles are separate still, whatever is putting the msg in the notification center seems to not be doing the legwork to wake up, vibrate and send the notification
[11:34] <Saviq> sil2100, define "push is working fine"
[11:34] <sil2100> Chipaca mentioned that from the logs push seems to be doing everything it's supposed to be doing
[11:34] <sil2100> Chipaca: ^
[11:34] <sil2100> (from the logs)
[11:34] <Saviq> Chipaca, it's push that wakes the screen up and vibrates, right?
[11:35] <imgbot> [11:35] <Saviq> unity8 is not doing it, that's for sure, but maybe there's another component that should, but isn't
[11:35] <sil2100> Those are the questions I'd like to know the answers for
[11:35] <davmor2> sil2100: who is on the image building spree
[11:36] <Saviq> ogra_, ↑ ;
[11:36] <ogra_> davmor2, me, trying to fix th eemulator builds that fail since yesterday
[11:37] <jibel> Chipaca, in the log there is "playing sound /usr/share/sounds/ubuntu/notifications/Slick.ogg using paplay" if I use paplay <nofication sound> from phablet user is it supposed to work?
[11:37] <davmor2> ogra_: haha!
[11:37] <ogra_> sadly it looks like they run fine til the very end ... but we end up with a 0 byte device tarball
[11:37] <ev> popey: no worries at all; I got to learn a bit more about the internals of this thing
[11:37] <davmor2> ogra_: why it does work anyway :P
[11:37] <ogra_> so i'll have to do a few rebuilds with adding more and more verbosity to finally find the sisue
[11:38] <Chipaca> jibel: sounds on rtm aren't working, that's a separate bug
[11:38] <davmor2> doesn't even
[11:38] <jibel> k
[11:38] <Chipaca> jibel: that's rsalveti
[11:38] <Chipaca> somehting about pulseaudio's mom coming to visit
[11:43] <Saviq> dbarth_, sil2100, if you keep the screen on, is the notification bubble displayed, or is it just the envelope that goes green?
[11:46] <sil2100> jibel: ^ ?
[11:50] <Saviq> jibel, also, do SMS and incoming calls work fine? if so, it really must be somewhere between push and usensord/powerd
[11:51] <dbarth_> Saviq: just the enveloppe
[11:52] <Saviq> I just tried SMS and calls, and is fine, vibration, power and bubble, so everything seems to be working fine on the receiving ends of this
[11:53] <Saviq> someone needs to dig into push and what it's calling to trigger the above, why isn't it getting through
[11:54] <dbarth_> Saviq: are you testing on RTM? i have image #19 here and rvr was on rtm-proposed
[11:56] <Saviq> dbarth_, rtm-proposed
[11:56] <Saviq> r256
[11:56] <rvr> Yes, SMS is fine in rtm proposed
[11:58] <Saviq> so yeah, the broken bit is somewhere between push and usensord/powerd AFAICT
[11:59] <sil2100> :|
[12:04] <Chipaca> Saviq: how usensord/powerd?
[12:04] <Chipaca> Saviq: not sure where that one comes in :)
[12:04] <Saviq> Chipaca, you're talking to them to trigger vibration and screen, no?
[12:04] <Saviq> "you" == ubuntu-push
[12:04] <Chipaca> Saviq: "screen"? you mean the led?
[12:04] <Saviq> Chipaca, no, I mean screen, as in backlight
[12:05] <Chipaca> we don't touch the backlight, no
[12:05] <Saviq> someone has to
[12:05] <Chipaca> Saviq: why?
[12:05] <Chipaca> the screen doesn't go on when a notification arrives
[12:06] <Saviq> Chipaca, that's what people complain about :)
[12:06] <Chipaca> uh?
[12:06] <Saviq> that there's no notification bubble or vibration on incoming email
[12:06] <Saviq> jibel, dbarth_ ↑?
[12:06] <Chipaca> for emails, vibrations are explicitly not asked for
[12:07] <Chipaca> ditto for bubbles
[12:07] <Chipaca> notification centre entries should be there though
[12:07] <Chipaca> oh, let me check bubbles wrt emails
[12:07] <Chipaca> i know telegram does not ask for them
[12:07] <Chipaca> so, yes, gmail asks for bubbles
[12:08] <Saviq> jibel, sil2100, dbarth_, the plot thickens ↑
[12:08] <Chipaca> but bubbles does not mean 'turn the screen on'
[12:08] <Chipaca> however the bug also says the notification centre is empty
[12:08] <Chipaca> or did i misread?
[12:08] <Saviq> Chipaca, there's no bubbles even if screen on apparently
[12:09] <Saviq> Chipaca, that I'm not sure of, at least the LED comes on, so the envelope goes green
[12:09] <sil2100> Uh oh!
[12:09] <Saviq> which means something did happen to the notification centre, whether an item got added, not sure
[12:10]  * Saviq has no gmail account, and is not really even involved in this, other than improving communication apparently
[12:10] <Chipaca> Saviq: yeah, the notification led coming on but the notification centre being empty is why i think the problem lies in the indicator
[12:11] <Chipaca> but i had missed the thing about the bubble
[12:11] <Chipaca> jibel: poke
[12:11]  * Chipaca wants to confirm
[12:11] <Saviq> Chipaca, yeah, if LED on and no item in centre, that's indicator
[12:11] <Saviq> or well, could be unity8 too in theory, but SMS and missed calls work, so...
[12:12] <Chipaca> Saviq: also because in the debug log, push *thinks* it's asking for (and getting) everything it's been told to
[12:21] <sil2100> Let me try upgrading and check that
[12:23] <Chipaca> sil2100: is this on rtm-proposed on krillin?
[12:31] <sil2100> Chipaca: yes
[12:32] <Chipaca> sil2100: any risk to me flashing it?
[12:33] <sil2100> No ;) It's our promotion candidate, so it's good in overall
[12:33]  * sil2100 tries to add his google account
[12:33] <Chipaca> sil2100: that's still ubuntu-touch/ubuntu-rtm/14.09-proposed yes?
[12:33] <sil2100> hm, I'm unable to do that apparently
[12:34] <sil2100> Chipaca: yes
[12:34] <Chipaca> sil2100: the problem seems to not be only gmail, so you could install poke
[12:34] <sil2100> jibel, davmor2: I apparently can't setup my gmail account - the google account page ends up white all the time
[12:35] <davmor2> sil2100: congratulations I've managed to set it up across the board :)
[12:36] <sil2100> Oh, I think I just have connection issues
[12:41] <sil2100> davmor2: how do the gmail notifications work? If I'm logged in the gmail account and have it running in the BG, should it automatically inform me of new e-mail?
[12:42] <Chipaca> sil2100: yes
[12:42] <davmor2> sil2100: you need to enable gmail in the google account and login once I think then you should get notifications
[12:42] <Chipaca> sil2100: and you can prod it to poll sooner over dbus
[12:42] <sil2100> Chipaca: ok, I got a notification popup
[12:42] <Chipaca> phew :)
[12:42] <sil2100> No sound, but the bubble appeared
[12:42] <Chipaca> sound doesn't work in rtm
[12:43] <sil2100> Not sure about wibration, it might have vibrated but I'm not sure ;p But it was on a screen that's turned on
[12:43] <sil2100> Should it work when the screen is turned off?
[12:44] <Chipaca> sil2100: yes, it should, but if it isn't vibrating, and sound isn't working, how would you know :)
[12:44] <Chipaca> sil2100: is it appearing in the notification centre?
[12:44] <sil2100> Chipaca: I saw it on the notification indicator
[12:45] <sil2100> hm, on screen turned off I didn't seem to get a notification
[12:45] <Chipaca> no sound in rtm is bug #1413818, fwiw
[12:45] <davmor2> Chipaca, sil2100: so in image 16 I get blue flashy light and an item in indicator but no bubble for gmail and nothing for telegram, in 19 I get blue flashy light an item in indicator and no bubble for gmail and a vibrate osd and item in indicator for telegram
[12:45] <davmor2> Saviq: ^
[12:46] <Chipaca> davmor2: gmail is not asking for vibration, so you wont' get one
[12:46] <davmor2> Chipaca, sil2100: ofcourse I blame Saviq for all of this :)
[12:46] <sil2100> davmor2: so it seems not to be a regression, right?
[12:46] <davmor2> Chipaca: yeah but I don't get OSD on gmail either
[12:46] <sil2100> davmor2: since I got an OSD on gmail on the latest -proposed
[12:47] <sil2100> (when screen was on)
[12:47] <davmor2> sil2100: ah I'm here with screen off I'll try again with screen on
[12:48] <Saviq> communication shutdown
[12:48] <Chipaca> davmor2: how are you checking for bubbles?
[12:48] <Chipaca> davmor2: if the screen is off, how do you know you don't get a bubble? :)
[12:48] <Chipaca> (hint: you can't; the screen is off)
[12:49] <davmor2> Chipaca: normally it wakes the screen or is that linked to the ping/vibrate?
[12:49] <Chipaca> davmor2: it doesn't normally wake the screen
[12:49] <Chipaca> i don't know where that impression comes from, but it's a false impression
[12:50] <davmor2> Chipaca: SMS, calls and alarms that all trigger OSD bubbles
[12:52] <Saviq> davmor2, all those wake the screen up explicitly indeed
[12:54] <Chipaca> davmor2: so it does. Push doesn't do that.
[12:55] <imgbot> [12:55] <Chipaca> davmor2: nor have we been asked to do that. Not sure we should do that or not :)
[12:55] <imgbot> [12:55] <sil2100> huh
[12:55] <Chipaca> in testing i just got a bubble for twitter, on rtm-proposed, fwiw
[12:56] <Chipaca> not sure what we're looking for any more. jibel?
[12:56] <davmor2> Chipaca, Saviq, sil2100, jibel, rvr: okay so upgrade to 256 is all good, gmail does indeed display an OSD when the screen is on
[12:56] <Chipaca> i should make account-polld ask for vibrations
[12:56] <sil2100> I think we need jibel and rvr to double-check the expectations here
[12:56] <Chipaca> and maybe find out whether we want to turn on the screen when showing a popup
[12:57] <jibel> Chipaca, yeah, it's all a bit confusing, is there a spec somewhere that describes the expected behaviour of the different notifications?
[12:57] <Chipaca> also look into the %!s(MISSING) bit of the log
[12:57] <sil2100> Since the bug expects vibration, sound and screen notification, but that's not the case?
[12:57] <Chipaca> jibel: i don't think there is a spec as to what to expect from gmail notifications
[12:58] <Chipaca> jibel: i can point you at the developer docs that say what is available
[12:58] <Chipaca> jibel: but i don't think you're asking for that
[12:58] <jibel> Chipaca, no, I'd need a design doc
[12:58] <Chipaca> jibel: for gmail notifications
[12:58] <jibel> Chipaca, gmail and other notifications in general
[12:58] <Chipaca> jibel: but you're not asking about other notifications in general
[12:59] <Chipaca> i mean, other notifications in general vibrate, because they ask to vibrate
[12:59] <jibel> Chipaca, designing tests from implementation is a guaranteed failure :)
[12:59] <Chipaca> you're expecting notifications that don't ask to vibrate to vibrate :)
[12:59] <Saviq> Chipaca, jibel, the notification system is kind-of a mess right now, we never had the time to converge it all properly, but design team is currently working on a notification refresh, which is when we should ask those questions :)
[13:00] <davmor2> Chipaca: So I don't mind the OSD not waking the screen it saves the battery, but I think vibrate would be nice just so there is some sort of notification that there is a mail there maybe
[13:00] <Chipaca> davmor2: yes, i think account-polld should ask for vibrate
[13:00] <Chipaca> davmor2: sergiusens can turn them off if he dislikes them ;-p
[13:00] <jibel> Chipaca, I'm looking for a doc that says "Here is the beahaviour when I receive a notification from gmail, here is the behaviour when I receive a notification from app X, ..."
[13:00] <Chipaca> jibel: no such thing exists, and i doubt it will exist ever
[13:00]  * sil2100 sighs
[13:01] <Saviq> jibel, it will always miss $my_favourite_service
[13:01] <sil2100> We should get our designs straight
[13:01] <Saviq> sil2100, shush
[13:01] <Chipaca> sil2100: that is being done, as Saviq pointed out :)
[13:01] <davmor2> Saviq: look it's all your fault anyway ;)
[13:01] <Chipaca> yeah, Saviq, all your fault
[13:01] <jibel> Saviq, yeah, but there are probably classes of apps that share the same behaviour
[13:01] <Chipaca> you owe us all cake, now
[13:02] <jibel> anyway, we can as well remove these tests from the test suite
[13:02] <Saviq> jibel, so yeah, you should've said "email" not "gmail" :)
[13:02] <Chipaca> jibel: that's closer to what i was trying to get at
[13:02] <Chipaca> jibel: what are you testing for?
[13:03] <davmor2> Saviq, jibel: it's things like do we treat telegram the same way as sms being as the two are basically a messaging app?
[13:04] <jibel> Chipaca, we are testing rtm for regression but some of the initial tests have been designed from the implementation, and without reference it's hard to say if it's a regression or an expected change in the implementation
[13:04] <Saviq> davmor2, *I* would agree that it should be the same, it's all IM
[13:04] <Chipaca> jibel: sorry, i'm trying to get to concrete things we can fix. You say tests have been designed from the implementation, but you seem to be testing for things which have never worked
[13:05] <Chipaca> davmor2: Saviq: I hope, as part of implementing the new notifications spec, we can unify notification handling and not have n paths for it, which is at the root of dissimilar behaviours
[13:06] <Chipaca> jibel: e.g., never has the screen come on to show a gmail notification bubble
[13:06] <Chipaca> jibel: never have gmail notifications vibrated
[13:06] <Chipaca> jibel: etc
[13:06] <jibel> Chipaca, concretely sound/vibration on incoming telegram message or gmail worked and is not working anymore, not sure when it changed though
[13:07] <Saviq> Chipaca, same here (hope)
[13:07] <Chipaca> jibel: ok. sound is not working in rtm (that's bug 1431517)
[13:07] <davmor2> Chipaca: why not enable everything and in the notifications page in setting allow people to select what they get for each app? Novel concept I know :)
[13:07] <Chipaca> um
[13:08] <Chipaca> jibel: sorry, wrong bug
[13:08] <Chipaca> jibel: bug 1413818
[13:08] <Chipaca> davmor2: notification setting page would be too complex
[13:08] <Chipaca> davmor2: although we come pretty close
[13:09] <Chipaca> davmor2: you can disable vibrations (for all notifications), or all notifications
[13:09] <Chipaca> it's something :)
[13:09] <Saviq> davmor2, then you'll ask for setting per-app per-profile (silent, quiet, DnD etc.) :P
[13:09]  * Chipaca will have a D&D profile just to confuse people
[13:10] <rvr> iOS have that
[13:10] <rvr> You can configure which can of notifications are displayed
[13:10] <Chipaca> rvr: not saying it can't be done, saying it would take more design power than we currently can wield
[13:10] <sil2100> jibel: so, what should we do in this case?
[13:10] <sil2100> jibel: I'm not sure we still know what changed, and I'm not sure we even know what's the expectation here
[13:11] <sil2100> I'm a bit worried it might have worked by 'accident' in the past or something
[13:11] <jibel> sil2100, davmor2 compared to 16 and 19 and apparently it is the same behaviour
[13:11] <rvr> sil2100: jibel: I was worried this problem was a regression, but seems it is not, because notifications are an important feature for users.
[13:11]  * Saviq thinks it actually never worked, but memory is flawed
[13:11] <sil2100> rvr: good call, I would say it's important, but indeed it doesn't seem like a regression at least
[13:12] <jibel> I'm sure it worked because notifications during the beta program in January was driving me crazy :)
[13:12] <Chipaca> jibel: and have just confirmed that account-polld--generated notifications haven't had working vibrations for several months at least
[13:12] <Chipaca> although it seems that's unintentional :)
[13:14] <jibel> and gmail notifications used to work too, don't know when it stopped.
[13:14] <Chipaca> jibel: "work"?
[13:14] <jibel> Chipaca, I mean sound + vibration on incoming gmail message
[13:15] <Chipaca> jibel: outside of rtm, sound works; that might be confusing you?
[13:15] <jibel> Chipaca, maybe
[13:16] <Chipaca> jibel: vibration hasn't worked since august of 2014 at least
[13:16] <Chipaca> *for gmail*
[13:16] <dbarth_> rvr: so the bug is invalid per se, i guess; though not uninteresting, considering the discussion above
[13:16] <Chipaca> (and other account-polld sources)
[13:17] <Chipaca> i can use the bug to fix the vibration thing, which is a real bug and needs fixing (although not a regression)
[13:17] <Chipaca> or i can create a new bug for it :)
[13:19] <jibel> I marked our test as "To repair" and we'll figure that out after this release. At least not a regression compared to latest promotion.
[13:19] <jibel> sil2100, ^
[13:19] <rvr> jibel: +1
[13:19] <sil2100> jibel: +1
[13:20] <rsalveti> morning
[13:22] <rsalveti> ogra_: any news regarding the emulator image?
[13:23] <rsalveti> saw you built many images today
[13:23] <ogra_> rsalveti, it just started working with the last build
[13:23] <ogra_> and i dont know why
[13:23] <rsalveti> hm, alright
[13:23] <rsalveti> ogra_: what was the issue exactly?
[13:23] <ogra_> we ended up with a 0byte generic_x86 file
[13:24] <ogra_> so it failed to pull that from the builder to cdimage
[13:24] <ogra_> but the file is fine inside the android package ...
[13:24] <ogra_> what i did was to replace all cp commends in livecd-rootfs that cares for copying the android bits with "cp -v" to get more info in the log
[13:25] <ogra_> and it just started working
[13:25] <ogra_> *commands
[13:26] <ogra_> so it is something to keepan eye one, but works for now
[13:26] <rsalveti> ogra_: haha, alright
[13:26] <rsalveti> yeah
[13:26] <ogra_> it only started with tonights image ... might be the moon phase or so
[14:33] <dobey> trainguards: ^^ can i get a silo for line 52 please? thanks
[14:33] <sil2100> dobey: on it!
[14:56] <sil2100> dobey: one moment, some technical problems ;)
[14:59] <dobey> sure
[15:13] <dobey> sil2100: hmm, seems to be broken still? dashboard doesn't show anything, and trying to build silo 25 results in error about no config for it
[15:13] <sil2100> huh?
[15:14] <dobey> oh
[15:14] <dobey> nevermind
[15:14] <dobey> somehow i was looking at rtm not ubuntu
[15:14] <sil2100> dobey: looks ok here
[15:14] <sil2100> :)
[15:16] <sil2100> == Images krillin 256, mako 214, generic_x86 206 PROMOTED to RC ==
[15:47] <sil2100> jibel, davmor2: is everything more or less wrapped up on your side? Will you have some cycles to already resume vivid sign-off?
[15:47] <davmor2> sil2100: no we are to busy partying like it's 1999
[15:48] <sil2100> hm, oh partying? Then maybe you want to skip the evening meeting once again to have time for more dancing, hmm?
[15:48] <sil2100> HMM?
[15:50] <davmor2> sil2100: what neetming hic you're not my dad hue carnt tell ME wata due hic
[15:52] <davmor2> sil2100: not we are cracking on with sanity on mako and silos for vivid now
[15:53] <sil2100> I'm actually once again thinking about the evening meeting, since in such a case like today I don't want to waste anyone's time if everything's clear
[15:53] <sil2100> popey: do you have anything for us in the evening meeting?
[15:53] <jibel> sil2100, it's resumed already
[15:54] <sil2100> I'm fine with having the meeting, but not if there's nothing new to discuss
[15:56] <popey> sil2100: no
[16:04] <sil2100> jibel: do you have anything for the meeting?
[16:05] <jibel> sil2100, bot really
[16:05] <jibel> not*
[16:05] <sil2100> robru, ogra_, davmor2, rvr: anything from you guys?
[16:05] <ogra_> nope
[16:05] <rvr> Nope
[16:05] <sil2100> ogra_: how's the emulator? I heard it just fixed itself?
[16:05] <ogra_> images build fine again
[16:05] <davmor2> nope
[16:06] <ogra_> sil2100, yeah, no idea what that was
[16:06] <sil2100> hm, I'm starting to feel bad by cancelling yet another evening meeting
[16:06] <sil2100> Should I feel bad about that? I wonder
[16:06]  * ogra_ thinks its is fine
[16:07] <jibel> canceling meeting when there is nothing on the agenda is not a bad thing
[16:08] <ogra_> +1
[16:09] <sil2100> robru: skipping the meeting once again o/
[17:01] <robru> sil2100: sweet
[17:21] <robru> bregma: landing 26
[18:13] <dobey> hmm
[18:15] <robru> dobey: what's up?
[18:16] <dobey> robru: just wondering when ToyKeeper will be able to retest my pay-ui landing
[18:17] <robru> dobey: I think her day usually starts in 3-4 hours.
[18:17] <ToyKeeper> dobey: The OTA image was already built and is almost done being tested...  it's probably too late.
[18:17] <robru> or she's up early ;-)
[18:17] <ToyKeeper> (was probably too late yesterday)
[18:18] <dobey> ToyKeeper: it's too late for the OTA image indeed. but we still want to get it in the store as an update (and then it will get pulled into the next image for ww13 or whatver)
[18:18] <dobey> oh
[18:19] <dobey> ToyKeeper: did you move to .nz or something?
[18:19] <ToyKeeper> No, I've pretty much always been on a NZ-like schedule.
[18:19] <rvr> Mirv: Mega-silo 12 is mega-failing. Doesn't pass the bq logo screen after installing the packages.
[18:20] <dobey> ToyKeeper: ah, ok
[18:20] <robru> ToyKeeper: NZ-like? I thought you lived in NZ!
[18:21] <dobey> heh
[18:21] <ToyKeeper> I just woke up, but it looks like the OTA already got promoted about 3 hours ago.
[18:22] <ToyKeeper> dobey: So, I should be able to get back to silos since there's nothing left for the OTA.
[18:22] <dobey> ToyKeeper: ok, thanks
[18:22] <ToyKeeper> dobey: Is it already landed in vivid?
[18:23] <dobey> ToyKeeper: pay-ui is a click package only
[18:23] <ToyKeeper> Right, okay.  I had been thinking it was targeted at one or the other.
[18:24] <ToyKeeper> I think this last OTA is the end of 14.09, so I'll try it out on vivid.
[18:24] <dobey> nope, just the store. but it is included in the images by default, so we wanted to get it into the ota image too
[18:24] <ToyKeeper> (if I understand correctly, anyway)
[18:24] <ToyKeeper> (but I'm not fully awake yet...)
[18:25] <dobey> ToyKeeper: well, pay-ui has to work on both, so testing on rtm would be best i think
[18:25] <dobey> (or both even)
[18:27] <ToyKeeper> I should remember not to attempt thinking until I've been up for at least half an hour.
[18:28] <dobey> sometimes you forget though :)
[18:31] <sil2100> rvr: hey, don't test silo 12 for now
[18:31] <sil2100> rvr: it's not something for a normal sign-off
[18:31] <sil2100> It's a big one with 5.4.1 and required actually a separate image and almost a full regression suite ran
[18:32] <dobey> ugh google calendar doesn't show week numbers either
[18:32] <rvr> sil2100: We talked about installing the silo in our devices and do an informal check during the weekend
[18:32] <rvr> sil2100: (We = ops team)
[18:33] <rvr> sil2100: But after installing silo packages, the system doesn't boot
[18:36] <sil2100> uh oh
[18:36] <sil2100> Mirv: boing ^
[18:36] <sil2100> o/
[18:43] <robru> brbrunch
[19:53] <davmor2> popey: Music app is good \o/
[19:57] <popey> davmor2: ooh!
[19:57] <popey> davmor2: good as in "seems okay so far" or "clear to upload"
[19:58] <davmor2> popey: clear to upload it does everything it's meant to as far as I can tell
[19:58] <popey> thanks davmor2
[20:01] <popey> \o/ uploaded
[20:01] <popey> ahayzen_: ^
[20:18] <Mirv> rvr: did you follow the instructions about cleaning QML cache etc?
[20:19] <Mirv> rvr: and not using citrain tool
[20:20] <Mirv> davmor2: are you on the ops team too? ^
[20:20] <davmor2> I am
[20:21] <davmor2> Mirv: ^
[20:21] <Mirv> davmor2: did you upgrade and do you know if rvr (or others) maybe thought they can use normal citrain tool?
[20:21] <davmor2> Mirv: probably
[20:22] <zyga> cihelp: i need help understanding how to get a project set up in CI train
[20:22] <davmor2> Mirv: are you saying you can't?
[20:22] <Mirv> davmor2: yes, like the instructions says
[20:23] <Mirv> davmor2: could you move the card maybe back from Failed?
[20:23] <josepht> zyga: I think you need trainguards for that
[20:23] <zyga> dobey: (let's talk here)
[20:23] <zyga> josepht: I don't understand what that is
[20:23] <davmor2> Mirv: which instructions I was about to install it here
[20:23] <dobey> ok
[20:23] <Mirv> davmor2: https://wiki.ubuntu.com/Process/Merges/TestPlans/Qt "and instructions for updating phone or desktop at https://wiki.ubuntu.com/Touch/QtTesting - do not forget to remove the QML cache before rebooting! "
[20:23] <josepht> zyga: s/cihelp/trainguards/ :)
[20:24] <zyga> josepht: ah, I see
[20:24] <zyga> it's not a bot :)
[20:24] <dobey> josepht: i don't think trainguards manage the config for CI do they?
[20:24] <zyga> dobey: is the CI system specific to phablet/click packages?
[20:24] <dobey> zyga: no
[20:24] <zyga> dobey: specific to .deb packages?
[20:24] <dobey> zyga: the qt 5.4.x update goes through the ci train for example
[20:24] <zyga> dobey: if no, then I think it could be useful for checkbox
[20:25] <zyga> dobey: is that something we can use for per-merge-request CI?
[20:25]  * Mirv makes the instructions on the testplan page more bold
[20:25] <dobey> zyga: yes, there's jobs that run tests on MPs
[20:25] <josepht> dobey: no
[20:25] <Mirv> davmor2: in short, citrain tool fails to cope when something in the silo has a new dependency that needs to be installed from normal archives, after which citrain proceeds to remove half of the rootfs
[20:25] <davmor2> Mirv: nice one I'll try that now if I get it all up and running I'll move the card then does that sound fair :)
[20:25] <zyga> dobey: how can I define what kind of tests run?
[20:25] <dobey> zyga: see all the "PS Jenkins bot" comments on https://code.launchpad.net/~dobey/pay-ui/mir-app-test/+merge/251163 for example
[20:26] <josepht> zyga: are you looking for tests to be run on MPs?
[20:26] <Mirv> davmor2: thanks! do you know if anyone else besides rvr needs to be pinged?
[20:26] <dobey> zyga: via debian/rules (for when building a deb), and via autopkgtest config for click packages, plus the config bits in the CI system itself
[20:26] <davmor2> Mirv: no I'll add a note to the ticket
[20:26] <zyga> josepht: I'm not sure, I don't understand any of the UE CI stuff yet
[20:27] <dobey> josepht: zyga has checkbox currently being merged via a tarmac outside of CI train. i was suggesting it would be good to get that moved into the CI train
[20:27] <zyga> dobey: we're not building debs or clicks like that, we don't have packaging in our branches
[20:27] <ahayzen_> popey, \o/
[20:27] <Ursinha> josepht: I'm not super familiar with that, but maybe that's the autolanding cu2d-config job?
[20:27] <zyga> we have a script in the tree that discovers tests to run, sets up containers/vms and proceeds to run each test in each environment
[20:28] <zyga> then that either passes or fails the merge request
[20:28] <dobey> hmm
[20:28] <zyga> we can edit one file and say that we want to test on vivid now, or stop testing utopic
[20:28] <zyga> similarly we can add a new library and its dependencies
[20:28] <josepht> Ursinha: I think cu2d-config is what he's after
[20:28] <zyga> or stuff like that
[20:29] <zyga> I'm trying to understand how that translates to this system
[20:29] <zyga> we build a number of libraries and tools
[20:29] <zyga> some of which end up in debs later (and are packaged in debian and in a set of PPAs)
[20:29] <Mirv> davmor2: ok, thanks! too bad if rvr is already gone so he doesn't get to test it
[20:29] <zyga> some of which are built as click packages though that process is manual for now (we run that script once a release is planned)
[20:30] <zyga> debian packages have DEP-8 tests and build-time tests
[20:30] <zyga> click packages have nothing as expected
[20:30] <zyga> how can I translate that over to the CI train (is that the right name?)
[20:30] <Mirv> davmor2: also, it may be confusing that I still included the citrain commands on https://wiki.ubuntu.com/Touch/QtTesting even though I said not to use them, so I now put them as strikethrough so it's more clear to use the manual dist-upgrade instructions below
[20:31] <zyga> oh and we have like 30 branches monitored by one tarmac
[20:31] <zyga> what I
[20:31] <zyga> what I'm describing is just lp:checkbox
[20:31] <davmor2> Mirv: commands run
[20:31] <zyga> but the mechanics is generic
[20:31] <josepht> zyga: we have a bot that monitors branches; when an MP is proposed it kicks off a jenkins job to run the appropriate tests (I'm not sure how customizable that bit is) and merges the branch (assuming the correct number of approvals are given and such)
[20:31] <dobey> zyga: i'm not sure what all exactly you're doing in checkbox. it sounds like maybe you're doing way more complex things than i was expecting though
[20:32] <zyga> dobey: it's an old project with lots of things to support :/
[20:32] <zyga> dobey: we really want our 12.04-based tests to run for example
[20:32] <davmor2> Mirv: looks good here I bet he just used citrain
[20:32] <zyga> dobey: as sometimes we introduce something that fails on python3.2
[20:32] <zyga> josepht: where are the definitions of things that jenkins runs?
[20:32] <Ursinha> fginther has all the answers, if he's around he could clarify and we would all learn :)
[20:32] <dobey> zyga: right, i'm sure CI train can run tests on a precise node/vm
[20:33] <davmor2> Mirv: I'll update the ticket now look out for an anouncement on Monday Landing meeting ;)
[20:33]  * fginther catches up
[20:33] <zyga> is the CI train capable of working with non-bzr branches (wink wink)
[20:33] <fginther> no
[20:33] <fginther> :-)
[20:33] <zyga> is that planned at least?
[20:34] <josepht> zyga: the configs are here: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/files
[20:34] <dobey> probably not before launchpad git support is finished
[20:34] <fginther> zyga, the CI infrastructure is completed geared toward launchpad projects and debian packages (and to a vers small extent click packages)
[20:34] <Ursinha> to be supported somewhere yes, we still don't know if in CI train as it is :)
[20:34] <Mirv> davmor2: you managed to upgrade already? cool!
[20:34] <davmor2> Mirv: yes I have Broadband ;)
[20:34] <Mirv> davmor2: thanks. I also replied to rvr's e-mail in case he checks it still so we'd have two extra testers.
[20:35] <Mirv> davmor2: oooh, I've heard of those! :)
[20:35] <dobey> but you can't use tarmac without bzr either :)
[20:35] <zyga> dobey: we don't love tarmac
[20:35] <dobey> :(
[20:35] <zyga> dobey: what we have can run without tarmac
[20:35] <zyga> dobey: in fact, it's something we can run from the tree at any time
[20:35] <zyga> dobey: so it's useful for reproducing issues
[20:36] <robru> dobey: zyga: CI Train does not run tests beyond what get run when you 'debuild' in your source tree. the train just automates building of debs in a PPA, then you manually verify the debs, and if you approve them, then the train merges your merges for you. it's very rudimentary and very manual.
[20:36] <zyga> dobey: we'll be off bzr the day it's possible though that's a secondary topic
[20:36] <zyga> robru: so we cannot use it as we're not keeping packaging in trunk
[20:36] <dobey> well, sure. tarmac is designed to run things from the tree the same as the would be run by the developer
[20:36] <zyga> robru: packaging is in debian and in a number of packaging overlays
[20:36] <robru> zyga: yeah that's the other thing, you need debian/ in trunk
[20:36] <zyga> robru: oh, then this is not going to work for us
[20:37] <zyga> robru: we keep 10+ projects in one tree as this is much easier to work with (it's one project but it has libraries and plugins and stuff and packaging is pretty complex)
[20:37] <zyga> robru: where project == something we release and package as separate thing
[20:37] <dobey> ick :)
[20:37] <robru> zyga: yeah sounds like a really poor fit. train enforces lp project == debian package
[20:37] <zyga> robru: because we didn't want to invent anything that can combine sensibly $N trees or have to have $N trees around and synchronized
[20:37] <zyga> robru: I see
[20:37] <fginther> zyga, yeah, that is something that the CI MP testing and ci-train were not designed to handle
[20:37] <zyga> robru: ok, that settles it for now then :/
[20:37] <dobey> you're going to be one of those people who uses submodules when you move to git, aren't you?
[20:38] <zyga> dobey: maybe, we're not sure
[20:38] <zyga> dobey: one of the reasons is that we don't have a stable api by design
[20:38] <zyga> dobey: more like linux + drivers
[20:38] <zyga> dobey: though we've started a process where that changes
[20:38] <zyga> dobey: and we have 5+ new projects that have stable api and are handled separately of lp:checkbox
[20:38] <zyga> dobey: so over time checkbox will become smaller
[20:38] <zyga> dobey: but that's a process
[20:39] <zyga> fginther: so about the way it works though
[20:39] <zyga> fginther: can the CI system support a project that wants to build and test for precise, trusty, utopic and vivid from one tree?
[20:39] <robru> zyga: yeah if all you need is "a bot that runs tests when an MP is proposed" then lp:cupstream2distro-config might be able to sort you out
[20:39] <robru> but that's different than the train
[20:40]  * zyga looks
[20:40] <zyga> well, all I want is a git hook
[20:40] <zyga> and we'll script the rest via bits and pieces
[20:40] <zyga> just lp has no hooks
[20:40] <zyga> so we improvise with tarmac
[20:41]  * zyga still wishes for a travis like system for canonical
[20:41] <robru> zyga: right, lp:cupstream2distro-config has the setup that allows you to configure what tests to run and when, based on scanning your trunk for MPs against it. it's not "a hook" but it can make things happen shortly after MPs get proposed.
[20:41] <zyga> where one can say "I want to support those configs"
[20:41] <zyga> "this is how you provision a config"
[20:41] <zyga> "this is how you test"
[20:41] <zyga> do the rest
[20:41]  * zyga reads that code
[20:42] <fginther> zyga, sorta, the CI system can build the same source package against multiple releases, but post build testing is very limited. Someday it will properly support dep8 testing, but that's not there today
[20:42] <zyga> fginther: dep8 is different
[20:42] <zyga> fginther: not everything works with dep8 in general
[20:43] <zyga> fginther: many tets require things that are only in the source tree
[20:43] <zyga> (I love dep-8 but that's the reality)
[20:43] <dobey> zyga: dep-8 can do that
[20:43] <zyga> dobey: oh, no it cannot, how could it
[20:43] <zyga> dobey: it can only install packages, it cannot see the build tree anymore
[20:43] <zyga> dobey: it runs after the build tree is gone
[20:43] <zyga> dobey: at least in debian
[20:43] <dobey> zyga: uhm, there is a flag to require a built source tree
[20:43] <zyga> dobey: you can package that stuff
[20:44] <vila> zyga: oh yes he can, he get the source and run from there
[20:44] <dobey> zyga: where the dep-8 tests will grab the source and build it
[20:44] <zyga> ah, I see
[20:44] <zyga> I didn't know that
[20:44] <zyga> though I also meant that sometimes upstreams don't put stuff into their tarballs
[20:44] <zyga> it's just in the VCS
[20:44] <dobey> zyga: that's pretty much all some of the ubuntuone dep-8 tests did, as it would grab the source and build/run the tests from the tree, to ensure that any dependencies didn't break it
[20:45] <zyga> dobey: yeah, we're using dep-8 whenever we can
[20:45] <dobey> zyga: we caught many pep8 and twisted changes before they landed in distro, by doing that
[20:45] <zyga> dobey: it's a great thing
[20:46] <dobey> zyga: well, anything you need to run the tests should be in the tarballs. if it's not in the tarball, the tarball is broken, i'd say
[20:46] <zyga> dobey: though it started with debian, it's really useful for breaking api and changing dependencies without being careful
[20:46] <zyga> dobey: I know that now, I package some things where upstream doesn't realease tests in the tarball because it's big and they don't want to
[20:46] <zyga> dobey: all the stuff we're writing is dep-8 friendly
[20:47] <zyga> btw, what's the source-rebuild flag/
[20:47] <zyga> I could use that for providers that don't yet have a cli tool to test after installation
[20:47] <zyga> that could catch job clashes when providers that share a namespace do smething nasty
[20:47] <dobey> Restrictions: build-needed
[20:47] <dobey> in debian/tests/control
[20:48] <zyga> ah, nice, I have to try that!
[20:49] <zyga> dobey, thanks for all the tips, I've learned a lot!
[20:49] <dobey> sure
[20:50] <rvr> Mirv: Ah, I see! Thanks, I'll check!
[20:53] <Mirv> rvr: o/ :)
[20:54] <zyga> dobey: quick question, is there anything related to webapps that's using this system?
[20:54] <zyga> dobey: checkbox has a sever backend that's pretty big and totally not packaged
[20:54] <zyga> dobey: it's also using this system that I've described
[20:54] <zyga> dobey: do you know what other webapps are doing by any chance?
[20:55] <dobey> zyga: i think the main webapps are using CI train, but i'm not 100% sure
[20:55]  * Mirv feels it way past bedtime, -> sleep
[20:55] <dobey> they're all pretty much just .desktop files which run "webapp-container $URL" after all
[20:56] <zyga> dobey: I'm not talking about click webapps
[20:56] <zyga> dobey: think launchpad
[20:56] <zyga> dobey: not a click that wraps launchpad.net link
[20:56] <zyga> dobey: I'm talking about the actual website with message queues, databases and stuff
[20:56] <dobey> no, things that aren't packaged aren't using it afaik
[20:57] <zyga> do you know what they are using?
[20:57] <dobey> i don't recall what lp is using exactly
[20:57] <cjwatson> zyga: webhooks are on the list for LP git, though not fully specced out yet
[20:58] <dobey> i know the app store, login.ubuntu.com, stuff, and such are a tarmac though
[20:58] <cjwatson> Launchpad itself?  It uses PQM and buildbot
[20:58] <zyga> cjwatson: yeah, I know, I'd love to be able to influence that
[20:58] <cjwatson> Very 2005
[20:58] <zyga> cjwatson: I don't know if my recommendation reached you (it was done via several layers0
[20:58] <cjwatson> zyga: We had webhooks coming from two teams in the stakeholder process, so it'll be high on the agenda once we're far enough through dependencies
[20:59] <cjwatson> zyga: There was no point having it on the agenda for this dev cycle since it's too far down the stack
[20:59] <zyga> cjwatson: understood
[21:00] <zyga> cjwatson: github hooks are different than git hooks, whatever we build must be enough to support travis.ci supporting launchpad down the road
[21:00] <zyga> even if we have to send patches down them to convince them (I suspect there are more things thay need apart from the hook itself)
[21:01] <zyga> cjwatson: not supporting travis would be a mistake, it measn that hooks are useless for the average person that dones't have their own infrastructure to hook into
[21:01]  * zyga talks too much on 22:01 on Friday
[21:01] <cjwatson> zyga: travis.ci was the specific example given, we understand that
[21:01] <cjwatson> travis-ci, rather
[21:02] <cjwatson> zyga: though it's not entirely within our control, it will involve negotiating with travis-ci since they'd need to add Launchpad support too
[21:02] <zyga> cjwatson: yeah
[21:02] <zyga> cjwatson: it's open source
[21:02] <zyga> cjwatson: so we could do that if we convince them to merge it back
[21:02] <cjwatson> sure, but who cares if it's not deployed on travis-ci, right?
[21:02] <zyga> cjwatson: they also need basic identity management and repo discover
[21:02] <cjwatson> I don't know their politics
[21:02] <zyga> cjwatson: yes, hence the convincing part
[21:03] <cjwatson> and yes I am well aware that github hooks are different from git hooks, I'm capable of googling for the spec ;)
[21:03] <zyga> cjwatson: I kind of wish I was on your team hacking this, this is how much I want this to happen
[21:03] <zyga> I know, sorry if I sound silly
[21:07] <cjwatson> Also, Launchpad itself will likely be an earlyish adopter of git, so we'll get to investigate merge gatekeeping strategies; but of course our CI will be on-site
[21:09] <cjwatson> well, earlyish adopter of git on Launchpad, obviously not of git in general ;)
[21:09] <zyga> cjwatson: yeah, but I'm sure the result will be very interesting
[21:14] <rvr> Mirv: Successful system upgrade!
[21:37] <robru> cjwatson: yeah sign me up to beta test that when it's ready