[00:04] <robru> kgunn, great, got silo 5 fully landed, I just hit merge & clean for you now because we're a little short on silos ;-)
[00:06] <robru> kgunn, I guess this means silos 2 and 3 should be rebuilt, but I will leave that up to you.
[00:06]  * robru -> dinner! bbl
[00:07] <kgunn> robru: dinner and thanks!
[00:07] <kgunn> :)
[00:07] <robru> kgunn, you're welcome!
[00:07] <ToyKeeper> sergiusens, mandel: The unity-scope-click MP in the download manager silo looks like it's waiting on re-testing and review from alecu.
[00:07] <ToyKeeper> sergiusens, mandel: You sure this is ready for landing?
[00:07] <ToyKeeper> https://code.launchpad.net/~mandel/unity-scope-click/rebuild-with-udm/+merge/214935
[00:08] <ToyKeeper> The last jenkins test run also lists some failures.
[00:20] <ToyKeeper> Chipaca: Any extra details you could give about silo 012 (push) would be helpful.  Really, almost any detail at all.  Link to a bug or MP, details on how to test it, etc.
[00:21] <ToyKeeper> The landing proposal has a comment indicating it can't currently be tested, and needs additional people around.
[01:01] <sergiusens> ToyKeeper: I'm not so worried about the jenkins failures as it requires the latest unmerged u-d-m (which is why it built fine in the silo); I am worried however about alecu's comment from just 3 hours ago
[01:03] <ToyKeeper> Thanks, I was wondering about that.
[03:06] <robru> ToyKeeper, how's it going? anything signed off for me to land?
[03:48] <ToyKeeper> robru: Sorry, didn't hear your ping earlier.
[03:48] <ToyKeeper> robru: I finally got the third phone, and am testing it.
[03:48] <robru> ToyKeeper, no worries, thanks
[03:49] <ToyKeeper> Its owner stayed late at work...
[03:57] <Mirv> good morning
[04:03] <ToyKeeper> robru: It appears to work, aside from one kind of big issue.  After ending one call, the second one stays on hold.
[04:03] <robru> ToyKeeper, oh excellent
[04:03] <ToyKeeper> It's still an improvement over the base image though, so I'm inclined to give it a "Yes".
[04:16] <ToyKeeper> It must be late.  It didn't occur to me for like 10 minutes that you can get the second call back by hitting 'play' after hanging up the first call.
[04:19] <ToyKeeper> robru: In any case, silo 004 is signed off.
[04:19] <robru> ToyKeeper, thanks!
[06:42] <Mirv> maybe a new image with mir 0.1.8 should be kicked?
[06:43] <didrocks> Mirv: +1, doing
[06:43]  * didrocks wonders why a Mir version landed without the qt fix
[06:43] <didrocks> asac: do you know from your backlog? ^
[06:49] <imgbot> [07:08] <sil2100> Uh!
[07:09] <sil2100> Am I the only one not being able to sign in on the CI Train spreadsheet? I get a login.ubuntu.com Oops!
[07:09] <Mirv> sil2100: LP seems down too, so no, not the only one
[07:10] <sil2100> ouch
[07:10] <Mirv> it worked a while ago, and spreadsheet does work but I was already logged in
[07:10] <Mirv> so down maybe for 10 mins or so
[07:11] <sil2100> Mirv: btw. I marked you as a reviewer for one of my appmenu-qt5 fixes I made - didn't know who to ask and thought maybe you could help ;)
[07:12] <Mirv> sil2100: I noticed, the diff looked good to me (aside from the #undef signals but that's what you get for mixing Gtk + Qt...) but I've not run it yet
[07:15] <sil2100> Mirv: thanks for taking a look - yeah, it's also what Qt5 does actually for their gtk theme plugin, so I would say it's something acceptable...
[07:15] <sil2100> At least in this case, as I am not using signals anywhere in that file
[07:21] <Mirv> yep, should be good
[07:22] <Mirv> LP seems to work again
[07:24] <sil2100> login.ubuntu.com still seems to have problems
[07:30]  * Saviq just had to try 5 times to finally log in to ci-train... openid failed to "discover a server" first, then OOPS, then 2fa, wrong link...
[07:30] <Saviq> uh or am I able to log in at all?
[07:30] <Saviq> ah, 6 times a charm...
[07:30] <Saviq> :|
[07:31]  * sil2100 still can't log in
[07:35] <ogra_> didrocks, asac, did either of you request the cron job to be shut off ?
[07:36] <didrocks> ogra_: I didn't at least
[07:36] <ogra_> hmpf
[07:38] <asac> didrocks: i dont know tbh. i know kgunn came along with a crash fix that was supposed to be added to the projects that jfunk could validate while we are waiting for the event fix. I didn't know that was landing a new upstream version with ABI break etc.
[07:38] <asac> didrocks: any damage?
[07:38] <asac> ogra_: not me
[07:38] <didrocks> asac: the crash fix was the one with "crash on shutdown" that we had for weeks now
[07:39] <asac> didrocks: right
[07:39] <didrocks> asac: we don't know yet of any damage as I had to kick an image with it
[07:39] <asac> hmm.
[07:39] <ogra_> should i start an image build now ? we didnt get one for the night and there were quite some chnages
[07:39] <didrocks> ogra_: already done
[07:39] <ogra_> *changes
[07:40] <ogra_> ah, k
[07:40] <ogra_> right, i should listen to my bot :P
[07:40] <didrocks> ogra_: still ~30 minutes before it's done I guess
[07:40] <didrocks> :p
[07:40] <didrocks> (1h ago, I didn't realize right away that the image didn't contain Mir as it wasn't the cronned one)
[07:40] <asac> not good that we didnt get an image; is robru not able to kick images?
[07:41] <ogra_> nope
[07:41] <didrocks> asac: we got an image
[07:41] <didrocks> before the Mir change
[07:41] <didrocks> Mir was early today
[07:41] <ogra_> we got 295 from yesterday evening
[07:41] <didrocks> I thought the produced image was the cronned one
[07:41] <didrocks> as there was only one
[07:41] <ogra_> would have been nice to have one inbetween
[07:41] <didrocks> didn't check right away, and so, assumed that Mir which entered before the cronned image was in latest
[07:41] <ogra_> since 2/3 of the changes of the night are on the image
[07:42] <didrocks> yeah
[07:42] <didrocks> ogra_: so you think the release team disabled again by error?
[07:42] <didrocks> ogra_: is there a comment in crontab?
[07:42] <ogra_> no comment
[07:42] <didrocks> should have one I guess :)
[07:42] <ogra_> and this kind of changes usually doesnt happen in the bzr branch
[07:42] <ogra_> so no commit message either
[07:43] <didrocks> we got that on beta as well, right?
[07:43] <ogra_> (only permanent changes to crontab usually go to bzr)
[07:43] <didrocks> not sure beforehand
[07:43] <ogra_> yep
[07:43] <ogra_> i assume infinity has a script or some such ... and forgot to remove touch
[07:43] <didrocks> maybe, infinity can you check, please?
[07:43] <didrocks> ogra_: is there a way to ensure that I'm on the right android version?
[07:44] <didrocks> (tested some upgrade path)
[07:44] <ogra_> ## Also built on demand by touch release team.
[07:44] <ogra_> ## DO NOT DISABLE DURING MILESTONES
[07:44] <ogra_> 02 2 * * *      for-project ubuntu-touch cron.daily-preinstalled --live
[07:44] <didrocks> like, the container has the right drivers…
[07:44] <ogra_> i changed it to that
[07:44] <ogra_> :)
[07:44] <didrocks> great ;)
[07:44] <asac> didrocks: if ToyKeeper refers to "new bugs found" ... this doesnt mena they are regressions, right?
[07:44] <ogra_> (though if it is a script it probably cant read )
[07:44] <ogra_> :P
[07:45] <didrocks> asac: I guess so. It doesn't seem anything that could have been regressed again. It's hard to parse though
[07:45] <didrocks> asac: but I'm unsure, as I explained to her multiple times that we don't really care about exploratory testing and if we find new bugs, we need to confirm if it's a regression or not
[07:45] <asac> ToyKeeper: would be cool if you could clearly state that "New bugs found" are not regressions and highlight those that are.
[07:46] <didrocks> ogra_: did you see my question about the driver/android version?
[07:46] <ogra_> nope
[07:46] <didrocks> 09:43:58 didrocks | ogra_: is there a way to ensure that I'm on the right android version?
[07:46] <didrocks> 09:44:02 didrocks | (tested some upgrade path)
[07:46] <didrocks> 09:44:16 didrocks | like, the container has the right drivers…
[07:47] <ogra_> hmm
[07:48] <ogra_> didrocks, there is one stamp in the system-image ini file
[07:48] <ogra_> and there is:
[07:48] <ogra_> adb shell getprop ro.build.date
[07:48] <didrocks> Fri Apr 11 21:04:45 UTC 2014
[07:48] <didrocks> seems to match
[07:48] <ogra_> yeah
[07:48] <didrocks> so, it's a good news :)
[07:49] <didrocks> asac: I tested stable -> devel upgrade
[07:49] <ogra_> i dont think there is a way to verify the boot.img though
[07:49] <didrocks> worked well
[07:49] <didrocks> (a full image download happened of course)
[07:49] <ogra_> but if it wouldnt have changed you wouldnt be able to boot a new rootfs
[07:49] <didrocks> then, I did devel -> devel-proposed to be on latest
[07:49] <didrocks> ogra_: oh? I thought some people were still able to boot the new rootfs with the old android
[07:49] <didrocks> ogra_: like those on maguro
[07:50] <ogra_> didrocks, they need an up to date initrd
[07:50] <didrocks> ah, so probably possible at the beginning
[07:50] <didrocks> until we broke ABI
[07:50] <ogra_> it is still possible, but the initrd needs to have the recent code changes
[07:50] <didrocks> ok, anyway, good news! the fact to not flash recovery right away while doing stable -> devel-proposed doesn't impact us
[07:51] <ogra_> (worst case you can just update-initramfs -u)
[07:51] <didrocks> ooopsss
[07:51] <didrocks> stable -> devel
[07:51] <didrocks> ogra_: ok, making sense ;)
[07:51] <didrocks> (I didn't tried with any living data, just the upgrade path regarding recovery)
[07:51] <didrocks> rsalveti: FYI ^
[07:52] <ogra_> this is good stuff :)
[07:52] <didrocks> try*
[07:52] <didrocks> yep!
[07:52] <didrocks> so, of course, you see the old android logo while doing the first update :)
[07:52] <didrocks> and then, the new one with new recovery
[07:52] <ogra_> right
[07:52] <didrocks> (while I was doing devel -> devel-proposed as a subsequent update)
[07:53] <ogra_> you did that all with a readonly image ?
[07:54] <asac> didrocks: really?
[07:54] <asac> didrocks: thats good news :)
[07:54] <didrocks> ogra_: had to pass it rw to change channels.ini
[07:54] <didrocks> asac: indeed! I was quite skeptical myself TBH :p
[07:54] <ogra_> ah so only the last bit in rw
[07:54] <didrocks> yeah
[07:54] <asac> didrocks: did you use apps at all on the old image?
[07:54] <imgbot> [07:54] <imgbot> [07:54] <didrocks> asac: no, it was really about testing recovery
[07:54] <asac> checking how configs might explode
[07:55] <asac> ah
[07:55] <asac> ok
[07:55] <didrocks> I think QA is going to do the real test?
[07:55] <ogra_> ugh
[07:55] <ogra_> so many changes
[07:55] <asac> well, now that we know that it works, we could try to find someone else
[07:55] <didrocks> I was just preparing the rest as we didn't get any news :p
[07:55] <didrocks> yeah
[07:55] <didrocks> I was really worried about that one, so good to know where we stands for
[07:55] <didrocks> and having a positive news)
[07:55] <didrocks> ogra_: most of the changes are rsalveti's rebuild for shlibs
[07:55] <asac> ogra_: yeah, that might mean dead to the idea of producing a better image. lets hope
[07:55] <didrocks> ogra_: so don't be so afraid
[07:55] <ogra_> some of them, yes
[07:56]  * didrocks updates to get new Mir and see
[07:57] <ogra_> hmmm
[07:57] <ogra_> my phone woke up, i opened system-settings and now it is stuck
[07:57] <asac> ogra_: unity crash?
[07:57] <ogra_> doesnt take input
[07:58] <ogra_> asac, well, might be, the screen is still on
[07:58] <ogra_> with system-settings on it
[07:58] <asac> sounds like something is freezing
[07:58] <asac> might dump core
[07:58] <ogra_> so if it crashed  it doesnt repawn
[07:58] <didrocks> be patient
[07:58] <didrocks> it's a whole minute :)
[07:58] <didrocks> check if something appeared in /var/crash
[07:58] <didrocks> with a growing size
[07:59] <didrocks> ok, after reboot with new Mir, I have an UI
[07:59] <didrocks> ship it! :)
[07:59] <ogra_> ok, it respawned now
[07:59] <didrocks> I don't see perf enhancement :/
[07:59] <ogra_> thats a very odd user experience
[07:59] <ogra_> i doubt an enduser will wait that long and just reboot
[08:00] <ogra_> -rw-r----- 1 phablet whoopsie  6696880 Apr 15 09:59 _usr_bin_system-settings.32011.crash
[08:00] <ogra_> -rw-r----- 1 phablet whoopsie 31881265 Apr 15 09:59 _usr_bin_unity8.32011.crash
[08:00] <ogra_> 31M ... sigh
[08:00] <asac> ogra_: probably ricks crash
[08:01] <ogra_> yeah, smells very much like it
[08:01] <asac> maybe it got fixed by the crash that only happens on shut down :)
[08:01] <ogra_> oh !
[08:01] <asac> and thats why they wanted that in
[08:01] <asac> ogra_: thats not on the latest, right?
[08:01] <ogra_> seems download-manager did its job while the system was hung+
[08:01] <didrocks> asac: because ogra asked to shutdown his unity8! :)
[08:01] <ogra_> asac, 294
[08:01] <didrocks> (j/k)
[08:01] <asac> at least our services dont get torn down
[08:01] <didrocks> I know what you mean :p
[08:01] <asac> :)
[08:02] <didrocks> ok, after a 5 minutes play, at least, nothing major
[08:02]  * ogra_ got the reboot dialog immediately after opening updates after the crash
[08:02] <asac> didrocks: on the new mir image?
[08:02] <didrocks> asac: yep
[08:02] <asac> didrocks: i tell you they fixed the crash that ogra is seeing :)
[08:02] <didrocks> asac: let's hope it's the same :)
[08:02] <didrocks> we'll know if the crash is really fix however in some hours only
[08:03] <didrocks> when the AP for that image will run
[08:03] <asac> yeah
[08:03] <didrocks> or maybe
[08:03] <didrocks> let me run them
[08:03] <asac> didrocks: try to get a backtrace from your .crash
[08:03] <asac> :)
[08:03] <asac> or upload to a bug at least
[08:03] <asac> or not :)
[08:03] <asac> ogra can do that
[08:03] <didrocks> asac: I mean, you talk to ogra, right?
[08:03] <asac> oh right
[08:03] <asac> you didnt see it yet :P
[08:03] <didrocks> yep :)
[08:03] <didrocks> let me run AP tests
[08:03] <asac> ogra_: can you try to retrace that one?
[08:04] <didrocks> (AP tests started)
[08:05] <ogra_> asac, just checking why whoopsie doesnt bother to upload them
[08:05] <didrocks> asac: few tests run, no AP crash! (it crashed on first one)
[08:06] <didrocks> but I do see the rendering is so slowwww compared to #250
[08:06] <didrocks> (UI staggering)
[08:06] <didrocks> was already the cases in recent images
[08:07] <asac> ok
[08:08] <asac> ogra_: whoopsie is supposed to work?
[08:08] <ogra_> asac, yes
[08:08] <asac> ogra_: why didnt we tell rick to use that?
[08:08] <asac> :)
[08:08] <ogra_> asac, well, it is supposed to upload
[08:08] <asac> without interaction?
[08:08] <ogra_> because it should happen automatically
[08:08] <ogra_> right
[08:08] <asac> thought we disabled that to avoid bandwidth etc.
[08:09] <asac> i actually was under the impression we disabled whoopsie automatic upload
[08:09] <asac> saying people should run it manually if there is a crash
[08:09] <ogra_> http://paste.ubuntu.com/7253982/
[08:09] <asac> that was roughly 8 month ago :)
[08:10] <asac> /var/lib/apport/autoreport exists?
[08:10] <ogra_> no, but the MATCH=NULL disables it
[08:10] <ev> asac: huh? Why would we rely on people to manually run whoopsie? That's a recipe for wildly skewed statistics. There were bugs in the upstart job, but if those are fixed we should enable automatic reporting.
[08:10] <ev> as was always the intention
[08:11] <asac> ev: err
[08:11] <asac> ev: if you are on a phone
[08:11] <ogra_> ev, well, look at the job above
[08:11] <asac> you dont want to do that
[08:11] <ogra_> ev, http://paste.ubuntu.com/7253982/
[08:11] <asac> ev: we agreed to not auto upload long ago :)
[08:11] <ev> really? Because it's exactly what Apple and google do
[08:11] <asac> ev: 3g bandwidth
[08:11] <asac> etc.
[08:11] <ev> we agreed to disable it in the face of bugs
[08:11] <ev> whoopsie already is a no-op when you're on 3g data
[08:12] <asac> ok; well, seems to not work still :P
[08:12] <ev> Every time an application crashes on my iPhone, data goes up to either the application developer or to Apple
[08:12] <ev> and the platform and applications are better for it
[08:12] <ogra_> well, it seems pretty explicitly disabled from what i see in the job
[08:12] <ev> they don't rely on developers to manually trigger crash reporting for every general consumer use case
[08:12] <ev> because developers wont use their phones in the same way that consumers do
[08:13] <ev> and because developers will never scale to the degree that consumers do
[08:13] <asac> ev: i am not saying it should be manually forever
[08:13] <ogra_> high hopes :)
[08:13] <asac> but rather opt in
[08:13] <asac> allowing users when there is a crash to decide whether he wants to provide feedback or not
[08:13] <asac> and then remembering that seting
[08:13] <asac> anyhow
[08:13] <ogra_> we have a switch in treh privacy settings for that
[08:14] <ev> that's entirely not how our competitors operate, and for good reason
[08:14] <asac> seems its not working/enabled from what ogra is saying
[08:14] <asac> ogra_: right, is that disabled?
[08:14] <ogra_> but i doubt it does any apport/whoopsie interaction
[08:14] <ev> it can be disabled, and we can give them the opportunity to disable it at first use
[08:14] <ogra_> last time i chgecked it was on
[08:14]  * ogra_ looks
[08:14] <asac> ev: we should ask on first use; until that happens you shouldnt just call home and upload potentially sensitive data.
[08:14] <asac> i havent really used android for a while
[08:15] <ogra_> hmm
[08:15] <asac> err started using a new phone; but if i remember i also got asked something like that
[08:15] <asac> on first use
[08:15] <ogra_> it is off now and i cant tick it
[08:15] <asac> anyhow, seems we agree
[08:15] <asac> :)
[08:15] <asac> ogra_: thats seb128
[08:15] <ev> asac: the plan is to have the first use dialog ask you if you want to turn it off
[08:15] <asac> no?
[08:16] <asac> ev: where is that plan?
[08:16] <asac> in general its what i am saying: ask user on first use what to do
[08:17] <ev> asac: in conversations between myself and the legal team
[08:17] <seb128> what?
[08:17] <ev> right, but to be clear the default will be set to leaving it on
[08:17] <ev> opt-out, rather than opt-in
[08:17] <didrocks> asac: ok, no crash while running the unity8 AP tests…
[08:17] <asac> ev: if you get asked on first use, there is no default
[08:17] <didrocks> asac: however, got a freeze of the whole UI
[08:17] <asac> its a choice
[08:17] <didrocks> completely stuck…
[08:17] <ev> it's a toggle in this case
[08:18] <asac> if we plan to make the dialog so that we trick users to enable it, i would think we should at least have a wider discussion on what we want
[08:18] <asac> didrocks: the freeze isnt a crash?
[08:18] <ogra_> aww
[08:18] <didrocks> asac: doesn't seem so, no crash file, no collect happening
[08:19] <ev> asac: it's not tricking anyone into enabling anything
[08:19] <ogra_> so my former crash left the renderer processes of all open webapps around
[08:19] <ogra_> sigh
[08:19] <asac> ev: we will see :)
[08:19] <ev> it's about being positive about the error reporting experience
[08:19] <ev> asac: we will see?
[08:19] <asac> how the solution looks like
[08:19] <ev> the solution is already established and has been for some considerable amount of time
[08:19] <asac> we have a first start dialog asking that?
[08:20] <asac> didrocks: that happens after AP tests were run?
[08:20] <ogra_> no
[08:20] <didrocks> the UI responsivness seems even worse to me
[08:20] <didrocks> asac: while it was running
[08:21] <didrocks> -/+ buffers/cache:       4254       3613
[08:21] <asac> seb128: i am not sure; ogra mentioned that the error reporting setting doesnt work; thought you might know more
[08:21] <didrocks> -/+ buffers/cache:        400       1434
[08:21] <didrocks> rather
[08:21] <didrocks> so not swapping/mem full
[08:21] <sil2100> didrocks: yeah, me and Mirv noticed something similar before
[08:21] <asac> didrocks: dmesg?
[08:21] <didrocks> sil2100: before == before that image?
[08:21] <asac> sil2100: in an old image?
[08:21] <ogra_> asac, seb128, it worked after a while (two minutes or so) that i tried to tick it
[08:21] <ev> we've already planned out with the design team how it should look. With people coming and going in that department, I haven't followed up on where it stands - I know the first use dialog was stalled for a while. I need to catch up with cimi.
[08:21] <seb128> asac, no, our code didn't change, we are just using dbus to talk to whoopsie iirc ...
[08:22] <seb128> ogra_, ^
[08:22] <sil2100> didrocks: remember when we were running AP tests once because of smoketesting being done? During running unity8 tests I was getting a unity8 hang-up, no crash, just non-responsive
[08:22] <seb128> I would say it's an issue on the whoopsie side
[08:22] <sil2100> *done=gone
[08:22] <asac> ogra_: kk
[08:22] <sil2100> asac, didrocks: on an old image, yes
[08:22] <didrocks> asac: nothing apart from britness and wlan changes
[08:22] <ogra_> seb128, well, i dont think i have ever even touched that area of the settings before (i had seen it once) so i dont know if it ever worked for me
[08:22] <asac> ogra_: did it ever work better?
[08:22] <didrocks> sil2100: hum…
[08:22] <didrocks> let me reboot
[08:23] <asac> ogra_: ah ok
[08:23] <ogra_> asac, i never ticked/unticked the box before and it was ticked the times i opened that page before
[08:23] <sil2100> didrocks: I remember I think I just restarted unity8 from console, pressed the power button twice and the tests moved on
[08:23] <ogra_> this time i saw it untick itself while the page opened
[08:23] <sil2100> didrocks: as it seemed that unity8 hanged becoming unresponsive after stopping
[08:23] <asac> hmm. eventqueue bug?
[08:23] <sil2100> (during restart)
[08:23] <didrocks> ok, let's try a full rerun
[08:23] <ogra_> and trying to tick it again didnt work for about 2min
[08:24] <sil2100> didrocks: from what I understood, Mirv was getting something similar apparently
[08:24] <didrocks> ok, let's see
[08:24] <asac> ogra_: maybe after you enabled, whoopsie started processing the crash files?
[08:24] <asac> ogra_: and thats why system was busy?
[08:24] <ogra_> asac, ?
[08:24] <Mirv> sil2100: yes, I got it once
[08:25] <asac> ogra_: 10:23 < ogra_> and trying to tick it again didnt work for about 2min
[08:25] <ogra_> asac, i only looked at that setting long after the crash appeared
[08:25] <asac> well, whoopsie also has to do something with the .crash file
[08:25] <ogra_> and there are no whoopsie upload processes
[08:25] <ogra_> (and there were none, i checked)
[08:25] <bzoltan> sil2100: Mirv: I would like to land couple of fixes with the line 44
[08:25] <asac> ogra_: ok
[08:25] <asac> then i dont know
[08:26] <ev> whoopsie only reads crash files and shovels them over the wire to daisy.ubuntu.com if a .upload file exists for the .crash file
[08:26] <ev> if something is going wrong in the report creation or processing, that's apport
[08:26]  * ogra_ runs whoopsie-upload-all manually ... 
[08:26] <asac> guess something that ev and seb128 would have to look at if its the same behaviour for other folks
[08:27] <ev> kernel core pipe -> apport -> something that touches .upload (apport-gtk or whoopsie-upload-all) -> whoopsie -> daisy.u.c
[08:27] <asac> e.g. odd behaviour of settings
[08:27] <ogra_> root@ubuntu-phablet:~# sudo -u \#32011 /usr/share/apport/whoopsie-upload-all
[08:27] <ogra_> WARNING: Not running as root, cannot process reports which are not owned by uid 32011
[08:27] <ogra_> so running it manually works fine it seems ...
[08:27] <ogra_> it just doesnt auto-trigger
[08:28] <asac> ogra_: cool. how will you find the error report online?
[08:28] <ogra_> whoopsie keeps a local record or so
[08:28] <asac> ok then lets wait what it tells us
[08:28] <ogra_> there is a UI option too
[08:28] <seb128> asac, ogra_: settings just call defined whoopsie interfaces, I would be surprised if the issue was on our side
[08:28]  * asac excited :)
[08:28] <ogra_> probably this works now
[08:28] <didrocks> asac: sil2100: Mirv: stuck again
[08:28] <didrocks> can you reproduce guys?
[08:28] <Mirv> bzoltan: landing-004
[08:28] <bzoltan> Mirv: thanks
[08:28] <popey> didrocks: will be 2 mins late..
[08:28] <Mirv> hmm, I haven't seen it now
[08:28] <ogra_> seb128, well, the odd behavior of the tickbox seems to be on your side
[08:29] <didrocks> Mirv: try on latest image
[08:29] <ogra_> seb128, i doubt any of the other issues is
[08:29] <asac> seb128: have you ever tried that settting :)?
[08:29] <ogra_> oh, crap, i will be late for the meeting
[08:29]  * ogra_ brb in 5
[08:29] <didrocks> I'll be late as well
[08:29] <didrocks> I have a delivery
[08:29] <seb128> asac, yes, it worked fine and works fine on the desktop as well
[08:29] <didrocks> so 5 minutes
[08:29] <didrocks> ogra_: asac: sil2100: Mirv: popey: davmor2: ^
[08:29] <sil2100> Let me upgrade
[08:30] <sil2100> didrocks: ACK
[08:30] <didrocks> start the unity8 AP tests meanwhile :p
[08:31] <asac> hmm. i only intended to attend the evening meeting
[08:31] <Mirv> didrocks: I'm on it, and I've been running dialer app AP tests mostly
[08:35] <didrocks> coming
[08:37] <ogra_> "All reports uploaded successfully"
[08:38] <asac> ogra_: can you find them now?
[08:39] <ogra_> no, they are not in the page the "previous error reports" option in the system-settings offers
[08:40] <ogra_> and i have no clue where else to look for them
[08:40] <popey> seb128: happy days.. http://popey.com/~alan/phablet/device-2014-04-15-094044.png
[08:41] <seb128> popey, \o/
[08:41] <seb128> thanks for testing ;-)
[08:41] <seb128> ogra_, ^
[08:41] <popey> needs more testing ☻
[08:41] <seb128> didrocks, ^
[08:41] <seb128> right, but that's an improvement ;-)
[08:41] <popey> e.g. the percentage bar issue that I see in bug 1307683 can happen
[08:41] <popey> absolutely
[08:42] <seb128> is that issue new since that click fix?
[08:42] <seb128> or was it here before?
[08:42] <popey> i saw it in #294 for sure
[08:42] <popey> seems intermittent
[08:42] <seb128> k, weird
[08:42] <Chipaca> ToyKeeper: you still there?
[08:42] <seb128> if it's intermittent I would say it's an issue with the service/dbus communication between the service<->settings
[08:44] <seb128> ogra_, is bug #1307687 still happening with yesterday's settings update? we tweaked the scrolling bounds in that update
[08:45] <ogra_> seb128, dunni, it is already downloaded ... (so i always get the reboot option immediately when opening that page)
[08:45] <ogra_> seb128, i'll keep an eye open for it on the next update
[08:46] <seb128> ogra_, danke
[08:46] <asac> the update thing looks good
[08:53] <seb128> ;-)
[08:56] <Laney> when that swipe up thing happens you get stuck in the page somehow
[08:56] <Laney> 'back' doesn't work
[08:56] <ogra_> right
[08:56] <ogra_> but eventually the download has finished and you get a reboot question
[08:56] <Laney> I don't even understand how that can happen
[08:56]  * Laney plays the x-files theme
[08:57] <ogra_> lol
[09:01] <ogra_> asac, ev, so while /var/crash claims the reports have been uploaded, i cant find it on e.u.c  ... https://errors.ubuntu.com/?release=Ubuntu%2014.04&package=unity8&period=day&version=7.85%2014.04.20140410.1-0ubuntu1
[09:03] <sil2100> Mirv: can you give that merge a review-try again? :) If anything, I built packages from this branch for testing in ppa:sil2100/qt
[09:03] <ev> ogra_: pm me the output of this sudo gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.GetIdentifier
[09:03] <ev> on that device
[09:04] <popey> davmor2: didrocks http://popey.com/~alan/phablet/device-2014-04-15-100423.png
[09:04] <popey> got a screenshot of it ☻
[09:04] <didrocks> popey: nicely done!
[09:04] <seb128> Laney, you still get it with the current version?
[09:04] <seb128> Laney, Ken made changes to avoid the scrolling
[09:07] <Laney> seb128: dunno about the bug
[09:08] <Laney> but how can you get stuck in a screen?
[09:09] <seb128> Laney, seems like a toolkit issue if that really happens, I can't confirm though ... what do you do exactly?
[09:09] <Laney> swipe up to get into that blank state
[09:09] <Laney> then try to go back
[09:09] <seb128> swipe up does nothing for me
[09:09] <seb128> is that specific to the device or do you get it on desktop as well?
[09:10] <Laney> if the initial bug is fixed you might not be able to reproduce it any more
[09:11] <seb128> Laney, well "initial bug", we got https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/update_listview_bounds_fix/+merge/215182 landed
[09:11] <Laney> sure
[09:12] <seb128> that's why I'm asking what version you guys are running
[09:12] <seb128> I guess that means "a version without that change"
[09:12] <Laney> yep
[09:13] <davmor2> popey: nice
[09:14] <didrocks> popey: if the click updates got the +1 for you, I'll just update touch-meta to drop the system updates btw, keep me posted
[09:18] <didrocks> davmor2: in addition to you reaching out the Mir guys on the UI speed
[09:19] <didrocks> davmor2: do you have a bug for the laggyness of the whole rendering?
[09:19] <didrocks> popey: maybe? ^
[09:19] <davmor2> popey: did
[09:20] <thostr_> didrocks: what's the status on preview silos? any estimate when those become available?
[09:20] <didrocks> thostr_: can you give me a line?
[09:20] <didrocks> is it 32?
[09:21] <thostr_> didrocks: no, not ci sheet related
[09:21] <thostr_> didrocks: I was more asking about special kind of silos which we can "block" for days/weeks to prepare new features
[09:22] <didrocks> thostr_: it wasn't ack yet
[09:22] <thostr_> didrocks: cannot recall if it was you or asac calling those preview silos
[09:22] <didrocks> thostr_: and I'm already working at 100% on the release
[09:22] <didrocks> and trying to get regressions fixed
[09:22] <thostr_> didrocks: ack
[09:22] <asac> thostr_: not before release
[09:23] <mandel> sil2100, any idea if silo 11 was et to be landed?
[09:23] <mandel> sil2100, I lost connection last night and I could not talk with sergio about it
[09:23] <Mirv> sil2100: reviewed that merge proposal, and it seemed functionally good too
[09:25] <sil2100> Mirv: thanks!
[09:25] <sil2100> mandel: so, I think the idea was to land it, but we still need someone from QA to sign it off before releasing
[09:26] <mandel> sil2100, ok, very well, do you know if I can do something from my side?
[09:26] <mandel> sil2100, or should I just move to other things? :)
[09:33] <sil2100> mandel: I think you're free right now ;)
[09:35] <popey> didrocks: am doing more tetsing of click updates
[09:35] <didrocks> great!
[09:35] <popey> let me play more before +1ing
[09:35] <didrocks> sure
[09:35] <mandel> sil2100, great, let me know, if you can, any developments :)
[09:35] <didrocks> don't trust French-released code!
[09:35] <sil2100> ;p
[09:35] <popey> awwwwww
[09:35] <didrocks> mandel: from what I know, this will be post-trusty
[09:35] <didrocks> from the description and what was discussed yesterday
[09:36] <didrocks> (if you talk about the media-hub)
[09:36] <popey> you can say that now seb128 isn't in guillotining distance?
[09:36] <mandel> didrocks, I'm talking about the download manager
[09:36] <mandel> didrocks, media-hub is a diff beast hehe
[09:36] <didrocks> ah, ok ;)
[09:36] <didrocks> popey: exactly!
[09:38] <mhr3> didrocks, is the train spreadsheet right in saying that we're at traincon0?
[09:38]  * seb128 see the guillotine mentioned and give the look to didrocks
[09:38] <didrocks> mhr3: we do are in the same situation: QA sign off every feature
[09:38] <didrocks> s/do//
[09:39] <mhr3> didrocks, why? there was promoted image yesterday
[09:39] <didrocks> mhr3: because the promoted image was under the "whitelist blockers"
[09:39] <didrocks> and because the blockers are supposed to be fixed in the next 2 days?
[09:40] <didrocks> remember, we have a trusty release…
[09:40] <mhr3> we still do releases? :P
[09:40] <mhr3> i thought that's a thing of past :)
[09:41] <didrocks> mhr3: well, that's what people will try "ubuntu touch"
[09:41] <didrocks> on
[09:41] <bzoltan> Mirv:  the silo4 is good to land
[09:42] <mhr3> didrocks, j/k thx for explanation
[09:42] <didrocks> mhr3: yw!
[10:04] <Mirv> bzoltan: it looks like sil2100 published it now
[10:05] <sil2100> I published it as soon as I noticed it being yellowish
[10:09] <ogra_>  crap
[10:10] <ogra_> my network dropped again
[10:10] <ogra_> (on the phone)
[10:10] <ogra_> NM is seriously misbeahving since a few days for me
[10:15] <ogra_> bah
[10:15] <ogra_> so NM definitely messes up the routing on my phone
[10:15] <ogra_> http://paste.ubuntu.com/7254444/
[10:15] <Chipaca> om26er: good morning kind sir!
[10:16] <ogra_> popey, davmor2, did one of you notice something like that ? i got it a few times a day
[10:16] <ogra_> suddnely the browser cant find sites anymore etc
[10:16] <ogra_> *suddenly
[10:16] <om26er> Chipaca, hey ;)
[10:17] <Chipaca> om26er: let me know when you're set to finish this
[10:17] <popey> ogra_: no, but that could explain bug 1307051 and bug 1307052
[10:17] <ogra_> hmm
[10:17] <Chipaca> om26er: on the "good news" front, rhuddie is working on making autopilot do these checks :)
[10:17] <ogra_> i'll file a NM one ... lets see
[10:17] <om26er> Chipaca, ok, in 10 minutes. I am doing lunch atm
[10:17] <om26er> Chipaca, that's great to hear
[10:18] <Chipaca> om26er: buen provecho! ping me when you're lunched
[10:23] <ogra_> bug 1307981
[10:23] <ogra_> popey, in case you run into networking issues, please check routing and (possibly) confirm
[10:23] <popey> ok
[10:23] <ogra_> davmor2, ^^^you too
[10:24] <popey> i rarely leave the house, so it doesn't happen often ☹
[10:24] <ogra_> ?
[10:24] <ogra_> it happens to me with a phone that didnt leave the room
[10:26] <davmor2> Morning all
[10:27] <davmor2> ogra_: I've not had any issue but I'll keep my eyes open
[10:27] <ogra_> k
[10:27] <didrocks> ogra_: stop throwing your phone out of the window!
[10:27] <didrocks> that's how the screen broke
[10:27] <ogra_> lol
[10:27] <ogra_> nah, it broke in oakland :P
[10:29] <popey> seb128: should system-settings tell me there are updates available to click apps, or does it only say "1 update available" at the top when there's system image updates?
[10:29] <ogra_> i thinnk thats something the push service is supposed to do
[10:29] <ogra_> (once we get it back)
[10:29] <om26er> Chipaca, ok, I think we can do the testing now
[10:30] <seb128> popey, sorry, I'm not sure to parse that question right ... it should list all updates available, system and clicks
[10:30] <seb128> popey, system being one entry, usually listed first, then followed by clicks
[10:30] <Chipaca> om26er: ok. before going ahead, could you pastebin ~phablet/.cache/upstart/ubuntu-push-client.log ?
[10:31] <seb128> popey, the label should be "<n> updates available" where n = system_image + n_click
[10:31] <om26er> Chipaca, http://paste.ubuntu.com/7254526/
[10:32] <Chipaca> om26er: interesting; you had a bit of trouble there, but it's sorted now
[10:33] <om26er> Chipaca, that might be network disconnect
[10:34] <Chipaca> om26er: i've asked for notifications to be sent; i'll let you know once i get an ack
[10:34] <om26er> Chipaca, btw how do you know my device name ?
[10:35] <Chipaca> om26er: you mean, system-image-cli -i ?
[10:35] <Chipaca> om26er: I don't; the notifications we're sending out cover everything right now
[10:36] <om26er> Chipaca, no I meant how do you send a message to me without knowing my device ID etc, but I guess you send the same message to everyone who have the client installed ?
[10:36] <Chipaca> om26er: system updates are broadcast, yes
[10:36] <popey> seb128: ok
[10:36] <popey> seb128: i dont see that
[10:36] <Chipaca> om26er: unicast notifications are in the future still
[10:36] <seb128> popey, what do you see?
[10:36] <Chipaca> om26er: rick wanted it this way around :)
[10:36] <popey> seb128: http://popey.com/~alan/phablet/device-2014-04-15-113641.png
[10:36] <Chipaca> *round
[10:36] <Chipaca> round*
[10:36] <om26er> Chipaca, cool
[10:37] <popey> seb128: i have not visited the updates screen yet
[10:37] <popey> seb128: and i know i have a bunch
[10:37] <popey> seb128: http://popey.com/~alan/phablet/device-2014-04-15-113739.png
[10:38] <seb128> popey, that screenshot seems about right? what is the issue?
[10:38] <popey> seb128: i see no indication of updates at the top
[10:39] <seb128> popey, oh, sorry, I misread what you ask .. "Install 41 updates" label in the button is the indication
[10:39] <seb128> popey, that's the design https://wiki.ubuntu.com/SoftwareUpdates?action=AttachFile&do=get&target=phone-settings-updates-available.png
[10:40] <popey> seb128: no, i mean, on the screen http://popey.com/~alan/phablet/device-2014-04-15-113641.png - below search usually i see a notification there's a system update waiting
[10:41] <popey> my question is - should I see a notification there for click updates too, or do we only notify users of system updates?
[10:43] <bzoltan> sil2100: Mirv: thank you
[10:44] <seb128> popey, oh ok, yes we should for click, I don't think we tested that though/not sure if that got implemented
[10:44] <seb128> popey, can you open a bug about it?
[10:44] <popey> sure thing
[10:44] <Laney> I think it's that the visibility isn't set if you have only click updates
[10:45] <Chipaca> om26er: ok, ready?
[10:45] <om26er> Chipaca, yes
[10:45] <Chipaca> om26er: sent
[10:45] <om26er> Chipaca, it works :)
[10:45] <Chipaca> om26er: \o/
[10:46] <om26er> Chipaca, approved, its a go now.
[10:46] <Chipaca> sweet
[10:47] <Chipaca> om26er: thanks!
[10:47] <Chipaca> sil2100, Mirv, didrocks: got a +1 from QA :) does that mean i can ask you to land it?
[10:48] <popey> seb128: ok done, bug 1307993
[10:48] <seb128> popey, thanks
[10:48] <didrocks> Chipaca: published!
[10:48] <didrocks> Chipaca: we'll kick an image as soon as it landed
[10:49] <sil2100> :)
[10:51] <Mirv> nice
[10:55] <Chipaca> didrocks: sil2100: Mirv: party mode is ON
[10:55] <didrocks> Chipaca: another bottle of champaign? :)
[10:55] <Chipaca> didrocks: no, not on a tuesday. Just a silly hat.
[10:56] <sil2100> ;p
[10:56] <didrocks> ;)
[10:56] <Chipaca> freenode doesn't let me nick to Chipâca
[10:56] <Chipaca> so you'll have to take my word for it
[10:56]  * Chipaca is lying
[10:56] <Chipaca> ssh, you
[11:00]  * popey steps away from the irc
[11:02]  * sil2100 goes for lunch
[11:20] <dpm> hi psivaa, would it be possible to trigger a Jenkins run for https://code.launchpad.net/~dpm/ubuntu-filemanager-app/include-plugin/+merge/213368 ? For some reason it hasn't run ever since the last change in the branch was done a couple of hours ago
[11:21] <psivaa> dpm: just a sec
[11:23] <dpm> cool, thanks
[11:38] <didrocks> Chipaca: kicking an image with push notification
[11:42] <didrocks> davmor2: still all good on dogfooding side for now?
[11:42] <davmor2> didrocks: I'll get back to you but there seems to be nothing worse that yesterday so far
[11:43] <davmor2> than even
[11:43] <didrocks> good :)
[11:44] <imgbot> [11:45] <psivaa> dpm: http://91.189.93.70:8080/job/ubuntu-filemanager-app-ci/164/console appears to have run successfully
[11:47] <dpm> psivaa, excellent, thanks! Will it take a while for the Jenkins approval to show up in https://code.launchpad.net/~dpm/ubuntu-filemanager-app/include-plugin/+merge/213368 ?
[11:47] <Mirv> bzoltan: you can merge & clean landing-004 now, all in release pocket now
[11:55] <bzoltan> Mirv: Cool, thanks
[11:57] <dpm> psivaa, could it be that jenkins ran on the wrong MP? The results you show me correspond to https://code.launchpad.net/~nskaggs/ubuntu-filemanager-app/ap-binary-support/+merge/215724
[11:57] <dpm> but I was expecting it to run on https://code.launchpad.net/~dpm/ubuntu-filemanager-app/include-plugin/+merge/213368
[11:57] <ogra_> line 22 would be ready ... unless someone thinks this needs specific QA signoff
[11:58] <didrocks> ogra_: easy revertable, so I would say, go ahead and publish
[11:58] <popey> seb128: in updates I have 41 of them, and i tapped install, strangely the UI started randomly scrolling down.. then started scrolling up again...
[11:58] <psivaa> dpm: yes, it could be. i picked up from the latest rebuild, wich had balloons's branch. i've kicked the one with your branch now: https://code.launchpad.net/~dpm/ubuntu-filemanager-app/include-plugin/+merge/213368
[11:58] <ogra_> right, its zero risk
[11:59] <dpm> psivaa, thanks
[11:59] <seb128> popey, I'm not sure we tested with a list going over the screen, seems like worth another bug report
[11:59] <psivaa> dpm: http://91.189.93.70:8080/job/ubuntu-filemanager-app-ci/165/ si the new one. sorry about it earlier
[11:59] <popey> seb128: ok
[11:59] <seb128> thanks
[11:59] <dpm> psivaa, no worries, thank you!
[11:59] <Laney> You should ping gatox instead of poor seb128 about updates UI bugs
[12:00] <Laney> or I guess just file them ...
[12:00] <popey> ☹
[12:10] <sergiusens> didrocks: om26er not sure who to contact; but can we get a second QA look on https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=29
[12:11] <didrocks> sergiusens: it's om26er on that time, but I guess he's looking at every entry having QA testing needed to yes
[12:11] <sergiusens> seems it was misled yesterday by the failing jenkins MR for the scope as it was failing; which is as expected
[12:11] <ogra_> didrocks, hmm http://paste.ubuntu.com/7254934/
[12:11] <ogra_> did i do something wrong ?
[12:11] <sergiusens> didrocks: yeah, just trying to uncross off a possible list
[12:12] <didrocks> ogra_: when you did run build with "watch only", did it detect lxc-android-config?
[12:12] <ogra_> yes
[12:12] <didrocks> ogra_: do you have that log?
[12:12] <ogra_> the main sheet updated properly with each setp i did
[12:12] <ogra_> which log ?
[12:12] <didrocks> ogra_: of the build job
[12:12] <didrocks> ogra_: as told, it doesn't fail on purpose as you may upload it afterwards
[12:13] <didrocks> and rekick a watch only
[12:13] <sergiusens> mandel: can you track with om26er? ^^
[12:13]  * sergiusens needs to make a coffee run; all out
[12:13] <ogra_> didrocks, you mean this ? https://ci-train.ubuntu.com/job/landing-006-1-build/23/console
[12:14] <didrocks> ogra_: yeah, see you don't see "lxc-android-config"
[12:14] <didrocks> ogra_: just rerun it with watch only
[12:14] <didrocks> I guess the source is published now
[12:14] <mandel> om26er, ping me if you need anything, I think the test plan is clear enough
[12:14] <ogra_> i did run with watch only
[12:14] <ogra_> weird
[12:15] <didrocks> ogra_: too early, before lxc-android-config source was published, I guess?
[12:15] <ogra_> (and the package said it was published on LP)
[12:15] <didrocks> ogra_: don't trust it that status, I've been tricked sometimes ;)
[12:15] <didrocks> ogra_: see, it's in now
[12:15] <didrocks> and publish will let you pulish
[12:16] <didrocks> even publish
[12:17] <ogra_> yep, works ... it seems
[12:18] <didrocks> :)
[12:21] <ogra_> sergiusens, hmm ... just seeing https://code.launchpad.net/~sergiusens/phablet-tools/package_install/+merge/215777 ... didnt we say we dont want to apt-get update beofre tests ?
[12:22] <ogra_> (even though that can cause probs you want to test against the state the image had at build time)
[12:23] <sergiusens> ogra_: well I'm trying to address the bug;
[12:23] <sergiusens> ogra_: I can add a switch perhaps
[12:23] <ogra_> iirc asac wanted it explicitly to not apt-get update back in the days
[12:23] <ogra_> but that might have changed :)
[12:24] <sergiusens> ogra_: it runs update when ppas and custom tars are added
[12:24] <ogra_> iirc that was stemming from the fact that we couldnt be sure AP in the archive didnt get updated inbetween
[12:24] <sergiusens> true we may not want to update
[12:24] <sergiusens> doanac: plars can you look at the above MR? ^
[12:24] <ogra_> well, for PPAs it indeed has to update
[12:24] <ogra_> i dont know a way to make apt do a selective update with only adding the PPA info
[12:25] <sergiusens> ogra_: the ideal solution is to NOT go into writable mode for image testing ;-)
[12:25] <ogra_> ++
[12:25] <ogra_> time to revisit in U
[12:25] <ogra_> :)
[12:26] <asac> ogra_: sergiusens: yes, we dont want apt-get update because only if we do that we can parallelize image production while test are running
[12:26] <ogra_> asac, the prob is if people try to test against an older image
[12:26] <asac> we explicitely kicked that out for that reason
[12:26] <asac> ogra_: sure, then the package is gone
[12:26] <ogra_> we had that a few times when people tried some tests against promoted
[12:26] <asac> but better than pretending you test that image (which you dont .. .you test something undefined)
[12:27] <asac> ogra_: the problem is that we dont keep the debs around afaik
[12:27] <ogra_> we do
[12:27] <asac> sure in librarian
[12:28] <asac> but we dont resolve that magically
[12:28] <ogra_> but apt doesnt know about them anymore once they are supeseded
[12:28] <sergiusens> asac: can you address https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1284612
[12:29] <ogra_> if we cant force testing into redonly we should consider reworking the rw test with launchpadlib calls to pull the right versions
[12:29] <asac> sergiusens: if this is a tool to install a package it should probably update
[12:29] <ogra_> would be rather complex though
[12:29] <asac> sergiusens: or get a flag that allow updating
[12:30] <sergiusens> asac: right, the flag is fine
[12:30] <asac> sergiusens: however, i am talkinga bout phablet-test-run behavioru. that thing surely shouldnt
[12:30] <asac> udpate by default
[12:30] <ogra_> asac, well, as i said above you cant add a PPA without apt-get update
[12:30] <sergiusens> ogra_: the problem with launchpad lib is the dependency management
[12:30] <ogra_> if you test landings you are forced to do it
[12:31] <asac> hmm
[12:31] <sergiusens> asac: yeah, reason for asking doanac and plars to review; this code is there for ci and others have started to use it
[12:31] <sergiusens> we really need to NOT use debs for the autopilots
[12:31] <sergiusens> period
[12:31] <didrocks> psivaa: mind restarting mediaplayer-app test?
[12:31] <didrocks> (now that the image test is over)
[12:31] <didrocks> and before next image is published
[12:33] <psivaa> didrocks: ack, running. sorry missed it before
[12:33] <didrocks> no worry :)
[12:35] <mardy> asac: hi! Are there any news about the request of decoupling trunk from the archive image?
[12:36] <mardy> asac: if you are looking for pilots, I volunteer :-)
[12:38] <asac> mardy: the call I mentioned was pushed to next week - after release. I assume we will work on planning this out after that
[12:40] <didrocks> ogra_: seems we just went above the threshold for settle after on calculator app, but not that much, so seems to just be noise
[12:40] <didrocks> u-s-c isn't that high
[12:40] <didrocks> but contributed
[12:41] <didrocks> ogra_: you can m&c FYI
[12:42] <ogra_> oh, sorry
[12:42] <didrocks> (which will, in your case, just delete the package from the ppa and free the silo)
[12:42] <didrocks> ogra_: no worry, we aren't low in silos
[12:43] <mardy> asac: OK, thanks
[12:44] <didrocks> ok, time for running I guess!
[12:44] <imgbot> [12:44] <imgbot> [12:45] <didrocks> Chipaca: FYI ^
[12:45] <didrocks> this is YOUR image :)
[12:45] <Laney> haha
[12:45] <Laney> run and hide
[12:45] <ogra_> massive changes !!!
[12:46] <davmor2> Chipaca: don't act like it's a good thing though, it means you and your team get to fix everything that goes wrong with it :D
[12:47] <Chipaca> didrocks: davmor2: I'm going to take it home and hug it and squeeze it and pet it and lock it in a cage and keep it forever.
[12:47] <didrocks> heh
[12:48] <ogra_> didrocks, dang, so we cant publish it
[12:48] <davmor2> Chipaca: photo's or it didn't happen
[12:48] <didrocks> ogra_: we will! ;)
[12:48] <didrocks> anyway, really running now :p
[12:50] <Chipaca> I'm going to make myself a tee with “I have an image.”
[12:57] <Saviq> didrocks, line 24 has "QA sign off needed: Yes", not sure who set it so, but shouldn't this only be there for features? it's a rather small bugfix landing?
[13:11] <om26er> mandel, we need to run the testplan for ubntu-click-scope as well given that's a dependency of u-d-m
[13:11] <om26er> that's not mentioned in the testplan page
[13:21] <om26er> mandel, also do you know what else other than unity-click-scope uses ubuntu-download-manager ? we need to ensure anything that uses it is also tested
[13:22] <Saviq> cihelp: I've filed a bug about unity8 otto runs being down: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1308062
[13:24] <fginther> Saviq, ack on the bug report. I've been looking at this off and on for the past couple days. I'm looking at an alternative to otto to get this going again
[13:28] <fginther> Saviq, do you see any issues when running on a desktop under unity7?
[13:28] <fginther> Saviq, any unity8 autopilot test issues?
[13:29] <Saviq> fginther, no, that works fine
[13:29] <Saviq> fginther, I've been playing with the idea of running them under xvfb with autopkgtests
[13:29] <Saviq> fginther, this way we'd at least have a way to reproduce locally
[13:29] <fginther> Saviq, I've also been playing with running them on a VM as we used to.
[13:30] <Saviq> fginther, uh... feels like a step back :/
[13:34] <fginther> Saviq, agreed, but don't want to discount any option that might get things running again
[13:34] <Saviq> fginther, understood
[13:47] <zsombi> cjwatson: ping
[13:48] <cjwatson> zsombi: hi
[13:48] <zsombi> cjwatson: I'll have an updated branch soon 4 U
[13:50] <cjwatson> ok
[13:53] <zsombi> cjwatson: lp:~zsombi/ubuntu-ui-toolkit/dynamic-tabs-test-failure has some changes, could you check it with arm64? thx!
[13:56] <bfiller> sil2100: could you please reconfigure silo 14 to remove qtorganizer5-eds? And then create a silo for line 28 which has multiple qtorgranizer5-eds bug fixes
[13:58] <cjwatson> zsombi: two runs of just tst_tabs passed; let me try a full build/test
[13:58] <sil2100> bfiller: let me take a look at that one
[13:58] <sil2100> didrocks: if you have a moment, I would need a packaging ACK for this one: https://ci-train.ubuntu.com/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_appmenu-qt5_0.3.0+14.04.20140415-0ubuntu1.diff
[13:59] <zsombi> cjwatson: huhh??! now that's weird!!!
[14:00] <cjwatson> well, your last iteration passed with the extra delays, I just figured you'd done a better version of that
[14:05] <sil2100> bfiller: both things - done
[14:06] <bfiller> sil2100: thank you
[14:10] <didrocks> Saviq: not for the one which was discovered by QA and are spot lighted (on the release blocker list)
[14:11] <didrocks> sil2100: +1
[14:11] <Saviq> didrocks, that one's not a blocker, afaik?
[14:11] <sil2100> Thank you o/
[14:11] <didrocks> Saviq: it's a "need to be fixed before release"
[14:12] <didrocks> Saviq: like the Qt one
[14:12] <Saviq> didrocks, so a blocker - should be marked as such :P
[14:12] <didrocks> Saviq: we didn't put as promotion blocker
[14:12] <didrocks> Saviq: or we wouldn't have promoted yesterday
[14:12] <Saviq> didrocks, ok is fine
[14:13] <Saviq> in any case
[14:13] <Saviq> it's ready for QA sign off
[14:13] <didrocks> Saviq: " * Important bugs to track before trusty release:"
[14:13] <didrocks> Saviq: that's how I labelled it, if you think I should change… :)
[14:13] <didrocks> om26er: can you please test that one as a priority? ^
[14:13] <zsombi> cjwatson: let me know when you get some news on my branch...
[14:13] <Saviq> didrocks, whatever, is fixed already ;)
[14:13] <didrocks> om26er: line 24
[14:13] <didrocks> Saviq: excellent news!
[14:13] <didrocks> Saviq: so, the "no dialer app showing" and messaging app, was all the same, right?
[14:14] <didrocks> just greeter not unlocking?
[14:14] <om26er> doanac, ok, on it
[14:14] <om26er> oops
[14:14] <om26er> didrocks, ^
[14:14] <didrocks> thanks om26er :)
[14:14] <didrocks> Saviq: also, the "cover 3 components" weight in the decision
[14:15] <Saviq> didrocks, yeah, there's one more: bug #1305128, but not a blocker/important AFAICT
[14:15] <didrocks> Saviq: thanks for the quick fix btw!
[14:15] <Saviq> didrocks, thank mterry!
[14:15]  * didrocks does
[14:15] <didrocks> Saviq: oh, that even user facing?
[14:15] <didrocks> let me open the bug
[14:15] <Saviq> didrocks, with content-hub yes
[14:16] <didrocks> interesting
[14:16] <didrocks> Saviq: yeah, reading the description, we have more important issues IMHO
[14:16] <davmor2> didrocks: dogfooding complete at last.  it looks like the only new issue I have is merging multiple calls but that might not be supported by my provider so I'm going to play about with that a bit and report an issue if there is one
[14:16] <didrocks> davmor2: ok, so not a regression in any way!
[14:17] <didrocks> davmor2: it was #295, right?
[14:17] <didrocks> or #296?
[14:17] <zsombi> cjwatson: actually seems a simple idle timer (wait(0)) would also be enough there... but let's get this done first
[14:18] <didrocks> should be 296 actually
[14:18] <davmor2> didrocks: 296
[14:18] <didrocks> davmor2: nice, so with the new Mir!
[14:18] <didrocks> davmor2: can you do a light dogfood of 297? (it's 296 + push notifications)
[14:18] <didrocks> davmor2: I guess we'll have another image kicked soon, so not a full test, but just to see if you don't spot any regression
[14:19] <didrocks> ogra_: mind promoting #296?
[14:19] <ogra_> not at all
[14:19] <didrocks> all indicators are green!
[14:19] <didrocks> \o/
[14:19] <didrocks> ogra_: you should have your command line in ctrl + R :p
[14:19] <ogra_> thats  a bug
[14:19] <didrocks> ahah
[14:19] <ogra_> the indicators are surely not supposed to be green :P
[14:20] <didrocks> ogra_: it's the new greenpeace theme!
[14:20] <ogra_> lol
[14:20] <sil2100> ;p
[14:20] <cjwatson> zsombi: full build passed
[14:20] <sil2100> Yay for promotions \o/
[14:20] <sil2100> It's been so long since we had a promotion-streak that I think we need to celebrate this somehow
[14:21] <didrocks> agreed
[14:21] <zsombi> cjwatson: awesome! I'll give you one more snapshot, let's get tested with that as well
[14:21] <didrocks> we are too close to not have image #300 as the one we switch on the stable image :p
[14:21] <cjwatson> zsombi: ok
[14:21] <ogra_> didrocks, hmm, that messaging-app crash is new
[14:21] <sil2100> messaging-app crash?
[14:22] <ogra_> (telepathy-ofono in the messaging-app test)
[14:22] <didrocks> ogra_: we had it in the past IIRC (I checked this morning)
[14:22] <ogra_> hmm, when ?
[14:22] <ogra_> not in the last one
[14:22] <didrocks> like 8-10 images ago
[14:22] <ogra_> we had it with dialer a few times
[14:22] <didrocks> it was on and off
[14:22] <davmor2> didrocks: next image is 297a right?
[14:22] <didrocks> yeah, but also with messaging-app
[14:22] <ogra_> k
[14:22] <didrocks> davmor2: no, it's 297b! :)
[14:22] <didrocks> :p
[14:23] <didrocks> Chipaca: confirmed on the dashboard that push notification didn't kill unity8 AP tests at least!
[14:23] <Chipaca> didrocks: foiled again!
[14:23] <ogra_> yeah, you are totally breaking our chance of having 300 for release
[14:23] <didrocks> sil2100: mind checking gallery-app?
[14:24] <didrocks> ogra_: are we must refrain!
[14:24] <Chipaca> hey, i can ask you to rerun that with an updated push client
[14:24] <didrocks> or have 333
[14:24] <ogra_> oh, then lets hurry up ...
[14:24] <didrocks> Chipaca: you need to ask doanac with the self-service test system
[14:24] <didrocks> Chipaca: we can only test images here
[14:25] <didrocks> ogra_: disable the cron job! :)
[14:26] <ogra_> grrr
[14:26] <sil2100> didrocks: aye!
[14:26] <Chipaca> or we could claim the openssl in the image has a bug whereby if you say "please" it gives you *all* the passwords, not just some of them
[14:26] <ogra_> usage: copy-image [-h] [-k] [--verbose]
[14:26] <ogra_>                   SOURCE-CHANNEL DESTINATION-CHANNEL DEVICE VERSION
[14:26] <ogra_> copy-image: error: Can't find version: 296
[14:26] <ogra_> stgraber, ^^^i thought we had synced up the image versions for the emulator builds ?
[14:26] <didrocks> Chipaca: as long it forces you to be polite… :)
[14:27] <Chipaca> didrocks: people finding that bug will just *know* it's the MI5
[14:27] <didrocks> heh ;)
[14:27] <zsombi> cjwatson: one more try then, pls :)
[14:27]  * sil2100 upgrades and checks the logs in the meantime
[14:27] <mandel> om26er, udm is a dependency of click-scope and AFAIK both projects have testng plans
[14:27] <mandel> om26er, the udm test plan covers on single step of the click-scope as well as a single one of image updates
[14:28] <om26er> mandel, the way we tackle this is that we ensure all the reverse deps for a service (u-d-m in this case) are mentioned in the test plan, so that someone testing that component knows and makes sure to execute all the required test plans
[14:29] <om26er> mandel, also is click-store and image updater the only consumers for downloader in default image ?
[14:30] <imgbot> [14:31] <cjwatson> zsombi: if this is racy, how about I wait for my pending mir build to finish ...
[14:31] <stgraber> ogra_: we did...
[14:31] <ogra_> stgraber, oh ... i see, generic_x86 never had a promotion
[14:31] <mandel> om26er, yes, they are the only clients in the image. In the test plan of udm both are mentioned (https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-download-manager)
[14:31] <zsombi> cjwatson: the wait(0) doesn;'t differ too much from the wait(1) :) but I thought it woudl be good to try before we push it for landing
[14:32] <renato> sil2100, I am having problems with the new Qt Signal/Slot connection syntax on powerpc arch, do you know something about that?
[14:32] <zsombi> cjwatson: how long would that take?
[14:32] <ogra_> hmm, and the fact that it is an x86 build minght mean the build is queued somewhere on a buildd ...
[14:32] <mandel> om26er, in the test plan we are touching all those parts in which udm is fundamental, testing that installed apps are shown in the click scope in order to land udm does not make much sense
[14:32] <stgraber> ogra_: hmm, also doesn't explain why generic_x86 is two builds behind...
[14:32] <ogra_> copy-image is actually right
[14:32] <ogra_> there is no 296 for generic_x86
[14:32] <mandel> om26er, nevertheless I have run all the tests in the click-scope
[14:32] <stgraber> oh yeah, of course, since they don't share the build chroot, there's no guarantee that they'll stay in sync at all
[14:32] <ogra_> stgraber, busy buildds ?
[14:33] <stgraber> because you may trigger the x86 one more often or it may fail while the armhf one doesn't
[14:33] <om26er> mandel, great, we just need to update the u-d-m wiki page to create a header like 'Dependents/Client' as seen in this test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/media-hub
[14:33] <ogra_> well, they are in sync in cdimage
[14:33] <ogra_> so the trigger should trigger both arches at the same time
[14:33] <ogra_> but if the livefs builder has a queue ...
[14:34] <sil2100> didrocks: so, just finished upgrading now, but from the logs I see that we already had this test failing before... it seems to be the same issue as reported here: https://bugs.launchpad.net/gallery-app/+bug/1304950
[14:35] <sil2100> didrocks: although the final error is different
[14:35] <cjwatson> zsombi: not exactly sure, 15min maybe?
[14:35] <sil2100> didrocks: I suspected before that the toolbar didn't appear and the click wasn't properly registered - this time it seems to be the same I guess, but it fails in an earlier stage
[14:35] <cjwatson> it's at 82% in cmake but who knows what that means
[14:35] <zsombi> cjwatson: ok... then I'll hand it over to t1mp, I'll go EOD
[14:36] <sil2100> renato: hi! Sadly, didn't encounter that yet, so I guess I cannot help with this one
[14:36] <cjwatson> hopefully the answer will be "yes" and then it's easy
[14:37] <didrocks> sil2100: ok, let's see what QA can say
[14:37]  * didrocks restarts collecitng the flaky tests list
[14:38] <bfiller> sil2100: sorry to bug you again about silo14 - needs another reconfiguration, this time with syncevolution added with that MR specified in the comment: https://code.launchpad.net/~renatofilho/ubuntu/trusty/syncevolution/fix-1306112/+merge/215881
[14:38] <sil2100> hah! Indeed
[14:38] <sil2100> bfiller: oh, I think we'll have to do a source package upload to the PPA in this case
[14:38] <bfiller> sil2100: yes I think so
[14:38] <sil2100> bfiller: since this package is not under citrain
[14:39] <bfiller> sil2100: right, recall we had to do that last time as well
[14:39] <sil2100> bfiller: let me reconfigure and push that
[14:39] <mandel> om26er, well, but how am I suppose to know all the clients of udm, I mean, is going to be exposed in qml
[14:39] <mandel> om26er, could be all apps in the store
[14:41] <om26er> mandel, we only care about what comes by default in the image, for example for qtdeclarative i was asked to run all the autopilot tests for all the apps in the image + uitoolkit and unity8
[14:41] <om26er> we probably need to maintain a list of internal consumers of u-d-m
[14:45] <mandel> om26er, well, I have updated the wiki with what I know that uses udm
[14:45] <mandel> om26er, AFAIK only clients atm
[14:45] <om26er> mandel, ok thanks.
[14:46] <om26er> didrocks, Saviq so it seems unity8 silo testing will take a *while* given we have an autopilot test plan to run for this which requires to run all autopilot tests for all apps
[14:47] <mandel> om26er, no problem
[14:47] <didrocks> om26er: it's one of the more important one, so I guess the focus should be there
[14:48] <didrocks> (release blocker)
[14:48] <om26er> didrocks, the focus is there already, device just finished flashing. just wanted to let you guys know
[14:48] <didrocks> om26er: oh sure, I didn't expect it to be quickly done, thanks for the head's up !
[14:48] <sil2100> bfiller: ok, prepared the package and pushed it to the silo PPA, should appear there pretty soon
[14:49] <sil2100> bfiller: in some minutes you can run Build with 'watch-only' I guess
[14:49] <Saviq> om26er, well, the test plan is to test *one* click app, unity8 and UITK manually
[14:49] <Saviq> om26er, or use the gatekeeper automagically
[14:49] <zsombi1> cjwatson: I'm still here :D any update?
[14:49] <om26er> Saviq, since there is a change in autopilot as well, we have to run its testplan as well, which requires us to run all tests
[14:50] <Saviq> om26er, I disagree, that's not what the testplan says
[14:50] <bfiller> sil2100: thanks
[14:50] <sil2100> bfiller: yw!
[14:50] <cjwatson> zsombi1: my other test build's in dpkg-deb right at the end, so will start very shortly
[14:51] <Saviq> om26er, "Run at least one click app autopilot suite..."
[14:51] <om26er> sil2100, https://wiki.ubuntu.com/Process/Merges/TestPlan/autopilot "Dependents/Clients"
[14:51] <zsombi1> cjwatson: I'll wait till that's done then :)
[14:51] <om26er> yeah in train-con0 we are being super precautious
[14:51] <om26er> *cautious rather ;)
[14:51] <Saviq> om26er, then please, find someone to run it automagically
[14:52] <sil2100> om26er: s/sil2100/Saviq ;p
[14:52] <Saviq> om26er, through http://q-jenkins:8080/job/autopilot-release-gatekeeper/ (if you yourself can't)
[14:52] <didrocks> seb128: killing update-manager from touch FYI based on popey's feedback
[14:52] <om26er> sil2100, ^
[14:52] <pmcgowan> does anyone know if a new chromium hit the archives recently
[14:53] <popey> pmcgowan: 34 today
[14:53] <om26er> now that meant for you :)
[14:53] <popey> pmcgowan: i lie, yesterday
[14:53] <Saviq> om26er, it's just a waste of time otherwise :|
[14:53] <seb128> didrocks, thanks
[14:53] <pmcgowan> popey, well, it is severely busted me thinks
[14:53] <popey> pmcgowan: i haven't restarted it since.. thanks ☻
[14:54] <pmcgowan> all my plugins are gone and cant install more
[14:54] <didrocks> pmcgowan: you should ping qengho on #ubuntu-desktop
[14:54] <om26er> Saviq, the reason is because some apps use certain autopilot features which other dont. and autopilot breakage can be catastrophic
[14:54] <ogra_> just use oxide
[14:54] <pmcgowan> ogra_, doesnt do plugins either ;(
[14:54] <popey> yeah, no problem with plugins there!
[14:55] <ogra_> heh, true
[14:55] <popey> dammit
[14:55] <pmcgowan> popey, works for you?
[14:55] <popey> I mean, no problem as there are none.
[14:55] <ChickenCutlass> lol
[14:55] <ChickenCutlass> right
[14:55] <pmcgowan> right
[14:55] <t1mp> cjwatson: let me know when you test the changes that zsombi made in https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/dynamic-tabs-test-failure/+merge/215886
[14:55] <Saviq> om26er, sure, that's ok, but doing it by hand is just crazy, they even have a jenkins job that does that already
[14:55] <t1mp> cjwatson: if it all works, I will happrove and we can land it
[14:55] <Saviq> it's even called "autopilot release gatekeeper"
[14:55] <cjwatson> t1mp: test's running now
[14:56] <t1mp> cjwatson: cool, thanks
[14:56] <t1mp> cjwatson: did you do a pull? there were some changes in the last few minutes
[14:56] <om26er> sil2100, ping
[14:56] <cjwatson> t1mp: I just did, yes, on r1011
[14:57] <t1mp> great
[14:57] <om26er> sil2100, there is an autopilot change incoming and we want to run autopilot tests, can you run that in a jenkins job please ?
[14:58] <Saviq> http://q-jenkins:8080/job/autopilot-release-gatekeeper/ ← here
[14:59] <om26er> Saviq, I don't have admin access to that job, trying to find the right person
[14:59] <Saviq> om26er, yup, me neither
[15:03] <sil2100> om26er: hmmmm, good question if I have the permissions, I probably don't...
[15:03] <sil2100> But let me try
[15:05] <bfiller> sil2100: need a silo for line 29
[15:05] <sil2100> Oh
[15:05] <sil2100> om26er, Saviq: it seems I have the permissions, let me look into how this works
[15:05] <sil2100> bfiller: checking in a moment
[15:06] <Saviq> sil2100, thanks
[15:06] <bfiller> sil2100: thanks
[15:07] <sil2100> bfiller: assigned, thanks for filling in the landing o/
[15:09] <sil2100> om26er: so, you want me to run all the tests with this with which silo?
[15:09] <cjwatson> t1mp,zsombi1: that looks fine, debuild -B passed
[15:09] <sil2100> 008?
[15:09] <om26er> sil2100, line 24
[15:09] <zsombi1> cjwatson: thx!!!!!
[15:09] <om26er> sil2100, yeah 008
[15:10] <t1mp> cjwatson: thanks! I'll approve the MR
[15:11] <cjwatson> thanks for looking at this
[15:11] <sil2100> om26er, Saviq: triggered, let's see how it goes
[15:11] <Saviq> sil2100, awesome, thanks
[15:12] <om26er> sil2100, when will you EOD ?
[15:13] <sil2100> om26er: I will be jumping out in like ~30 minutes for practice, but I will be back before 21:00 CEST
[15:13] <om26er> sil2100, Ninja much ?
[15:13] <sil2100> om26er: not ninja, but related ;p
[15:14] <sil2100> om26er: so, if you need anything re-ran, just drop me a PM and I'll do it for sure once back
[15:30] <sil2100> didrocks: ok, just in case I ran gallery-app test suite 2 times on the latest image with no failures once again
[15:30] <didrocks> sil2100: ok, anyway, I'm listing it
[15:30] <sil2100> didrocks: so it seems to be flakyness on the smoketesting infra as before ;/
[15:30] <didrocks> yep
[15:35] <sil2100> didrocks: I'll be jumping out now in ~5 min if anything o/
[15:40] <didrocks> sil2100: enjoy man!
[15:50] <didrocks> Saviq: you are going to deliver bug #1297197 as well?
[15:50] <didrocks> (saw you duplicated the other one)
[15:50] <Saviq> didrocks, define "deliver"?
[15:51] <didrocks> Saviq: like before trusty
[15:51] <didrocks> (I see a MP attached)
[15:51] <didrocks> but needs fixing
[15:51] <Saviq> is probably fixed already
[15:51] <Saviq> didrocks, so yeah, is on the readar
[15:51] <Saviq> radar, even
[15:51] <didrocks> Saviq: oh, like in the silo you propose?
[15:51] <didrocks> Saviq: it's not in #296 for sure
[15:52] <Saviq> didrocks, I mean the MP is fixed
[15:52] <didrocks> ah ok :)
[15:52] <Saviq> didrocks, I have 15 approved MPs already, want to get them through first... at least those you will agree to :P
[15:53] <Saviq> but will definitely look at that one, too, and Albert is looking into more ways to improve it, too
[15:53] <Saviq> truth is... it's mhr3's fault
[15:53] <didrocks> Saviq: I'm not surprised! all mhr3's fault! :)
[15:53] <Saviq> because before we would load the results on startup, so it'd be hidden behind the greeter ;P
[15:53] <didrocks> Saviq: more seriously, I have a lot of chopiness that I didn't get before new scopes, but not only scrolling
[15:53] <Saviq> and now they're only loaded when you unlock
[15:53] <didrocks> Saviq: like when switching between scopes
[15:53] <didrocks> (even once loaded)
[15:53] <Saviq> didrocks, same
[15:54] <Saviq> didrocks, they refresh
[15:54] <didrocks> ah ok
[15:54] <didrocks> so yeah, makes sense
[15:54] <Saviq> didrocks, not every time, but when they know they should, they refresh the results
[15:54] <didrocks> Saviq: ok, that exactly explain the behavior I'm seeins
[15:54] <didrocks> seeing*
[15:54] <Saviq> oh yeah, and that's the other mhr3's fault - all results go away and come in again even though nothing might've changed
[15:54] <didrocks> tssss :p
[15:54] <didrocks> Saviq: this branch will fix it as well?
[15:55] <didrocks> mhr3: what have you done dude!
[15:55] <didrocks> :)
[15:55] <mhr3> i break stuff
[15:55] <mhr3> you're welcome
[15:55] <mhr3> didrocks, your mails would be so boring without me :P
[15:56] <Saviq> didrocks, no, that won't be fixed until mhr3 gets off 'is a$$
[15:56] <didrocks> mhr3: I like boring :p
[15:56] <didrocks> Saviq: should that be 2 bugs then?
[15:56] <didrocks> or is there another one for mhr3?
[15:56] <didrocks> thostr_: do you know? ^
[15:57] <Saviq> didrocks, I don't think that's reported as a bug, it's a feature request from me :P
[15:57] <didrocks> let's use the same bug and adding a scope task
[15:57] <didrocks> as the net result is the same
[15:58] <didrocks> mhr3: which components? ^
[15:58] <Saviq> didrocks, unity-scopes-shell
[15:58] <didrocks> thanks!
[15:59] <mhr3> Saviq, lies! scopes don't refresh all the time
[15:59] <ogra_> oh man
[15:59] <ogra_> dialer-app gets worse with every new image
[15:59] <mhr3> didrocks, pls describe in detail what you're seeing
[15:59] <ogra_> stop these image builds !
[16:00] <didrocks> mhr3: skipping frames when switching between scopes
[16:00] <thostr_> mhr3: so, it was you!!! I had this suspicion all day long...
[16:00] <Saviq> mhr3, I didn't say all the time
[16:00] <Saviq> mhr3, I said that *if* you experience a jerk when switching between scopes, most often that's going to be scope refreshing
[16:01]  * asac starts ho
[16:03] <mhr3> didrocks, on each and every swipe?
[16:07] <ogra_> lol
[16:07] <ogra_> so the updater just updated my dict.cc webapp from 0.4 to 0.3
[16:08] <popey> odd thing with the welcome screen since previous stable (#294) - swipe to unlock, tap ubuntu button..
[16:08] <ogra_> (0.4 was only locally installed though ... but i have like 20 other apps like this)
[16:08] <popey> as soon as you press the ubuntu button the time disappears from the welcome screen just before the welcome screen goes
[16:09] <ogra_> popey, wow, that just a fraction of a second though
[16:09] <ogra_> it seems to print something at the very top of the lock screen
[16:09] <popey> noticable though.
[16:09] <popey> the date
[16:09] <popey> it moves up as the time disappears
[16:09] <ogra_> i wouldnt have noticed without you telling me
[16:09] <popey> hah
[16:09] <popey> bet you would eventually
[16:09] <ogra_> hmm, it felt like it was a longer string
[16:09] <popey> its repeatable
[16:10] <popey> is the welcome screen lightdm?
[16:10] <ogra_> nope
[16:10] <ogra_> not yet
[16:10] <ogra_> there is a landing for that somewhere
[16:10] <ogra_> (split greeter)
[16:11] <popey> so is this unity8? (for bug filing purposes)
[16:11] <ogra_> yes
[16:11] <popey> ta
[16:12] <popey> http://popey.com/~alan/phablet/device-2014-04-15-171154.png
[16:12] <popey> got it! :D
[16:16] <popey> ogra_: feel free to confirm bug 1308139
[16:18] <davmor2> Chipaca: How do I test the push service?  Or is it a case of wait for another image?
[16:19] <Chipaca> davmor2: which image are we talking about?
[16:19] <Chipaca> davmor2: *my* image?
[16:19] <popey> Chipaca: i got a notification that there was a new image after flashing cleanly #297
[16:20] <popey> but the popup appeared and disappeared to quick to see
[16:20] <davmor2> Chipaca: yes I'm on your image what push notifications should I receive
[16:20] <popey> and it had [34] in it
[16:20] <Chipaca> popey: ok
[16:20] <Chipaca> i think we should probably stop sending testing notifications about now
[16:20] <davmor2> popey: confirmed your clock issue
[16:20] <popey> i rebooted hoping to get it again, but i didnt
[16:20] <popey> thanks davmor2
[16:21] <Chipaca> popey: from the terminal (as phablet), stop ubuntu-push-client, move ~/.local/share/ubuntu-push-client/levels.db aside, and start it again
[16:21] <Chipaca> popey: that might get you a popup again :)
[16:21] <popey> ok
[16:22] <popey> Chipaca: http://popey.com/~alan/phablet/device-2014-04-15-172211.png
[16:23] <Chipaca> popey: yep
[16:23] <Chipaca> popey: i'm ... not sure if you think it's a bug or not :)
[16:24] <popey> is [34] some code for "you are awesome"?
[16:24] <popey> because it means nothing to me
[16:24] <popey> ergo, yes, I think that's a bug
[16:24] <Chipaca> we should get rid of the [##]
[16:24] <popey> want a bug?
[16:24] <Chipaca> popey: go on then :) thanks
[16:25] <Chipaca> popey: fwiw it's the message level
[16:25] <Chipaca> or number, or count
[16:25] <Chipaca> but it's called a level in push
[16:33] <ToyKeeper> Chipaca: You pinged earlier?
[16:33] <Chipaca> ToyKeeper: in response to something you were telling me
[16:39] <ToyKeeper> Chipaca: I don't see the silo in the spreadsheet any more; did you get everything landed?
[16:40] <Chipaca> ToyKeeper: yes, worked with om26er on that
[16:40] <Chipaca> ToyKeeper: thank you
[16:40] <ToyKeeper> Okay, good.  :)
[16:40] <Chipaca> ToyKeeper: rhuddie is working on making this level of testing automatable
[16:41] <Chipaca> ToyKeeper: and i'm working on making the tests more comprehensive
[16:52] <Saviq> we need something to run ap suites https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1278659 - running them manually is just a waste of time that we don't have...
[16:58] <asac> Saviq: you mean against landing silos?
[16:59] <asac> (just asking because CI is used by many just for the MP bot)
[17:00] <asac> oh its really about the MP bot
[17:00] <davmor2> meh I forgot about the landing meeting that's what happens when you are doing too much :D
[17:00] <asac> just autopilot-qt havin a special build system
[17:00] <asac> davmor2: we didnt notice :)
[17:01] <asac> davmor2: its all good. i had action to get jfunk find someone from QA to do upgrade testing from stable to current devel
[17:01] <asac> didrocks trie that the upgrade works
[17:01] <asac> in general, but we need more thorough look - meaing: accumulate some user data on the 6 month old image
[17:02] <asac> and see what happens then if you upgrade
[17:03] <davmor2> nice
[17:12] <renato> robru, hi, could you push a new build for silo 14
[17:13] <renato> robru, I have update the MR for syncevolution
[17:13] <robru> renato, sure
[17:13] <robru> renato, so you have new commits on same MPs, no new MPs right?
[17:15] <renato> robru, yes only new commits
[17:18] <jhodapp> robru, can you kick off a rebuild of media-hub in silo 017?
[17:18] <robru> renato, ok, building: https://ci-train.ubuntu.com/job/landing-014-1-build/20/console
[17:18] <robru> jhodapp, one sec
[17:18] <jhodapp> k
[17:18] <renato> robru, thanks
[17:20] <robru> jhodapp, sorry. new commits or new MPs?
[17:20] <robru> renato, you're welcome
[17:20] <jhodapp> robru, new push to an existing MP
[17:21] <robru> jhodapp, ok, just media-hub: https://ci-train.ubuntu.com/job/landing-017-1-build/30/console
[17:21] <jhodapp> robru, thanks!
[17:21] <robru> jhodapp, you're welcome!
[17:23] <robru> bfiller_afk, publishing silo 4
[17:23] <Saviq> asac, no, not about the MP bot, against silos
[17:24] <Saviq> asac, I need to be able to take a silo, tell jenkins to run x, y, z tests on it, and come back to get results
[17:27] <sergiusens> MP testing is orthogonal to silos (predates it)
[17:28] <asac> Saviq: sound fginther is talking about the "CI" job (e.g. the MP review bot)
[17:28] <asac> Saviq: we have silo automation high on our list
[17:28] <ogra_> Saviq, in my ideal worlls there would be an LP buildd producing an image from your silo and then run all AP tests automated against that image
[17:28] <ogra_> *world
[17:28] <asac> right. its also related to image production for silos
[17:29] <ogra_> but thats all pretty time consuming with our current setup
[17:29] <Saviq> ogra_, sure, images could be used, although I feel that a bit heavy
[17:29] <ogra_> well, thats the only way to actually test in the real context
[17:29] <Saviq> yikes
[17:29] <Saviq> asac, I think I pasted a wrong link :D
[17:29] <Saviq> hence the confusion
[17:29] <Saviq> I meant https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1308156
[17:30] <asac> Saviq: that also adds the "parallellization feature" into the mix :)
[17:30] <asac> which is number three
[17:31] <asac> now you could also add emulator :P
[17:31] <asac> but yeah, your need is known; lest review priorities on tuesday
[17:31] <asac> for ev's team
[17:31] <asac> those should clearly be pretty much on top
[17:32] <ogra_> well, emulator and parallelization are kind of the same thing
[17:42] <jhodapp|lunch> robru, sorry but had to make a couple more changes to media-hub, can you queue another rebuild of it please?
[17:43] <robru> jhodapp|lunch, sure thing
[17:43] <jhodapp|lunch> thanks!
[17:43] <robru> ugh, no space left on device...
[17:45] <robru> jhodapp|lunch, you're welcome: https://ci-train.ubuntu.com/job/landing-017-1-build/31/console
[17:47] <fginther> Saviq, regarding https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1308156
[17:47] <fginther> Saviq, is a job that runs all the ap suites in serial of any use?
[17:48] <Saviq> fginther, sure
[17:49] <Saviq> fginther, would be a stop-gap, but still faster than running them manually
[17:49] <Saviq> fginther, and, fwiw, more reliable
[17:49] <fginther> Saviq, what would the image baseline need to be? proposed?
[17:49] <Saviq> fginther, that'd probably be used most often
[17:49] <Saviq> fginther, but since it's flashing every time anyway, would that really matter?
[17:50] <Saviq> fginther, should be possible to flash with any channel / revision even
[17:50] <fginther> Saviq, I guess I meant proposed vs stable, etc.
[17:50] <Saviq> fginther, in terms of system image, not distro, right?
[17:51] <fginther> Saviq, yes, I'm referreing to the system image, my terminology may be off
[17:51] <Saviq> fginther, but yeah, same applies, since the devices are being flashed every time anyway, it should be possible to select which channel / revision to flash
[17:51] <Saviq> fginther, channel = devel-proposed, revision = 283 or whatever's the latest
[17:52] <Saviq> fginther, it would default to the newest revision in devel-proposed, could be useful to allow overriding, but not *really* necessary I'd think, for dev purposes we're all doing against the latest
[17:53] <Saviq> fginther, and for anything that would require investigation, I'd say local runs are good enough
[17:53] <fginther> Saviq, thanks so far... What about specifying the packages from the silo? Would it be acceptable to require a list of binary packages to install?
[17:54] <Saviq> fginther, I think yes
[17:54] <Saviq> fginther, we could then wrap that job with defaults for that per-project
[17:56] <Saviq> fginther, or something to that effect, but yes, I think installing all generated packages would be wrong to do, dist-upgrade could be not enough... or too much, installing from distro...
[17:56] <Saviq> fginther, then there's the ro requirement, phablet-test-click-setup currently only pulls from distro, it would need to understand PPAs, too
[17:57] <fginther> Saviq, yep, all of those can lead to problems, but I need to make sure this isn't going to error prone
[17:58] <Saviq> which brings us to https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1262879 ...
[17:58] <Saviq> which probably needs fixing prior to the above...
[17:58]  * Saviq wonders if we should have autopkgtests ran on device...
[17:58] <Saviq> or something standard to that end
[17:58] <Saviq> anyway
[17:58] <Saviq> /away
[17:58] <fginther> phablet-test-click-setup pulls stuff from distro? I thought it just hit bzr branches
[17:59] <Saviq> fginther, it does pull a unity8 tarball, for example
[17:59] <fginther> and yes, the goal is to move to something autopkgktests like, at least in the sense that the package knows how to test itself
[17:59] <Saviq> fginther, but even if it didn't, stuff that's in silos isn't there in trunks anyway...
[17:59] <fginther> Saviq, ah, unity8
[17:59] <om26er_> Saviq, ok, so trying through test plans for unity8, powerd and autopilot things are working fine, as expected. Only waiting for http://q-jenkins:8080/job/autopilot-release-gatekeeper/110/console to finish
[17:59] <Saviq> om26er_, awesome, thanks
[17:59] <fginther> Saviq, how do you test click packages (or do you)
[17:59] <fginther> ?
[18:00] <Saviq> fginther, phablet-test-click-setup + phablet-test-run
[18:00] <Saviq> fginther, but when I add a unity8 silo, p-t-c-s fails, 'cause it's trying to get a tarball for the installed unity8 version from distro
[18:00] <fginther> Saviq, sorry, I meant if a click package needs to be built, those are being built by silos
[18:00] <fginther> Saviq, I've seen that problem
[18:01] <Saviq> fginther, I'm not sure, but if they are indeed built by silos (I'm not sure they are, at least not for uploading to the store), p-t-c-s would need to know how to deal with that, too, and either branch from the silo (it's currently possible from http://people.canonical.com/~didrocks/citrain/silos/) or grab tarballs from the PPAs
[18:03] <fginther> Saviq, we're trying to solve the same issue with the ci-airline, I was just curious if the ci-train how a known way for dealing with click packages
[18:04] <fginther> Saviq, thanks for the input, I'll update the bug
[18:04] <Saviq> fginther, no worries, and sorry for dumping this like this ;D
[18:05] <Saviq> fginther, when I heard that we should run all app suites manually when trying to release autopilot... my heart stopped...
[18:06] <fginther> Saviq, I understand, it's obviously not the best use of people's time
[18:40] <Saviq> om26er, one failure: http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/label=mako-07/lastCompletedBuild/testReport/
[18:40]  * Saviq runs locally to see if flaky
[18:41] <om26er> Saviq, unity8 tests passed for locally so I don't see why they failed in jenkins
[18:41] <Saviq> om26er, where do you mean?
[18:41] <om26er> Saviq, woops looking at wrong column
[18:42] <Saviq> om26er, the clock test +1 here, must be flaky
[18:42] <om26er> Saviq, alright so we can approve this now :)
[18:42] <Saviq> om26er, yes please :)
[18:43] <om26er> Saviq, done
[18:44] <Saviq> \o/
[18:44] <Saviq> kgunn, silo 008 is +1 from QA ↑
[18:45] <kgunn> woopwoop
[18:45] <kgunn> where's mterry so i can thank him for the speedy work
[18:54] <robru> Saviq, kgunn ... what's that? silo 8 ready to publish?
[18:55] <robru> Saviq, kgunn : published silo 8!
[19:00] <Saviq> robru, thanks!
[19:08] <ogra_> asac, i assume we want an image build witht that ? ^^^
[19:11] <kgunn> ogra_: asac yes that's youre greeter wont unlock fix
[19:17] <bfiller> robru: can you re-upload syncevolution to silo14 with this MR: https://code.launchpad.net/~renatofilho/ubuntu/trusty/syncevolution/fix-1306112/+merge/215881
[19:18] <bfiller> robru: the MR was updated since it was first uploaded
[19:23] <robru> bfiller, sure
[19:23] <robru> bfiller, wait, is it just one MR? or are there two now?
[19:24] <bfiller> robru: should just be the one MR to syncevo
[19:24] <robru> bfiller, ok
[19:25] <robru> bfiller, hmmm, no
[19:25] <robru> bfiller, the original branch I uploaded was https://code.launchpad.net/~renatofilho/syncevolution/fix-photo-merge
[19:25] <robru> bfiller, and the commit there is different than the two at https://code.launchpad.net/~renatofilho/ubuntu/trusty/syncevolution/fix-1306112/+merge/215881
[19:26] <bfiller> robru: the fix-photo-merge MR  got released a while ago I believe. We're testing a new fix now which is the MR I pasted
[19:27] <robru> bfiller, oh ok, I guess I have old stuff lying around then ;-)
[19:28] <bfiller> robru: np, sil had uploaded this to silo 14 this morning, but since then renato has modified it
[19:28] <robru> bfiller, ohh ok ok, from just this morning
[19:28] <bfiller> robru: yeah
[19:30] <cjwatson> Could somebody retrigger CI on https://code.launchpad.net/~cjwatson/mir/arm64-install/+merge/215892, please (if it's not already running)?  I seem to have misplaced my s-jenkins login details
[19:45] <boiko> robru: hi, would you mind assigning a silo to row 34 when possible?
[19:49] <robru> boiko, ok, you got silo 16
[19:49] <boiko> robru: thanks!
[19:49] <robru> boiko, you're welcome!
[19:52] <robru> cihelp ^^ see cjwatson 's message
[19:52] <cjwatson> Oh thanks
[19:52] <fginther> cjwatson, ack
[19:53] <robru> cjwatson, you're welcome!
[19:54] <fginther> cjwatson, it just finished 21 minutes ago and passed. do you still want to rerun it?
[19:54] <cjwatson> Oh right :-)
[19:54] <cjwatson> No, that's fine then, thanks, sorry for the noise
[19:54] <fginther> cjwatson, no worries
[19:56] <davmor2> cyphermox: I just had wifi die on me on desktop what logs would be useful?  I got some stuff in dmesg about a bandwidth change where upon wlan0: disassociated and then deauthenticated.
[20:18] <cyphermox> davmor2: file a bug with ubuntu-bug
[20:23] <rsalveti> ogra_: can we build another image?
[20:23] <rsalveti> ogra_: this lxc-android-config is a nightmare if you run apt-get dist-upgrade
[20:23] <ogra_> rsalveti, yes, waiting for a few packages still
[20:23] <ogra_> rsalveti, well, nothing i can do
[20:24] <rsalveti> for some weird reason even when umounting the udev file I'm still unable to get it stalled
[20:24] <rsalveti> installed
[20:24] <ogra_> right
[20:24] <ogra_> proper only works from recovery
[20:24] <ogra_> if there arent any cross device links in place at all
[20:25] <ogra_> rsalveti, i'll kick a build as soon as unity8 has landed
[20:25] <robru> ogra_, rsalveti it's blocked in -proposed, I just pinged cjwatson about that. gotta run for lunch now but you can follow that up with him if you like
[20:25] <davmor2> cyphermox: apparently LP hates me
[20:26] <ogra_> cyphermox, ignore my last comment on the routing bug ...
[20:27] <davmor2> cyphermox: bug 1308238
[20:54] <imgbot> [20:55] <ogra_> rsalveti, ^^^^
[20:55] <rsalveti> ogra_: thanks!
[20:55] <ogra_> sorry, unity8 took a while
[20:56] <ToyKeeper> Hmm, odd time of day for a new build.
[20:57] <ogra_> heh
[20:57] <ogra_> we are trying to do one build per big landing atm
[20:57] <ToyKeeper> I'm not complaining though...  this means I can get my daily testing done quite a bit earlier.  :)
[20:57] <ogra_> 298 should have the "keyboard over greeter screen" fix
[20:57] <ogra_> right, but we will likely step on our own toes WRT automated tests
[20:58] <ogra_> which means no reference values
[20:58] <ToyKeeper> ogra_: Just yesterday I found that snap decisions can pop up under the keyboard.  Any idea if that might be fixed too?
[20:58] <ogra_> hmm, not sure
[20:58] <ogra_> kgunn, ^^^
[20:58] <ToyKeeper> I wouldn't really expect so, but it seems possible given the nature of the update.
[20:59] <ToyKeeper> I haven't really been doing exploratory testing much, but I keep tripping over new issues by accident.
[21:00] <ogra_> which is great :)
[21:00] <kgunn> ogra_: ToyKeeper don't think so, pretty sure that'd be seperate (snap-d under keyboard)
[21:00] <ogra_> in 14.04 we still have some freedom, nothing is 100% yet ... if you experience the same in 14.10 ... then it will be worrying ;)
[21:03] <kgunn> ToyKeeper: gotta bug # for that one ? (snap-d under osk )
[21:03] <ToyKeeper> kgunn: No, not yet...  just found it late last night, and I'm behind on filing bugs.
[21:03] <ToyKeeper> (hoping to catch up on that today, actually)
[21:04] <kgunn> its a cool one...
[21:04] <kgunn> if bugs can be cool
[21:04] <ToyKeeper> Easy to repro though...  trigger the OSK in landscape mode, then receive a text message.
[21:05] <ToyKeeper> (or call, or whatever)
[21:05] <kgunn> ToyKeeper: yeah...i got no sim
[21:05] <kgunn> :-/
[21:05] <kgunn> wife forced me onto verizon/cdma
[21:05] <ogra_> geez, ask your manager to get ayou a prepaid one
[21:05] <kgunn> yeah..i need to go get one
[21:06] <ToyKeeper> I should send you my SIM...  I can't test 3G with it, but the rest works.
[21:06] <ogra_> though testing calls is probably not your main focus :)
[21:06] <ToyKeeper> Actually, I suppose I should reinstall android to verify if it's a carrier issue or software issue.
[21:35] <Saviq> robru, hey, icanhassilo for line 17 please?
[21:39] <asac> ogra_: we want images for every landing, yes :)
[21:45] <Saviq> cyphermox, could we get a silo please ↑↑?
[21:51] <Saviq> last resort, rsalveti, could we have a silo please ↑↑↑?
[21:55] <cyphermox> unity is already in landing 002
[21:56] <Saviq> cyphermox, that's a temp silo
[21:56] <Saviq> cyphermox, can be ignored
[21:59] <imgbot> [21:59] <imgbot> [22:00] <boiko> robru: landing-016 tested and ready to go
[22:01] <ToyKeeper> ... and flashing.
[22:03] <cyphermox> Saviq: landing 8
[22:03]  * cyphermox goes out to get dinner
[22:03] <Saviq> cyphermox, thanks!
[22:10] <bfiller> robru: silo 1 ready to be published
[22:15] <robru> bfiller, silo 1 published
[22:16] <robru> boiko, silo 16 published
[22:20] <robru> bfiller, silo 7 published
[22:20] <bfiller> robru: nice
[22:21] <bfiller> robru: I may have a few more to publish shortly
[22:21] <robru> bfiller, sure
[22:21] <bfiller> robru: what's the status of releasing packages that are in the desktop, like indicator-datetime and syncevolution?
[22:21] <robru> bfiller, well, trusty release is tomorrow, so basically, only do that if they're critical bugfixes that are trivial to verify
[22:22] <robru> bfiller, or we can "publish" now and -release team will just block them in UNAPPROVED until after U opens.
[22:22] <bfiller> robru: that might be the best
[22:22] <robru> bfiller, but be aware that if they are blocked in proposed, they won't get to the phone either.
[22:23] <robru> or blocked anywhere, proposed or UNAPPROVED
[22:23] <bfiller> robru: yup, that's a bummer but understand
[22:23] <robru> bfiller, it's convergence ;-)
[22:36] <rsalveti> Saviq: it seems you're all set
[23:25] <bfiller> robru: silo 14 ready for release, it's fine that indicator-dateteime and syncevo will be stuck in UNAPPROVED
[23:26] <bfiller> robru: at least sync-monitor will land in image
[23:26] <bfiller> robru: also silo 6 ready for release
[23:26] <robru> bfiller, great
[23:27] <bfiller> robru: going to be afk for a while, send me email if there is a problem
[23:27] <robru> bfiller, published!
[23:27] <bfiller> robru: thank you sir
[23:27] <robru> bfiller, you're welcome!