[00:07] <robru> huh, output.txt says success, not sure what's taking this migration so long
[00:24] <veebers> robru: I understand that I don't need to bother you now that we have the train bot right? (he says while bothering him :-) )
[00:25] <robru> veebers, you got silo 7 ;-)
[00:25] <veebers> robru: awesome, thanks
[00:25] <robru> veebers, you're welcome!
[00:26] <veebers> robru: hmm, going to the landing-007 tab shows a bunch of errors for me. do I need to refresh perhaps?
[00:26] <robru> veebers, nah, the spreadsheet is just slow. it'll still work if you click build though
[00:26] <veebers> robru: sweet, will try that :-)
[00:27] <robru> veebers, http://people.canonical.com/~rbpark/citrain/ updates faster and is more accurate about silo statuses
[00:27] <robru> errrrrr mahhhhh geerrrrrrd platform-api finally landed for real! holy crap congrats ricmm!
[00:27] <veebers> ah cool cheers
[02:21] <rsalveti> robru: awesome
[07:39] <Saviq> davmor2, so what do you think of silo 20? of the two issues found one is fixed (time sync in greeter), the other is an old bug (bug #1325696)
[07:46] <sil2100> ogra_: morning! Packaging ACK required: https://ci-train.ubuntu.com/job/landing-012-2-publish/40/artifact/packaging_changes_mediascanner2_0.101+14.10.20140613-0ubuntu1.diff <- love this one, it has a nice changelog mention of the dep-change and a really well made symbols file o/
[08:03] <ogra_> sil2100, beautiful ! ACK
[08:16] <Laney> sil2100: why are you asking for acks for universe stuff?
[08:16] <ogra_> right ! you are a MOTU now !
[08:16] <ogra_> dang ... i totally forgot
[08:17] <sil2100> Oh
[08:17] <Laney> p0w3r
[08:17] <sil2100> Laney: well... theoretically I shouldn't, but Didier said that we had to ask 'core-devs' before publishing - so I thought the rule was 'core-devs-only' :) But if I can use my newly gained POWER than YEAH
[08:17] <Laney> I think you have to ask someone who can upload the package
[08:18] <Laney> core-dev is probably a shorthand for that
[08:18]  * sil2100 stands on top of a mountain in an epic pose then
[08:18] <ogra_> yeah,, since you could actually just upload the package you can as well judge the quality yourself
[08:19] <sil2100> Right, I was even talking about this with Robert in Malta, but in the end we didn't know what the rules for citrain-uploads are
[08:19] <sil2100> And it seems it just sticked with me
[08:19] <ogra_> the same as for the archive
[08:20] <sil2100> Oh, greeter revert ready for release
[08:20] <ogra_> lets go then :)
[08:20] <sil2100> We have an image promoted so I'll just do this one :)
[08:20] <seb128> you guys like reverts
[08:20] <ogra_> PAPI v2 didnt show any regressions in the tests
[08:21] <ogra_> ricmm deserves a medal for that one ... i think it is the first landing of such a size that just went through this cycle
[08:21] <seb128> ogra_, what about split greeter? ;-)
[08:21] <ogra_> seb128, lol
[08:21] <ogra_> right, we had *nearly* no work with that one
[08:23] <ogra_> woah ...
[08:23] <ogra_> 8 out of the 10 crashes the flo smoketest has today are indicator-network crashes
[08:23] <ogra_> randomly throughout the tests
[08:24] <sil2100> Saviq: I know you're not the lander of the split greeter, but since you're the only related one around a quick info:
[08:24] <Laney> oh COME ON
[08:24] <Laney> new u-s-s failures
[08:24] <sil2100> Saviq: I will have to rebuild unity8 I guess ;/
[08:24] <ogra_> Laney, well, the TZ one is gone
[08:24] <sil2100> Saviq: the changelog is b0rken
[08:24] <ogra_> think positive
[08:24] <Saviq> sil2100, yeah I saw it was weird
[08:24] <Laney> i want green
[08:24] <ogra_> and you got two for one ... who wouldnt want that !
[08:25] <sil2100> Saviq: CI train got confused
[08:25] <seb128> Laney, :-(
[08:25] <Laney> VOTE GREEN
[08:25] <Saviq> sil2100, will it require testing again?
[08:25] <ogra_> ++
[08:25] <seb128> Laney, which one this time?
[08:25] <sil2100> Saviq: I guess no need for a retest, since I will only change the commit message
[08:25] <Laney> updates
[08:25] <ogra_> seb128, update ones
[08:25] <Laney> http://ci.ubuntu.com/smokeng/utopic/touch/mako/80:20140613:20140530/8547/ubuntu_system_settings/
[08:25] <Saviq> sil2100, ok cool
[08:25] <seb128> shrug
[08:25] <seb128> nothing changed on updates!
[08:26] <ogra_> seb128, we got a new platform api
[08:26] <ogra_> probably some slight fallout ?
[08:26] <seb128> ogra_, let's revert!
[08:26] <ogra_> lol
[08:26] <seb128> ypou people love reverts
[08:26] <seb128> ;-)
[08:26]  * ogra_ refers to management :P
[08:26] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/80.changes
[08:27] <seb128> btw did anyone figure out the ring only once issue?
[08:27] <ogra_> not yet i think
[08:28]  * ogra_ isnt sure how "repeat" is handed to the backend but i can imagine there is just something like a newline char coming out of the gsettings change or some such so that option is dropped or something 
[08:28] <ogra_> <- wildly speculating
[08:30] <ogra_> whee, weird harp sounds out of my phone !
[08:30] <ogra_> and you cant stop it !!!
[08:30] <seb128> is that the new alarm sound?
[08:30] <ogra_> yeah
[08:31] <ogra_> and even if you hit the stop button it plays to the end
[08:31] <ogra_> that sound is like 5 min long (felt)
[08:31] <seb128> well at least it's harp being played!
[08:31] <seb128> not drums
[08:31] <ogra_> lol
[08:56] <sil2100> Mirv: an *NO*, no Qt 5.3 landing this week mister!
[08:56] <sil2100> ;)
[09:01] <mhr3> uh oh
[09:01] <mhr3> i really need a silo for 41
[09:02] <mhr3> sil2100, pls
[09:02] <Mirv> sil2100: yeah, not this week, it's on Monday like you remember! ;)
[09:03] <Mirv> mhr3: doing
[09:04] <Mirv> landing-015
[09:05] <davmor2> sil2100: Monday then for Qt5.3 so it fixes the world then right?
[09:13] <sil2100> Right!
[09:13] <sil2100> ;p
[09:21] <sil2100> Split greeter revert published o/
[09:21] <sil2100> Uh
[09:21] <sil2100> Or maybe not
[09:21] <sil2100> eh... the silo wasn't rebuilt after papi v2 it seems ;/
[09:22] <ogra_> ouch
[09:22]  * sil2100 rebuilds ubuntu-touch-session
[09:22] <mhr3> Mirv, eeeh, sorry, false alarm, giving up 015
[09:22] <sil2100> Saviq: once it rebuilds, could you take a quick look on if nothing is b0rken?
[09:22] <sil2100> Saviq: in silo 20
[09:30] <Saviq> sil2100, I think is already built
[09:30] <Saviq> sil2100, will check in a few
[09:46] <sil2100> Saviq: thanks o/
[09:47] <sil2100> Saviq: well, ubuntu-touch-session is still said to be building
[10:02] <Saviq> sil2100, +1 on silo 020
[10:09] <sil2100> Saviq: \o/
[10:09] <sil2100> Published, yay
[10:58] <popey> davmor2: on #80 my OSK is confused. It gets upper and lower case round the wrong way. It auto switches caps off at the start of a sentence, and then on for every subsequent letter. So I get "hELLO".
[10:58] <popey> and if I flip it off then type a letter, it flips back on again
[10:59] <davmor2> popey: I've seen that trying to add accounts for twitter and facebook but no where else.  What app are you testing on?
[11:00] <popey> in browser, lastpass webapp
[11:01] <davmor2> popey: so that might be the same issue then it just always triggers caps I've not seen it recently so didn't bug it let me see if it happens for me too then
[11:01] <ogra_> popey, hmm, OSK was updated before 80 ... and there was a change related to capitalization i think
[11:02] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/79.changes ... 79 had the new OSK
[11:02] <davmor2> ogra_: I think it might get triggered by certain text fields maybe
[11:02] <popey> it bugged me when i was out and about earlier and wanted to login to twitter
[11:02] <davmor2> popey: yeah that is where I have seen it before
[11:04] <ogra_> ah, right, and the capitalization changes were actually the upload before
[11:04] <alan_g> cihelp this morning I've seen a couple of failures like this: https://jenkins.qa.ubuntu.com/job/mir-android-utopic-i386-build/537/consoleText can you help?
[11:04] <ogra_> bug 1312329
[11:04] <popey> ARGH
[11:04] <alan_g> "tar: Error is not recoverable: exiting now"
[11:05] <popey> GPU lockups on my laptop are doing my head in
[11:05] <popey> Getting dangerously close to wiping and re-installing entire laptop
[11:06] <sil2100> The OSK problem might be related to my change
[11:07] <sil2100> Oh, or Elleo's
[11:08]  * davmor2 instantly blames sil2100  from now on for all keyboard issues ;)
[11:08] <fginther> alan_g, looking
[11:16] <fginther> alan_g, found the issue and am fixing
[11:17] <alan_g> fginther: thanks - let me know when I can restart failed jobs
[11:18] <fginther> alan_g, you can start now. I took the bad node offline while it's being fixed
[11:19] <alan_g> fginther: nice
[11:44] <Saviq> sil2100, is "sil/20140604: locked by 007" still valid for line 17?
[11:45] <sil2100> Saviq: not anymore :)
[11:45] <sil2100> At least not by 007
[12:06] <ogra_> sil2100, how about an image build ?
[12:06] <ogra_> greeter revert migrated
[12:07] <sil2100> ogra_: nice - let's do one :)
[12:07] <sil2100> At least we'll know instantly if something is wrong
[12:08] <ogra_> triggered ...
[12:12] <sil2100> ogra_: thanks
[12:12] <ogra_> bah, where is the bot
[12:13] <charles> ogra_: I'll take a look at stopping the new alarm sound as soon the snap is dismissed :-)
[12:13] <ogra_> charles, having some shorter sound (or something configurable) would also be cool
[12:13] <charles> ogra_, the plan is for there to be a configurable sound via the alarm app
[12:14] <charles> my guess is that'll come in the redesign that nik90 is implementing for RTM, but that's only my guess
[12:14] <ogra_> well, i think it should be a system setting ... given that all alarms i get here are from calendar
[12:15] <ogra_> or both share the same backend or some such ...
[12:15] <ogra_> +need to
[12:15] <nik90> ogra_: the new designs provided have a setting to change the alarm sound in the clock app
[12:15] <ogra_> nik90, right, but that doesnt help me with the calendar
[12:15] <nik90> ogra_: we will have a dedicated alarm ringtone folder
[12:15] <nik90> ogra_: why not?
[12:16] <nik90> ogra_: calendar app can add an event sound option which uses that same folder
[12:16] <ogra_> does the calendar app use the alarm pages from the clock ?
[12:16] <nik90> ogra_: atm it doesn't, but they can if they want to.
[12:16] <ogra_> i think that would make sense
[12:16] <charles> we should coordinate with them on that
[12:16] <ogra_> else we'll duplicate a lot of code
[12:17] <nik90> charles,ogra_: I will coordinate with the calendar app devs about this. But first charles we need the indicator-datetime to support different alarm sounds
[12:17] <charles> I would hope that calendar-app is going through qt5organizer-eds, but I haven't read the code
[12:17] <nik90> charles: the last time I checked it was hardcoded
[12:17] <charles> nik90, agreed, that's some thing I need to fix. It's still hardcoded
[12:18] <nik90> charles: well the calendar app uses qt5organizer-eds to set the event details. So I am sure they can set the event sound there. But the UI code is something they can borrow from clock after it has landed.
[12:20]  * ogra_ thinks we should have a system wide default that you can set from the settings and that is the default in both apps ... and then on a per app and per notification basis a way to override that 
[12:20] <charles> nik90, so when the clock app saves an alarm with a custom sound, will it be stored in EDS as a E_CAL_COMPONENT_ALARM_AUDIO?
[12:20] <charles> nik90, I can start coding to that RSN s.t. the hardcoded file is only used as a fallback
[12:21] <charles> let's see... working backwards, the qtorganizer term that translates into that EDS term is QOrganizerItemReminder::TypeAudibleReminder
[12:21] <nik90> charles: I am guessing the SDK Alarms API translates the stored alarm sound in EDS as a E_CAL_COMPONENT_ALARM_AUDIO. You will have to confirm with zsombi about that.
[12:21]  * charles looks at ubuntu-ui-toolkit
[12:22] <nik90> charles: however you are right about using the hardcoded file as a fallback
[12:23] <charles> confirmed, I think. AlarmsAdapter::organizerEventFromAlarmData()  is using QOrganizerItemAudibleReminders
[12:24] <charles> nik90, ogra_, added to my TODO: (a) supporting custom sounds and (b) stopping playback as soon as the snap is dismissed
[12:24] <zsombi> nik90: charles: it's not SDK Alarms doing that, it's EDS backend
[12:24] <nik90> charles: awesome. Let me know once (a) lands. I can then start looking to land the support in the clock app side
[12:24] <ogra_> charles, cool
[12:25] <charles> zsombi, I think we're saying the same thing though, right? ubuntu-ui-toolkit is using qtorganizer's QOrganizerItemAudibleReminders, agreed you don't care what happens below that, but renato's code is converting it into E_CAL_COMPONENT_ALARM_AUDIO
[12:28] <nik90> ogra_: I will try to bring this to the designer's attention..(system wide default that you can set from the settings and that is the default in both apps ... and then on a per app and per notification basis a way to override that)
[12:28] <zsombi> charles: yes :) sorry, I'm in a meeting and saw teh text popping up :)
[12:28] <ogra_> nik90, thanks a lot !
[12:28] <charles> zsombi, ok :)
[12:38] <renato> fginther, I think jenkis is blocked again: http://s-jenkins.ubuntu-ci:8080/job/phablet-team-address-book-app-staging-ci/
[13:10] <Saviq> sil2100, can you reconfigure silo 008 for us please?
[13:10] <sil2100> Saviq: sure
[13:11] <sil2100> Saviq: should be reconfigured now
[13:12] <bregma> you're enhancing my desktop session landing now?
[13:13] <Saviq> bregma, yes, added the unity8 branch
[13:13] <Saviq> bregma, and just kicked a rebuild (because unity8-desktop-session from silo 007 landed)
[13:14] <bregma> Saviq, what does that branch do, and does it require non-desktop testing before it can land?
[13:14] <Saviq> bregma, that branch just enables the logout button from the session indicator
[13:14] <Saviq> actually making it exit
[13:15] <bregma> Saviq, will that not also require changes to session-indicator?
[13:15] <Saviq> bregma, indeed, missed that one
[13:15] <Saviq> sil2100, sorry, can you recon again, forgot to add a indicator-session branch
[13:16] <sil2100> Ok :)
[13:16] <bregma> the party never stops
[13:16]  * bregma dances off into the crowd
[13:34] <imgbot> [13:35] <imgbot> [13:35] <ogra_> ChickenCutlass, ^^^
[13:35] <davmor2> ogra_: was this silo 020
[13:35] <ogra_> the greeter revert ...
[13:36] <davmor2> ogra_: yes
[13:36] <ogra_> right
[13:36] <sil2100> I curious how it will look test-wise
[13:36] <davmor2> this should just work too then :D
[13:36] <sil2100> Ah, darn it, forgot about the smoketesting modification
[13:36] <ogra_> :)
[13:36]  * sil2100 prepares a merge
[13:42] <mterry> fginther, hello!  So my split-revert packages landed, and if you remember, they were experiencing some odd autopilot/qmluitest failures in jenkins CI.  Now that they are merged in, are we seeing any oddities on the autopilot test suites?
[13:46] <ChickenCutlass> ogra_: nice ok
[13:48] <sil2100> psivaa-afk: https://code.launchpad.net/~sil2100/ubuntu-test-cases/touch-readd-dispatcher/+merge/223073 <- could you take a look?
[13:53] <ogra_> sil2100, wasnt that a dependency of unity8-autopilot anyway  ?
[13:54] <sil2100> ogra_: yes, but we're not installing unity8-autopilot - I mean not at least as part of the test-case
[13:54] <sil2100> Maybe it's installed for something else, like unlocking the screen?
[13:54] <ogra_> no, we install it before running any tests
[13:54] <ogra_> since it ships the unlock script
[13:54] <ogra_> right
[13:54] <sil2100> Ok then, so we're safe
[13:54] <sil2100> I'll leave this merge just in case, but in this case we're cool
[13:55] <ogra_> we'll see, the smoketests for 81 are already running
[14:09] <sil2100> elopio, brendand: hi guys! Any luck with filemanager by any chance?
[14:10] <brendand> sil2100, well we found that the test fixes aren't in yet
[14:10] <sil2100> Which test fixes?
[14:10] <brendand> sil2100, filemanager is still not approved to the store for the latest version
[14:10] <brendand> sil2100, that elopio did earlier this week
[14:10] <brendand> sil2100, they may not fix all the issues but we should certainly make sure it's updated and re-evaluate after that
[14:11] <sil2100> Ah
[14:11] <sil2100> Ok, good to know! It's rather confusing with click packages indeed
[14:11] <sil2100> popey: do you know anything about that ^ ?
[14:11] <brendand> sil2100, i noticed a possible issue but i want to try again when everything is perfectly up to date
[14:12] <sil2100> brendand: excellent news in overall, thanks!
[14:12] <brendand> sil2100, well we aren't out of the woods yet, but let's see what happens
[14:13] <popey> sil2100: "that" specifically?
[14:14] <sil2100> popey: brendand mentioned that a new filemanager is not yet approved in the store
[14:14] <popey> ok, i can triggeryes
[14:14] <popey> bah
[14:14] <sil2100> So I guess it's pending a review?
[14:14] <popey> yes
[14:14] <popey> no
[14:14] <popey> it's not been submitted to the store. elopio said earlier not to as he has another merge pending
[14:14] <popey> well, that his don't fix it
[14:14] <popey> 15:01:56 < elopio> brendand, popey: but, my clean ups don't fix the problems. What we seem to be having are random freezes.
[14:15] <popey> so no point pushing to store if it aint fixed
[14:20] <elopio> popey: well, we might get a little prettier traces of the errors.
[14:20] <sil2100> Ah
[14:20] <elopio> I need to sync with balloons to see if he found something or at least has better ideas of where to look for.
[14:20] <popey> happy to push to the store
[14:20] <popey> but need you guys to give me the nod when you have something you want pushing
[14:20] <brendand> elopio, just now the tests and the app are out of sync
[14:21] <brendand> elopio, so i need to roll back to an old version of the tests then
[14:21] <elopio> brendand: or use phablet-test-run
[14:21] <popey> https://code.launchpad.net/~ubuntu-filemanager-dev/ubuntu-filemanager-app/trunk
[14:21] <popey> store has r193, latest is r203
[14:21] <brendand> elopio, phablet-test-run is broken because of a bad unity8 version
[14:23] <brendand> elopio, which appears to have been transient
[14:23] <brendand> elopio, working now
[14:23] <brendand> elopio, i still think we should push it if it's test changes. it's not as if we're going to roll them back
[14:25] <elopio> brendand: yes, I agree to that.
[14:25] <elopio> brendand: can you look at my pending branch, so we land it too?
[14:25] <brendand> elopio, ok
[14:44] <sil2100> mandel: so, I'm looking at your branch now and I see you're not using a symbol map there
[14:44] <sil2100> mandel: it might be a bit more troublesome maintaining the symbols this way
[14:45] <mandel> sil2100, what do you mean? the addition of each of the archs pointing to two files, the 32 and the 64?
[14:45] <cyphermox> sil2100: you can free silo 13
[14:46] <cyphermox> like, free / nuke, etc.
[14:46] <sil2100> mandel: not sure if that will be required, I mean something different - without an ld-version script (also called an symbol export map) you're also maintaining STL and Qt symbols in your symbols file
[14:46] <sil2100> cyphermox: ok
[14:46] <sil2100> cyphermox: something wrong with that one?
[14:47] <cyphermox> not really, but I already uploaded the proper version to it before
[14:47] <mandel> sil2100, oh, I did see some of the qt ones being present, what do you recommend?
[14:47] <ogra_> sil2100, unity8 passed fine ....
[14:47] <cyphermox> it's tested and ready to land, but I'll upload directly with the correct version number to the archive
[14:47] <ogra_> so i guess we dont need your change
[14:47] <ogra_> dialer seems ot have a new error :(
[14:47] <sil2100> mandel: so, some projects already use this, let me write a comment on the merge with an example one :)
[14:48] <mandel> sil2100, great, thx
[14:48] <sil2100> mandel: it's easy and makes the libraries even better, as we're not leaking everything as it goes (which is the default in C++)
[14:48] <mandel> sil2100, is the first time I have to deal with this rather than update one
[14:48] <sil2100> ogra_: ok, geh
[14:49] <sil2100> ogra_: well, it doesn't look so bad, I saw this failing in the past - not sure if it was really fixed or just went away
[14:49] <ogra_> yeah
[14:50] <ogra_> 81 looks okayish up to now
[14:50] <ogra_> but it is only half doen yet
[14:56] <sil2100> cyphermox: ok, so I'm also removing the landing line as well
[14:57] <cyphermox> thanks
[14:57] <cyphermox> going to do a new one for urfkill most likely
[15:01] <elopio> brendand, balloons, sil2100, popey: ok! for the first time I've seen the filemanager going crazy. It just stays on the new opening animation for a long long time.
[15:02] <balloons> elopio, so it failed to start?
[15:02] <elopio> balloons: yes. I think it's the new version of white screen.
[15:03] <balloons> elopio, well.. old version you mean.. that was an issue in the past. a couple different times actually
[15:03] <balloons> there's old bugs ons
[15:05] <nik90> charles: hey, I noticed that when an alarm rings, the phone does not turn on and show the welcome screen. Instead I need to do that manually. Do you know what we might need to add that support similar when receiving calls?
[15:07] <brendand> elopio, me too
[15:07] <brendand> elopio, at least once for run
[15:07] <brendand> elopio, that's the issue - just hard to reproduce
[15:07] <brendand> elopio, strange that the test continues to run while the animation is ongoing
[15:07] <sil2100> uh
[15:08] <elopio> brendand: the thing is that we don't have a way to wait for the main view.
[15:08] <elopio> currently some tests do self.main_view.visible.wait_for(True) on the setUp
[15:08] <elopio> but that doesn't work, because visible is always True, even while the animation is going.
[15:08] <charles> nik90,  yeah it's an issue with powerd not watching for the wakeup. There's nothing to be done on our side of the stack, no API even for us to call for that
[15:09] <elopio> so as far as autopilot can find the components, it will start the test even if they are not really visible on the UI.
[15:09] <elopio> then the test fails after the first click, because if of course does nothing.
[15:09] <nik90> charles: do you know who the developer of powerd is?
[15:09] <brendand> elopio, that's got to be a bug in the application then
[15:09] <charles> nik90, rsalveti said his team would handle it, though I don't think it's been delegated to a specific dev yet
[15:10] <ricmm> its not scoped yet but our team will do it
[15:10] <ricmm> probably mandel
[15:10] <elopio> brendand: well, in my opinion is a bug in Qt because you can't rely on visible. It says True but it's not actually visible.
[15:11] <balloons> elopio, do we know why visible lies anyway? we depend on it, but it's not always set properly
[15:11] <elopio> but they have documented somewhere that you shouldn't rely on visible.
[15:11] <elopio> so, we need an alternate way to do it.
[15:11] <brendand> elopio, the real issue though is that it's failing to start up properly
[15:11] <elopio> like a month ago or so I was talking about it with kalikiana and he had some ideas of how to wait for things to be actually painted, but we never did anything about it.
[15:11] <nik90> charles: thnx
[15:12] <brendand> elopio, the test is failing correctly. maybe with a not clear reason, but it should fail in that situation
[15:12] <elopio> brendand: well, yes, that's the issue. The app is broken and it sometimes doesn't start.
[15:12] <elopio> secondary issue is that on autopilot we have no way   to know when the app started.
[15:12] <charles> mandel, congrats on being volunteered ;)
[15:12] <elopio> so failures look like random problems on the test, when they are actually apps broken.
[15:13] <mandel> charles, he, I noticed that.. will do asap, dealing with location-service and udm atm, as soon as I have some time I'll move to powerd, hopefully in 1/2 weeks
[15:14] <balloons> elopio, I would also saw we don't always know when an app crashes either in autopilot.. those too aren't clear in the log
[15:14] <balloons> *say
[15:16] <elopio> balloons: that's because it didn't crash. It just was slow to load.
[15:16] <renato> fginther, do you still around, jenkins is getting stuck again : http://s-jenkins.ubuntu-ci:8080/job/phablet-team-address-book-app-staging-ci/
[15:16] <elopio> or maybe even if we waited 5 minutes, it would never load.
[15:16] <balloons> elopio, right.. but I'm not sure we do well when apps do crash.. or whitescreen :-)
[15:16] <elopio> who should be checking that? ubuntu-app-launch ?
[15:16] <elopio> balloons: I think that autopilot collects every crash it finds.
[15:16] <elopio> if it's not on the artifacts, it's because the file was never created.
[15:17] <elopio> or maybe I'm trusting autopilot too much :)
[15:17] <balloons> elopio, well I use crash loosely.. if something doesn't appear / draw, or it whitescreens (i still don't know what to call that), or something eats all the cpu, etc.. we don't have a great way to tell via the log
[15:18] <balloons> basically if the app itself fails, which is the case in many of these, we can't easily tell that is the case
[15:18] <balloons> and sadly I feel we assume too often the test is at fault
[15:19] <elopio> balloons: yes, you are right.
[15:19] <elopio> one thing that will help is the screenshot. I asked veebers to raise the priority to that.
[15:19] <elopio> other thing are the measurements thomi is working on.
[15:19] <psivaa> sil2100: sorry was away for some time, i see you've taken care of url-dispatcher-tool MP yourself :)
[15:19] <elopio> we are still left with never knowing when something is painted on the screen.
[15:19] <sil2100> psivaa: hey! Yeah, it seems to have been unneeded ;)
[15:20] <popey> fginther: weather app is failing to build in s-jenkins - getting odd infrastructure errors in console log
[15:20] <psivaa> sil2100: ack :)
[15:20] <brendand> elopio, do we have any info on what makes the startup animation end?
[15:20] <brendand> elopio, is the app giving it some signal?
[15:20] <ogra_> davmor2, popey, is any of you dogfooding 81 already ?
[15:21] <elopio> brendand: I don't know.
[15:21] <davmor2> ogra_: I am
[15:21] <ogra_> cool
[15:21] <elopio> it should. Whoever wrote this new animation should be able to help us here.
[15:21] <elopio> Saviq: do you know about that ^ ?
[15:22] <Saviq> elopio, it's just a timeout
[15:22] <Saviq> brendand, ↑
[15:22] <sil2100> davmor2: hi! Are you busyish? :)
[15:22] <Saviq> brendand, elopio, but that's temporary, we'll soon know when app's drawn its first frame and hide then
[15:23] <sil2100> davmor2: could you take a quick look if 81 is not badly broken?
[15:23] <davmor2> sil2100: see above
[15:23] <elopio> Saviq: how do you know when an app draw it's first frame?
[15:23] <sil2100> hah!
[15:23] <sil2100> It seems ogra_ poked first ;)
[15:23] <brendand> Saviq, in this case we see the animation running for well at least 30 seconds
[15:23] <ogra_> sil2100, heh :)
[15:23] <brendand> Saviq, does that sound right?
[15:24] <Saviq> elopio, right now we don't, but we will once unity8 does the compositing
[15:25] <elopio> ok, sounds promising.
[15:25] <brendand> Saviq, and does the animation go away when an application eventually draws itself?
[15:25] <brendand> (right now)
[15:25] <popey> sil2100: do you have a fix for the keyboard capitalisation issue?
[15:26] <Saviq> brendand, it should
[15:26] <davmor2> popey: I don't see it now at all so I'm wondering if it is a race somewhere
[15:26] <Saviq> brendand, if you can see it running long after the app started, is a bug, please file one and we'll investigate
[15:26] <brendand> Saviq, so if the animation remains for as long as 30 seconds we can say the application is for some reason not able to draw itself
[15:27] <sil2100> popey: no, didn't have time to look into that - I guess my and Elleo's changes combined could have caused something strange
[15:27] <Saviq> brendand, it didn't start, yes
[15:27] <Saviq> brendand, I mean if you can *see* the dots
[15:27] <Saviq> brendand, then the app failed
[15:27] <brendand> Saviq, yes we see the dots
[15:27] <Saviq> brendand, 'cause the app is painted on top
[15:27] <brendand> Saviq, i will file one against the app itself
[15:28] <sil2100> seb128: so, you want to land line 32 first?
[15:28] <seb128> sil2100, yes please, it's a trivial fix for the desktop-next iso
[15:29] <seb128> sil2100, I'm going to land that now, then reconfigure silo 008
[15:29] <sil2100> Ok, assigning then :)
[15:29] <seb128> sil2100, thanks
[15:33] <elopio> sil2100: where can I see the commit log for 79 - 81 ?
[15:34] <balloons> elopio, is this helpful? http://people.canonical.com/~ogra/touch-image-stats/
[15:35] <elopio> balloons: yes it is. Thanks.
[15:35] <sil2100> seb128: hmm, spreadhseet takes ages to update
[15:35] <Laney> http://ci.ubuntu.com/smokeng/utopic/touch/mako/81:20140613.1:20140530/8558/ubuntu_system_settings/
[15:35] <Laney> YEAH!
[15:35] <ogra_> broken !
[15:37] <sil2100> Laney: LIES!
[15:37] <sil2100> I want those testst to be re-run!
[15:37] <sil2100> ;)
[15:40] <brendand> sil2100, so here is the primary issue with filemanager: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1329818
[15:41] <brendand> sil2100, let's put whatever tags we need / importance to make sure it gets serious attention
[15:41] <davmor2> ogra_, sil2100: so 81 is pretty good to be fair
[15:41] <fginther> popey, looking
[15:41] <ogra_> promotable good ?
[15:41] <brendand> sil2100, no doubt it's a tricky one
[15:41] <ogra_> or just so so good
[15:42] <popey> fginther: thanks
[15:43] <davmor2> ogra_: no different to 79 or 80 only with indicators working both sides of the greeter :)
[15:43] <sil2100> brendand: now this bug makes sense to me, at least we know that the 'white screen' problem is the cause now
[15:43] <ogra_> \o/
[15:43] <sil2100> brendand: thanks! Let me update the list on the e-mail
[15:43] <sil2100> davmor2: great news ;)
[15:43] <ogra_> davmor2, did you put some extra care into dialer ? looks like we have a new test failure there
[15:43] <sil2100> What a happy Friday 13th!
[15:44] <ogra_> we're down to 4 crashers !!!
[15:44] <sil2100> So many good news and good swift landings
[15:44] <sil2100> Ok, now this is a *really* good Friday 13th
[15:45] <davmor2> ogra_: works here what is failing?
[15:45] <ogra_> (of which two are indicator-network, one is system-settings and the other media-hub ... thats really great)
[15:45] <ogra_> davmor2, test_call_log_item_opens_messaging
[15:45] <ogra_> try send an SMS from the call log
[15:45] <davmor2> ogra_: yeap that works just takes it's time
[15:46] <Laney> no!
[15:46] <Laney> one is system-image-dbus
[15:46] <ogra_> ah, timing issue with the test perhaps
[15:46] <ogra_> Laney, nah ... all your fault :P
[15:47] <davmor2> ogra_: so felt like 4-5 seconds for it to open, but if the test is set to continue the window opens pretty much instantly it's just black, so if it looks for something or tries to interact with something it will fail
[15:48] <fginther> popey, fixed the problem with the broken workspace and it's building now
[15:48] <ogra_> davmor2, yeah
[15:48] <popey> fginther: thanks
[15:48] <ogra_> davmor2, as long as it works in real life i dont really care :)
[15:49] <davmor2> ogra_: yeah works in real life
[15:49] <ogra_> awesome
[15:50] <ogra_> sounds liek a good weekend candidate for promotion :)
[15:50] <sil2100> davmor2: could you check-out #81 from promotion side of things? :)
[15:50] <sil2100> We're still blocking promotion on filemanager, but..!
[15:50] <davmor2> sil2100: No :P
[15:51]  * ogra_ gets meeting coffee
[15:51] <sil2100> If the filemanager issue gets triaged properly and people assigned for fixing it, I guess we could consider taking the blocker off
[15:51]  * sil2100 has some nifty tools in the works which he wants to finish off to make managing this easier
[16:11] <popey> balloons: please upload http://popey.com/~alan/com.ubuntu.weather_1.1.272_all.click to store, it passes tests
[16:17] <davmor2> ogra_, popey: on 81 hit the apps header and switch it to something else
[16:18] <davmor2> nevermind it's the old if you drag down it breaks it
[16:23] <balloons> popey, done
[16:23] <popey> thanks balloons
[16:28] <popey> published
[16:33] <davmor2> sil2100: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1329834
[16:36]  * popey starts running filemanager tests with current filemanager in #81 to compare against
[16:36] <sil2100> popey, davmor2: if it's not a regression then I won't even include it in the e-mail I guess ;)
[16:36] <popey> +1
[16:36] <sil2100> popey: thanks!
[16:37] <davmor2> +1
[16:37]  * popey lights the bbq
[16:38] <davmor2> popey: that's a sure fire way to reduce the length of you hair :D
[16:38] <popey> ☻
[16:38] <popey> I'm going to light it with a match, not my hair
[16:38] <popey> (to be clear)
[16:38] <ogra_> you light the BQ ?
[16:39] <sil2100> Don't! We want those phones...
[16:39] <popey> elopio: got filemanager stuck on loading screen
[16:39] <elopio> popey: yay!!!
[16:39] <davmor2> popey: that didn't take long :)
[16:39] <elopio> popey: please mention here that it's reproducible by a user: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1329818
[16:40] <popey> well. reproducible by autopilot ㋛
[16:40] <elopio> oh, so you were running autopilot, not doing it with your fingers?
[16:40] <elopio> :(
[16:41] <popey> yes
[16:41] <popey> left comment and my log
[16:42] <popey> worth looking at the test that ran before the failed one, and see what it does, then reproduce that manually?
[16:42] <elopio> agh, so we still haven't ruled out autopilot from the possible causes.
[16:43] <popey> elopio: interestingly i see AP try and tap things and fail
[16:43] <popey> it didnt detect that the app had started
[16:43] <popey> *hadn't
[16:43] <elopio> popey: yes, that was one of my points related to this error.
[16:43] <elopio> from autopilot, we have no way to tell if the app is painted.
[16:44] <elopio> as soon as the qml tree is ready, it will start running the test.
[16:44] <elopio> until it tries to click something, which will fail because that something is not receiving the input.
[16:46] <elopio> I'm not sure if running the test before that one that you saw failing will give useful information. But if you have the time, we don't lose anything by trying.
[16:49] <popey> is there any way to insert a short 1-2s delay after the qml tree is ready, before the test starts?
[16:50] <popey> like launch.. wait for tree, wait for 1s, start test
[16:50] <sil2100> elopio: ah, and sorry if I miss out something in my landing e-mails - there's usually so much to write down that currently things can get 'lost'
[16:50] <sil2100> elopio: I have some tools in the works that will help out
[16:50] <sil2100> But for now it's mostly manual ;)
[16:51] <elopio> popey: the problem is that it's not being 2 seconds. The one I saw was waiting for at least 15 seconds, and it never finished loading.
[16:52] <popey> hmm
[16:52] <elopio> sil2100: yes, don't worry. If I see something important not mentioned, I can reply anyway
[16:52] <popey> Ran 24 tests in 577.870s
[16:52] <popey> FAILED (failures=1)
[16:52] <elopio> your mail is getting bigger every day, that's not good either.
[16:53] <popey> will play some more elopio
[16:53] <robru> barry, want to assign line 33?
[17:04] <robru> sil2100, hey, your commitlogs for 78, 79, 80, and 81 are broken... 0-length files
[17:04] <robru> http://people.canonical.com/~lzemczak/landing-team/
[17:09] <barry> robru: yep
[17:18] <robru> barry, hey you're not in #ubuntu-ci-choo-choo ;-)
[17:18] <robru> (line 34 is ready for a silo too)
[17:21] <sil2100> Uh oh!
[17:21] <sil2100> robru: let me check that
[17:21] <sil2100> Ah
[17:22]  * sil2100 was auto-syncing from canonistack and something is broken it seems
[17:22] <robru> sil2100, failed to upload or something?
[17:22] <robru> ah
[17:22] <sil2100> Eeek!
[17:22] <sil2100> Ok, bug bug
[17:23] <sil2100> Let me fix that
[17:24] <sil2100> Now it should work, let me regenerate those and sync
[17:24] <sil2100> robru: thanks for noticing :)
[17:24] <robru> sil2100, apparently I'm the only person reading the landing mails... including you! ;-)
[17:25] <sil2100> Uh oh! You got meee!
[17:25] <sil2100> ;)
[17:26]  * barry hacks bip.conf
[17:33] <sil2100> robru: should be ok now I guess
[17:34] <robru> sil2100, thanks
[17:34] <sil2100> Ok, today I think I need to EOD in some normal, sane hours ;)
[17:34] <sil2100> Even though it's anyway past my EOD
[17:34] <sil2100> o/ See you on Monday eveyrone
[17:34] <sil2100> *everyone
[17:35] <robru> sil2100, have a good weekend!
[17:42] <popey> elopio: Ran 24 tests in 596.758s
[17:42] <popey> OK
[17:42] <popey> annoyingly passed that time
[17:44] <popey> (interestingly i had switched off wifi for that run) ☻
[18:12] <boiko> robru: I need to add one more MR to an existing component, it is just a matter of adding it to the list of MRs and reconfiguring the silo, right?
[18:50] <robru> boiko, yep, if it's an existing component, you can run the reconfigure job yourself and it'll work
[18:50] <robru> boiko, you only need me if you want to add a new component
[18:50] <boiko> robru: ok, I just did it
[18:50] <boiko> robru: but after I've done that, do I need to do a full rebuild?
[18:51] <boiko> robru: or can I just rebuild the component I changed?
[18:51] <robru> boiko, in theory you can just rebuild the one component, but then after that you have to do a WATCH_ONLY build, because otherwise it won't realize that the other components are already built
[18:52] <robru> barry, ^ fyi
[18:52] <boiko> robru: ah ok, next time I'll do that, thanks
[18:54] <robru> boiko, we've had a few snags with that sort of thing recently... citrain will insist that your other packages never built, so you can't publish them, and then you really do need to rebuild. so that WATCH_ONLY build is super important. maybe even do that one first ;-)
[18:58] <boiko> robru: ok, yes, the watch_only build I have used multiple times already
[18:58] <robru> alright
[19:29] <robru> barry, alright, I'm stepping out for lunch. wanna publish silo 12?
[19:33] <barry> robru: sure
[20:01] <robru> barry, thanks
[21:20] <Saviq> fginther, whoo! re: qmluitests :)
[22:26] <robru> I just gotta run out to the shops before they close, will be back in a bit to handle any landings if anybody needs.
[23:37] <robru> wow, busy day