[03:04] <imgbot> [04:14] <imgbot> [04:14] <imgbot> [09:26] <davmor2> Morning all
[09:32] <davmor2> brendand: is there no landing meeting this morning?
[09:32] <Mirv> morning
[09:32] <Mirv> davmor2: lukasz is away at least, I promised to keep an eye on landings
[09:32] <brendand> davmor2, not sure if ogra_ is around
[09:32] <brendand> davmor2, i'm not up for a landing meeting anyway :/
[09:33] <ogra_> i am kind of around, but technically not supposed to do anything else than the scrum sprint
[09:33] <Mirv> I'd say skip it, then
[09:34] <davmor2> I only came on this early for the meeting if it isn't on I'll catch you all at 11:00 and I'll go do some shopping instead :)
[09:34] <davmor2> skip it
[09:34] <Mirv> ok :)
[09:34] <Mirv> there are two landings I haven't landed since the bugs are not on whitelists
[09:36] <popey> \o/
[09:36] <popey> shopping
[09:36]  * popey is not here
[09:47] <brendand> Mirv, which are those?
[09:47] <brendand> Mirv, the rules have changed so much i wouldn't be surprised if you were confused by now
[09:50] <Mirv> brendand: they've change so many times by now that I'm definitely confused :)
[09:50] <Mirv> brendand: rtm-004 and rtm-023
[09:51] <Mirv> the last rules I understood were that anything that is rtm14+critical can be added to the wishlist, but still the bug would need to be approved on that wishlist or other rtm bug spreadsheets/e-mails before landing
[09:52] <brendand> Mirv, if they are tagged with rtm14 and a date, then they can be landed
[09:53] <Mirv> brendand: I understood the tags need to have been verified by PM team? otherwise anyone could add those tags
[09:53] <Mirv> for example bug #1374397 has the tag but no PM comment
[09:53] <brendand> Mirv, yeah
[09:54] <Mirv> I think rtm-004 is clear, though, since the only bug referred has touch tag added by PM member
[09:54] <Mirv> but 023 has that 1374397
[09:54] <brendand> Mirv, https://bugs.launchpad.net/camera-app/+bug/1374397/comments/11
[09:56] <Mirv> brendand: Joe is not on the product team? I understood it should be anyone from the trio olli, pat, victor
[09:56] <Mirv> ah, damn, olli _has_ modified the tag in there actually, between comments 15 and 16
[09:57] <Mirv> brendand: so, yeah, 023 is also clear. I stared too much at the lists and not the bug comments/tag operations
[10:02] <ogra_> Mirv, did you check the original list (004 was on there for example)
[10:03] <Mirv> ogra_: 004's 1382501 was not on the original 10/23 planning e-mail or wishlists
[10:03] <ogra_> no, it was on the list we had before
[10:04] <ogra_> on the initial list, before the mails started
[10:05] <Mirv> I've now 3 lists I'm checking, but I've probably forgotten about the "original original" list. I though the 10/23 mail had everything known so far.
[10:05] <Mirv> anyway, these resolved now
[10:05] <ogra_> k
[10:10] <ogra_> Mirv, "Fwd: bug assignments for the 10/16 image" on phablet@ (forwarded from ue-leads) has the list
[10:10] <ogra_> iirc there was another one like 004 that didnt make the milestone
[10:11]  * ogra_ forgot which or if it landed yet 
[10:21]  * brendand wonder if there is a blanket allowance for changes to test/ code
[10:28] <Mirv> ogra_: ah, right, I had that starred too but it looked so similar to the e-mail three days later that I had forgotten about it being different
[10:29] <ogra_> if we would just be able to use launchpad searches like we always did it would be so much easier
[10:30] <ogra_> spreadsheet vs spreadsheet vs html-list-in-an-old-email really doesnt help
[10:41]  * ogra_ poders about the luxury to have an image for each landing now that we are down to a slow pace
[10:42] <ogra_> i think i'll triger a build ;)
[10:42] <ogra_> +g
[10:42] <ogra_> done
[10:49] <imgbot> [11:05] <brendand> ogra_, have the latest ci failures been triaged?
[11:05] <ogra_> brendand, how would they without landing meeting?
[11:06] <brendand> ogra_, true, but has nobody been looking at them at all?
[11:06] <brendand> ogra_, my point being that i can if no-one else has
[11:07] <ogra_> well, i dont think anyone has tried to find out why system-settings dont finish anymore since 127
[11:08] <ogra_> no idea why rollin back apt would/could do that though
[11:09] <ogra_> for UITK we should have a landing ... not sure about music app
[11:09] <ogra_> i poked Saviq last week about the unity8 failures, not sure where they got with that, i know he had an idea
[11:10] <ogra_> weather and the list of crashers could need a closer look i guess
[11:11] <ogra_> and mvo__ should take a look at the failing click tests ... i poked him during the week but we havent talked much more about it yet
[11:12] <brendand> ogra_, says dropping letters is not found
[11:12] <ogra_> oh, thats in the click test ?
[11:13] <ogra_> interesting
[11:13] <brendand> ogra_, makes sense - because it's not there
[11:13] <brendand> ogra_, is it supposed to be?
[11:14] <ogra_> http://people.canonical.com/~ubuntu-archive/click_packages/click_list has it ... but i think that migh be overridden by the custom tarball on krillin rtm
[11:14] <brendand> i heard something about removing it i'm sure
[11:14] <ogra_> not sure about utopic, iirc there is should be still installed
[11:17] <ogra_> hmm, i guess the test uses click_list as a base on both distros ... which is wrong
[11:41] <oSoMoN> trainguards: hey, if anyone is alive and around, can I have a silo for line 74?
[11:42]  * oSoMoN is faster than queuebot
[11:59] <imgbot> [11:59] <imgbot> [12:00] <Mirv> oSoMoN: o/
[12:02]  * ogra_ does his first wipe flash of his krillin since re-partitioning ... 
[12:02] <ogra_> to much testing during the sprint ... my system is really messed up :(
[12:03] <ogra_> i wonder how i would back up the call history
[12:03] <davmor2> ogra_: you can't muhahahahahah
[12:04] <davmor2> ogra_: I'm assuming it is a db somewhere
[12:04] <ogra_> well, it must be stored somewhere
[12:05] <davmor2> ogra_: there is no list, it's like spoons in the matrix ;)
[12:06] <oSoMoN> ogra_, I believe it’s ~/.local/share/history-service/history.sqlite
[12:06] <ogra_> thanks !
[12:06] <oSoMoN> boiko would be able to confirm
[12:08] <ogra_> well, we will see in about 45min when the flashing is done and i have put the file back in place :)
[12:16] <brendand> ogra_, it seems python3-autopilot doesn't depend on python3-evdev
[12:17] <ogra_> brendand, causing what issue ?
[12:17] <ogra_> (we should have seen that since mid last week)
[12:18] <ogra_> (image 123)
[12:24] <brendand> ogra_, well it might not cause an issue in ci if another package is pulling that in
[12:24] <brendand> ogra_, but trying to run tests stand-alone it seems to be the case
[12:24] <ogra_> well, i see there are a few more failures between 122 and 123
[12:25] <ogra_> so it might actually affet some tests ... but only a few it seems
[12:26] <ogra_> we should add the dependency if it really affects stuff though
[12:28] <ogra_> i remember we moved that direct dep back and forth in the past ... and ended with seeding it instead of a dep ... i cant remembery why anymore though (but my brain is in degraded post-travel mode today) ... iirc xnox was involved in the decidion
[12:28] <ogra_> cwayne, yo !
[12:28] <cwayne> ogra_: hey man
[12:29] <ogra_> cwayne, could you somehow work out a way to get the click_image_test smoketest fixed with mvo__ ? i guess he needs to modify it a little to not use the default click_list but to get the preinstalled list from you somehow
[12:30] <ogra_> currently the test uses http://people.canonical.com/~ubuntu-archive/click_packages/click_list as master ... but that doesnt work when apps get removed via custom tarballs
[12:30] <ogra_> (i.e. dropping_letters, filemanager or terminal)
[12:32] <oSoMoN> woot, the CI train doesn’t seem to know of vivid
[12:32] <oSoMoN> Mirv, any idea what’s going on there? ^^
[12:33] <cwayne> ogra_: sure thing
[12:34] <cwayne> davmor2: new custom tarball is ready for testing. the entire change log is updating about 80% of the scopes with translations
[12:35] <cwayne> if helpful, i can get you teh exact clicks that have been updated for translation
[12:38] <davmor2> cwayne: no that's okay
[12:51] <Mirv> oSoMoN: sounds like we're not yet ready for vivid silos then :(
[12:51] <Mirv> oSoMoN: we checked assigning a silo worked, apparently there's a problem with build
[12:52] <Mirv> and I've built vivid packages, but without running the 'build' job since I'm uploading manual Qt packages
[12:52] <Mirv> sil2100 will be back tomorrow
[12:54] <oSoMoN> :(
[12:55] <Mirv> there's no absolutely simple place where 'vivid' could be just added in the code, it might need some jenkins updating too
[12:56] <Mirv> we may possibly not have vivid cowbuilder chroot:s yet. not that I'd know how to check that.
[13:01] <Mirv> did what I could find https://code.launchpad.net/~timo-jyrinki/cupstream2distro/more_vivid/+merge/239721 , but would need review from ribru at least when he wakes up
[13:02] <Mirv> I won't deploy it before it's reviewed by someone who knows what's ok to change and what's not
[13:32] <brendand> ogra_, the messaging app tests seem to be making unity8 crash (or whatever you want to call it ;) )
[13:33] <brendand> ogra_, i can't get through a whole run without being met by the u-s-c screen
[13:34] <ogra_> Saviq, ^^^ seems we really need to exclude the dash from lifecycle mgmt (i saw it restarting plenty during traveling home too)
[13:36] <brendand> ogra_, it's odd though. this is a fresh flash and i'm not doing anything with the dash. just running messaging AP tests
[13:37] <ogra_> which might eat your ram
[13:37] <brendand> ogra_, and actually there is a unity8 crash present
[13:37] <ogra_> oh, then it might not even be the dash
[14:00] <brendand> Mirv, should i be concerned about these failed copies? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-008/+packages
[14:01] <dobey> Mirv: hrmm, looking at that branch, i think you need to add vivid stuff, as well as keeping the current utopic stuff
[14:01] <dobey> Mirv: utopic isn't gone, and people may still need to land something there to get an SRU done, at least for the next 9 months
[14:05] <Mirv> brendand: no. sounds like related to previous landing, and LP just keeps them eternally until they are dismissed.
[14:21] <brendand> pete-woods, do you want https://launchpad.net/bugs/1380586 to land for RTM?
[14:42] <pete-woods> brendand: I think that's what is wanted, yes
[14:43] <brendand> pete-woods, i can't find it in any list though, can you check with olli
[14:44] <olli> trainguards, brendand, ogra_, sil2000 et all
[14:44] <pete-woods> brendand: I think I'd have to ask thostr, but he's not back til tomorrow
[14:44] <olli> we have reviewed the wishlist with changes since 10/24
[14:44] <olli> will send mail in a sec
[14:45] <ogra_> olli, take your time, landing team works in degraded mode today anyway ...
[14:45] <ogra_> (while our bodies arrived home our brains are mostly still traveling)
[14:45] <dobey> s/landing team/\*/g
[14:46] <ogra_> haha
[14:47] <Mirv> dobey: re: branch, vivid was already added in one place, and that branch adds it into second place plus assumes dual landings will be vivid/rtm (if any). tests could probably have more than one series being tested. anyway, ribru can check the branch.
[14:47] <dobey> lots of people had extended stays in DC or took today off
[14:47] <davmor2> dobey: speak for yourself I'm on tippedy top form today honest gov'nor I'm not tired at all
[14:47] <Mirv> olli: thanks
[14:48] <davmor2> dobey: luckily I had these matchsticks to hold my eyes open :D
[14:48] <dobey> davmor2: you're just high on all the extra sweeteners we put in stuff over here :P
[14:48] <Mirv> I'm quite thankful for 2 nights at home bed instead of that awful hotel one
[14:49] <Mirv> something around 2*12h of sleep
[14:49] <davmor2> dobey: hahaha
[14:49] <Mirv> that corn syrup coca-cola tasted so fake :D
[14:49] <dobey> heh
[14:50] <olli> ogra_, :)
[14:50] <davmor2> Mirv: it did I had to buy one at the airport so I had change for the bus back in the uk, it tasted so much nicer
[15:00] <brendand> ogra_, does messaging-app open sideways when the phone is flat on the table?
[15:03] <ogra_> brendand, sometimes (and how would the phone be able to guess what the rotation state is in that state)
[15:12] <davmor2> ogra_: I have apps open upside down too
[15:13] <ogra_> davmor2, fix your table :P
[15:14] <ogra_> get a water balance and make sure it is straight
[15:14] <davmor2> ogra_: open gallery with the phone flat on the table
[15:14] <ogra_> (and even then, what i said above still applies ... how is the phone supposed to guess rotation if it lies flat on the table)
[15:15] <davmor2> ogra_: same for system settings the odd thing is though for system settings the loading screen it the right way up
[15:15] <ogra_> happens on androidd all the time too
[15:16] <ogra_> the splash is hardcoded
[15:16] <ogra_> using the shell rotation (which doesnt ever rotate)
[15:16] <davmor2> haha
[15:17] <ogra_> if the shell would rotate too it would be consistent based on a guess the rotation sensor does in HW
[15:17] <ogra_> i think the bug here is that the shell doesnt rotate ... causing that inconsitent behavior
[15:18] <ogra_> there is no way to manipulate the sensor HW to make better guesses
[15:19] <ogra_> android does the exact same thing, but there you see the shell being rotated so you dotn expect apps to come up in a different rotation
[15:26] <asac> did the wifi battery fix land yet?
[15:26]  * asac overslept after lunch because phone ran out of battery :P
[15:26]  * asac sees a new si
[15:28] <ogra_> asac, yes, landed on sat.
[15:28] <ogra_> (and battery life got awesome long here for me )
[15:28] <asac> ok lets see if that image brings cure
[15:28] <ogra_> 126 had the fixes
[15:29] <ogra_> 128 had the rollback for the apt desaster we had
[15:30] <ogra_> (and 131 new location and trust-store fixes ... thats about all that landed since friday)
[15:30] <ogra_> mdeslaur, jdstrand ^^^i assume you noticed by now that we rolled back apt ?
[15:31]  * popey observed that the clocks changed correctly on his ubuntu phone and alarms went off at the right time today
[15:31] <asac> ogra_: 131 krillin rtm?
[15:31] <asac> good
[15:31] <asac> i think got them all
[15:31] <ogra_> asac, yup, latest one
[15:31]  * asac happy dog again
[15:31] <asac> lets see
[15:40] <davmor2> asac: and more import did you get a notification for the new image?
[15:41] <asac> davmor2: yes i got a green notification thingy message center
[15:41] <mdeslaur> ogra_: yeah, saw that
[15:41] <davmor2> asac: \o/ Chipaca your fix worked on more than my phone :D
[15:42] <mdeslaur> ogra_: my mind is still blown that the apt package has anything to do with installing clicks :P
[15:42] <ogra_> mdeslaur, it broke with the packagekit version we have in rtm ... i would propose you prepare another apt landing that also includes packagekit
[15:42] <mdeslaur> ogra_: sure, I'll get around to it eventually
[15:42] <ogra_> mdeslaur, yes, packagekit is liked against libapt-pgk or some such
[15:42] <mdeslaur> ogra_: I'll probably just backport the security fix
[15:43] <asac> hehe
[15:43] <asac> nice
[15:43] <asac> so 131 seems to crash unity shell
[15:43] <asac> when i hit messaging app icon
[15:43] <asac> i think the indicator was empty before
[15:43]  * asac thinks its all still indicators crashing
[15:44] <davmor2> asac: seems very crashy currently no idea why though
[15:44] <ogra_> asac, it doesnt crash :P
[15:44] <ogra_> asac, it is "lifecycle managed"
[15:44] <asac> davmor2: ack. if you can identify a test case, bisecting might help
[15:44] <asac> ogra_: that i dont believe until i get a proof
[15:44] <asac> i didnt have a single app open
[15:44] <ogra_> something hogs your ram
[15:44] <asac> it was a fresh boot
[15:44] <asac> just settings
[15:44] <asac> nothing else
[15:44] <asac> indicators got empty, then i started app and unity restarte
[15:45] <ogra_> something hogs your ram and that makes lifecycle mgmt kick in ... since there is nothing else to kill it kills the dash
[15:45] <ogra_> (which IMHO should not be managed at all, but i lost that argument :P )
[15:45] <asac> ogra_: so even if liefcycle has this effoect, i am sure we shouldnt rule out any other cause
[15:45] <ogra_> asac, oh, unity restarting is indeed something else
[15:45] <davmor2> ogra_: no it is things lock unlock pin on sim and the phone is locked that is even before unity8, phone call went yesterday and crash unity8/mir ie ubuntu icon spinning
[15:46] <ogra_> i understood your dash restarted
[15:46] <davmor2> s/lock/like
[15:46] <ogra_> davmor2, thats unity8 itself then ... or u-s-c or lightdm
[15:46] <ogra_> can be any of the three if you see the spinner
[15:47] <ogra_> check /var/crash
[15:47] <davmor2> ogra_: this is what is say the whole system seems less stable as a whole
[15:47] <ogra_> davmor2, yeah, i had that with my OTAed image at the airport if you remember
[15:47] <davmor2> ogra_: it's been wiped 6 times since then ;)  OTA testing today
[15:47] <ogra_> i was assuming it was because i had so many test packages installed manually though ...
[15:48] <ogra_> and i must say after a fresh bootstrap today it all seems far more stable to me
[15:48] <ogra_> (havent seen anything cashing in the last 4h)
[15:48] <ogra_> *crashing too :P
[15:49] <ogra_> davmor2, wiped or bootstrapped ?
[15:49] <davmor2> ogra_: yeah with the latest it seems more stable but I'm going to do some heavy testing on it after the ota and custom tarball testing is finished
[15:49] <davmor2> ogra_: wiped
[15:51] <ogra_> wow, the filemanager is pretty useless trying to see anything in /var/crash
[15:52]  * ogra_ sees a bunch of "_usr...rash" 
[15:52] <ogra_> there seems to be no kinf of list view
[15:52] <davmor2> ogra_: rotate your phone
[15:52] <ogra_> doesnt rotate
[15:52] <ogra_> (the app that is ... others do fine)
[15:53] <ogra_> oh, blind me
[15:53]  * ogra_ found list view now 
[15:53] <ogra_> seems i got mediascanner crashes since the new flashing
[15:53] <davmor2> ogra_: I blame you trying to use an app to do something it was designed for
[15:54] <ogra_> :P
[15:54] <ogra_> hah
[15:54] <ogra_> clicking a file in that dir gets me a filemanager crash
[15:55]  * ogra_ goes to the terminal ...
[15:55] <ogra_> hmm, so i have mediscanner, filemanager, u-a-l and scoperunner crashes ...
[15:55] <ogra_> from the last 4h
[15:56] <ogra_> u-a-l is still the fitbit thing crashing it
[15:56] <ogra_> cwayne, ^^ do we have a fix for that already somewhere ?
[15:57] <cwayne> ogra_: what fitbit crash?
[15:58] <ogra_> cwayne, http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/398/artifact/clientlogs/security/_usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash/*view*/
[15:58] <ogra_> has an example
[15:58] <ogra_> "icon-path-unhandled"
[15:58] <ogra_> krillin only indeed
[15:59] <cwayne> uhm, ill take a look
[15:59] <cwayne> not sure that should really count as a crash and trigger apport though...
[15:59] <ogra_> its a recoverable error
[16:00] <ogra_> but produces a crash file indeed
[16:00] <cwayne> ill take a look, i believe that desktop file is automagically created by the scopes api, but will double check
[16:00] <ogra_> whom do i poke about the dashboard ?
[16:00] <cwayne> me :)
[16:01] <ogra_> it seems to never use the proper location data (looks actually like geoip, it is about 150km off at the next node of my provider)
[16:01] <davmor2> ogra_: if it isn't on mako it's cwaynes fault
[16:01] <cwayne> ogra_: it uses whatever unity-scopes-api gives us, and iirc the only think it uses location data for is sunrise/sunset
[16:01] <ogra_> the rest of the system seems to use location just fine ... on the spot on my house
[16:02] <ogra_> cwayne, well, and weather
[16:02] <cwayne> ah right
[16:02] <cwayne> so weather isn't one of ours, it's a remote scope
[16:02] <ogra_> tapping weeather gives me the 150km away location from geoip
[16:02] <cwayne> so I'm not sure how accurate it's location data is
[16:02] <cwayne> so that's not me actually, that's lucio :)
[16:03] <davmor2> cwayne: no it's you, you can blame lucio after but everything is your fault :P
[16:04] <cwayne> ha
[16:04] <davmor2> cwayne: if the scope is passing the geoip rather than the actual location then that won't help
[16:05] <dbarth> hey guys, are vivid landings possible this week?
[16:05] <dbarth> for all those silos that are not meant for rtm
[16:06] <cwayne> davmor2: dashbord isn't doing anything, weather only does geoip AIUI
[16:06] <cwayne> it's not allowed your lat/lng since its remote
[16:07] <ogra_> bad weather then
[16:12] <davmor2> cwayne: it's still your fault though don't think you are getting off that light ;)
[16:13] <cwayne> yeah, perhaps that's one that should be re-written to be local
[16:13] <cwayne> i'll poke some people
[16:14] <davmor2> cwayne: hahahaha :)
[16:17] <cwayne> davmor2: u wot m8
[16:19] <davmor2> cwayne: see that sounds less Cockney than when you say it :P
[16:20] <cwayne> lol
[16:25] <ribru> Mirv: hey, just up. will check branch asap
[16:42] <brendand> dbarth, what do you want to do with silo 009 for RTM?
[16:47] <ribru> Mirv: https://ci-train.ubuntu.com/job/upgrade-chroot/106/console looks good so far! I don't think I was involved in the opening of utopic so I had no idea how this would go but congrats ;-)
[16:47] <ribru> Mirv: it says SUCCESS but we should look into that libeatmydata thing...
[16:55] <ribru> oSoMoN: Mirv: ok looks like it's working (well, at least that one traceback is fixed, we'll see if anything else pops up) https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/85/console
[16:56] <dbarth> brendand: hi; i'd like to re-target that for a non-rtm landing
[16:56] <oSoMoN> ribru, cool, thanks
[16:57] <dbarth> ribru: ribru?! the new robru
[16:57] <brendand> dbarth, ok
[16:58] <dbarth> brendand: is vivid opening soon?
[16:58] <ribru> dbarth: ;-)
[16:58] <ribru> oSoMoN: you're welcome!
[16:58] <ribru> infinity: cjwatson: any thoughts on this libeatmydata spew? https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/85/console can it harm builds? can we fix it?
[16:59] <brendand> dbarth, last i heard it's not ready for landings yet
[17:00] <dbarth> brendand: ok; i'll continue asking tomorrow then ;)
[17:01] <dbarth> brendand: otherwise, i will re-add silo 20 back on the whishlist to get this one going
[17:04] <ribru> dbarth: we're doing the very first vivid landing right now, do you want to be number 2?
[17:05] <ribru> also, is it european dst right now or something? why did all my meetings jump forward an hour?
[17:06] <dbarth> ribru: oh, nice; i would gladly be
[17:06] <ribru> dbarth: k, which spreadsheet row?
[17:06] <dbarth> ribru: we flipped DST this week-end, yes
[17:06] <ribru> thanks
[17:06] <dbarth> lemme check
[17:08] <dbarth> ribru: line 19 and 20; so remove the line 19 landing request, and reconfig 20 for vivid please
[17:08] <ribru> dbarth: ok sure
[17:09] <ribru> dbarth: oh, so you don't want to land this in rtm then?
[17:09] <dbarth> ribru: nope, not now; the bugs are not critical enough
[17:10] <dbarth> ribru: can i also turn silo 020 to vivid maybe?
[17:10] <dbarth> ie, is the landing policy back to: devel 1st and stable next?
[17:10] <ribru> dbarth: yes vivid is wide open for all feature development
[17:11] <dbarth> cool!
[17:15] <ribru> Mirv: do you plan to free utopic/15?
[17:16] <ribru> dbarth: ok for starters you have silo vivid/8 http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-008 still looking at the other one
[17:19] <ribru> dbarth: hm, are you sure silo rtm-20 isn't a critical fix needed for rtm? "password prompt broken" sounds pretty serious.
[17:22] <dbarth> ribru: it's still a question mark; the severity is limited to cases where users /change/ their passwords
[17:22] <dbarth> ribru: but yeah, a potential rtm fix
[17:23] <ribru> dbarth: ok well I won't free that silo then, but we can make a sync silo to also sync it to vivid
[17:26] <ribru> dbarth: https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/87/console ok building for vivid
[17:32] <ribru> uh
[17:33] <ribru> well shit
[17:35] <davmor2> ribru: say what now?
[17:35] <ribru> davmor2:  ^^ check the uncaught exception. it says the file doesn't exist, but the build log clearly shows that file existing. i'm stumped.
[17:35] <ribru> dbarth: I guess hold off on doing that passowrd one in vivid for today
[17:36] <ribru> dbarth: but webbrowser app should be ready to test soon
[17:36] <ribru> davmor2: https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/87/consoleFull
[17:36] <dbarth> ribru: np; i'll let you check the file issue
[17:36] <dbarth> ribru: for ref. i think i had seen that one before during an rtm build attempt
[17:37] <ribru> dbarth: yeah there was an issue where the code just called '*.dsc' and it would break if there were two dsc files, but we fixed that some time back, so I have no idea what this issue is
[17:38] <davmor2> ribru: that's a lot of errors for something that is meant to of built
[17:39] <ribru> davmor2: ignore the libeatmydata stuff. i have no idea what that is, and stuff seems to be working in spite of that (it's coming up in all vivid logs). just check the traceback at the very end
[17:42] <davmor2> ribru: is citrain supporting vivid?  I thought Mirv said it wasn't this morning
[17:42] <ribru> davmor2: yeah mirv had a branch taht fixed it and I landed it so it's "working" now
[17:42] <davmor2> ribru: I blame Mirv then ;)
[17:44] <ribru> davmor2: dunno, the file pretty clearly exists: https://ci-train.ubuntu.com/job/cyphermox-test/309/console
[17:46] <ribru> dbarth: oh, i just noticed the package was actually uploaded, so WATCH_ONLY build seems to be working anyway: https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/88/console
[17:48] <brendand> ogra_, what is going on that so many things are crashing unity8?
[17:48] <brendand> ogra_, what could we have landed?
[17:51] <davmor2> brendand: only seems to of been from Saturday I wonder if it is the low power wifi stuff
[17:53] <davmor2> brendand: and possibly dbus-cpp by the sound of it ;)
[17:54] <ogra_> brendand, nothing really
[17:54] <dobey> ribru: so given the vivid issue above, is it possible to sync something from rtm to vivid?
[17:55] <ribru> dobey: yes it seems to be possible, there is a strange traceback but it doesn't happen until after the PPA upload completes, so the packages should be building in the ppa without issue.
[17:56] <dobey> ribru: ok cool. can we get a silo for line 45 in the spreadsheet then?
[17:56] <mandel> cihelp, how can I find the -dbgsyms for a silo?
[17:57] <ogra_> davmor2, the wifi changes cant crash unity8 (well, not directly at least)
[17:57] <ribru> dobey: ok, vivid 14
[17:57] <davmor2> ogra_: if they take out dbus I bet they could ;)
[17:57] <ogra_> brendand, davmor2, we dropped the hud ... but there were no dependencies declared on it by unity ....
[17:57] <ribru> mandel: IIRC those don't exist.
[17:58] <mandel> ribru, oh.. what a pita
[17:58] <ribru> mandel:  yep ;-)
[17:58] <ogra_> they doi exist for the rtm archive though
[17:58] <ogra_> so you should be able to use them after landing
[17:58] <ribru> mandel: there was a big discussion about that some weeks ago. IIRC the dbgsym packages are created at publish time, not at silo build time
[17:58] <ogra_> (now dont ask me where ... thats a pitti question)
[17:59] <davmor2> mandel: have a look at the silo ppa some include .debug in which case you can just grab the package and install it right?
[17:59] <ribru> dbarth: approve merges please -) https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/43/console
[17:59] <mandel> ribru, is a little annoying to have them at publish time when a silo under tests crashes
[17:59] <mandel> davmor2, I have a work around and created the debug for myself, I was asking to see if that was an ugly work around
[18:00] <ribru> mandel: yeah I totally hear you, sorry I can't remember more details, slangasek or infinity would know more, but it has something to do with launchpad, it's not something we can control from the ci train side.
[18:00] <davmor2> mandel: there is no such thing as an ugly work around if it works ;)
[18:00] <mandel> ribru, ack, is just unfortunate :)
[18:00] <mandel> davmor2, well... as it is right now is not reusable :P
[18:01] <dobey> ribru, mandel: i thought it just needs to have ddebs enabled on the PPAs?
[18:04]  * mandel mandel|lunch
[18:07] <dobey> ribru: yeah, we just need to get an admin to enable ddebs for all the landing PPAs
[18:12] <dobey> are there vivid builds on the system-image server yet? or should i just test the silo on utopic on my mako?
[18:40] <infinity> ribru: The ddeb availability issue isn't LP's fault, but rather that we're not using LP for them (yet) because we can't.  That's going to be solved VEry Soon, it looks like.
[18:41] <infinity> ribru: As for the eatmydata thing, that's entirely out of my hands as a distro guy, it looks like your infra tries to LD_PRELOAD it, but your chroots don't have it installed.
[18:41] <infinity> ribru: Harmless, but noisy (and not getting you the speed boost you're hoping for).
[18:42] <ribru> infinity: Hmmmmmmm thanks for the tip
[18:42] <ribru> Not sure why it wouldn't be installed
[18:42] <ribru> (I didn't make the chroots)
[18:42] <ribru> Will poke at it in a bit. Brb, lunch
[18:56] <davmor2> ogra_, ribru, cwayne: custom tarball is good :)
[18:56] <ogra_> land it then :)
[19:09] <mandel|lunch> cihelp, I'd like to block the landing of silo 13 for rtm, eventhough the branches have been approved I'm able to reproduce the bug that it in theory fixes
[19:09] <mandel> cihelp, should I just change the value in the spreadsheet?
[19:10] <dobey> mandel: if it fails tests, change the "testing pass?" column to "no" for that line in the spreadsheet
[19:11] <mandel> dobey, just that? is there a way to comment or should I just add a comment in the bug?
[19:11] <dobey> mandel: there's a comments column too. add comments there :)
[19:12] <mandel> dobey, ugh, the formatting is going to suck :-/
[19:12] <mandel> dobey, is a cpp bt from gdb
[19:12] <mandel> in a spreadsheet
[19:12] <dobey> well, put that in the bug then
[19:13] <dobey> and in the spreadsheet comments field put "testing failed, see bug #xxxxxxx" or something
[19:13] <dobey> obviously don't put stack traces in spreadsheet fields :P
[19:16] <ribru> mandel: yeah what dobey said.
[19:16] <ribru> mandel: also for silo / spreadsheet questions you should ping trainguards, not cihelp.
[19:17] <ogra_> you could paste the bt into the MP column .... just to test ribru's code ;)
[19:17] <dobey> watch it explode
[19:17] <ogra_> if the dashboard shows burning flames you broke it :)
[19:18] <dobey> (because that spreadsheet is already incredibly slow already, a 30K line stack trace probably is not going to be fun)
[19:18] <ogra_> might be fun to have queuebot patse it into IRC though ... one line per char
[19:19] <dobey> heh
[19:20] <ribru> ogra_: queuebot already has message-length restrictions. watch the migration messages from silos containing more than a handful of packages and you'll see it's often clipped.
[19:20] <ogra_> bah, spoiling all the fun ... these bot devs
[19:22]  * dobey puts +++ath in the spreadsheet
[19:33] <dobey> ogra_: any idea when vivid images will be available to flash?
[19:35] <cwayne> ogra_: sorry, had been at dr's, so i'm good to publish custom?
[19:36] <davmor2> cwayne: likely story ;)
[19:39] <cwayne> davmor2: ha, so should I press the magic button, or do i need to wait for ribru or someone on ye olde landing team
[19:42] <davmor2> cwayne: yes it's good as far as I can tell
[19:43] <cwayne> ok, hitting the magic button then
[19:44] <cwayne> aaand built
[19:44] <cwayne> WOO TRANSLATED SCOPES NOW IN IMAGE WOO
[19:57] <ribru> cwayne: er, what button did you hit?
[20:00] <cwayne> ribru: running a jenkins job to move the custom tarball past the qa gate
[20:01] <ribru> cwayne: uh, what jenkins is that? that's not part of the train as far as I knwo
[20:01] <cwayne> it's not part of the train, it's usually just getting a +1 from QA
[20:01] <cwayne> it's on s-jenkins
[20:02] <ribru> cwayne: ah ok, nm then. you said 'pressing the button' then queuebot didn't say anything so I thought maybe whatever you pressed didn't work. but if it's not part of the train then no worries
[20:03] <davmor2> ribru: were you hungry when you got up?
[20:03] <ribru> davmor2: yes, just like every day...
[20:04] <davmor2> ribru: that explains your nick then, I think we know what you might have a craving for ;)
[20:05] <ribru> davmor2: haven't read the channel topic in a couple weeks i guess?
[20:06] <davmor2> ribru: yeah just seemed funnier than the actual truth of the matter :)
[20:07] <ribru> davmor2: I'm craving my ribs to reconnect to themselves in a healthy way so i can get out of bed... ;-)
[20:07] <davmor2> I think you are safer where you are if you go around breaking ribs for the fun of it ;)
[20:17] <mandel> davmor2, can you help me understand how can I request a silo for line 55 in rtm and vivid?
[20:17] <mandel> davmor2, it looks like it was request for utopic but we should land in vivid and do an SRU, correct?
[20:26] <ribru> mandel: yes, vivid-first landings I think are best. I heard a rumour that we don't need the full rigamarole of an SRU though, there's going to be a sort of SRU-lite where we just land things in a special blessed PPA for utopic-based phone images going forward.
[20:27] <mandel> ribru, so I updated the spreadsheet, is there anything else we need to do
[20:27] <mandel> ??
[20:27] <mandel> that we == I
[20:27] <ribru> mandel: which row?
[20:27] <mandel> ribru, 55
[20:27] <ribru> mandel: looks good, I'll assign it
[20:29] <ribru> fginther: around?
[20:33] <mandel> ribru, superb, thx, do I have to request one for rtm too?
[20:34] <ribru> mandel: yeah rtm will require a second spreadsheet row with a second silo. is your landing one of the approved critical rtm fixes?
[20:35] <mandel> ribru, that is a very good question, I'll have to check that and ping people to get it there is not present
[20:36] <ribru> mandel: ok ping olli or asac about that I guess. once they approve it we can go for qa and get it into rtm
[20:37] <mandel> ribru, ack
[20:38] <olli> mandel, which one?
[20:39] <mandel> olli, bug 1341685
[20:39] <mandel> olli, is a fix that affects system image at the unit/integration tests level which is making barry s life horrible when trying to land system image
[20:41] <barry> mandel, olli note that that could also be considered a security bug.  it's asking on the wrong bus for whether the connection is constrained or unconstrained, though it's probably making the wrong answer in the safer direction.
[20:41] <olli> mandel, I added it to the wishlist and we'll check in tomorrow
[20:41] <olli> barry, that's one way to look at it ;)
[20:41] <mandel> olli, ok, it is quite critical from our point of view a barry mentioned
[20:41] <mandel> olli, lets say we really really strongly wish for it ;)
[20:42] <barry> cool.  olli let me know too about the phased update bug for si.  that's been communicated to me as critical for rtm too ;).  (i'm getting ready to put it in a silo for testing)
[20:42] <mandel> barry, we have a silo for vivid, would be nice if we test it there already
[20:43] <mandel> barry, at least we can have it there asap
[20:43] <barry> mandel: i'm not going to land my branch in vivid, though i will merge it into my si 3.0 branch for vivid.  rtm will only have si 2.5.1 and i don't plan to sru it into utopic (mostly because nobody cares)
[20:44] <barry> so si 2.5.1 is rtm only
[20:44] <mandel> barry, ok, well, I'll be aming for vivid and later in rtm (I'll be creating a utopic branch in the project to be able to sru stuff)
[20:45] <barry> mandel: cool
[20:45] <olli> barry, id on the phased one?
[20:45] <olli> I thought that was already +1'd
[20:45] <olli> but... I see way too many bugs atm
[20:47] <barry> olli: it's on "the" spreadsheet, but it's also LP: 1383539
[20:49] <ribru> infinity: https://ci-train.ubuntu.com/job/upgrade-chroot/113/console eatmydata is definitely installed in the chroot, reinstalling it doesn't seem to help. any ideas on how to fix that? I'm totally unfamiliar with eatmydata, i guess it's just configured wrongly.
[20:49] <ribru> or broken in vivid
[20:50] <barry> ribru: are you seeing eatmydata problems on a vivid chroot?
[20:50] <olli> barry, comment #4
[20:50] <olli> is there anything else you think is holding you back>
[20:50] <olli> ?
[20:51] <barry> ribru: comment #4 on which bug?
[20:51] <olli> https://launchpad.net/bugs/1383539
[20:52] <barry> olli: oops, yes, thanks
[20:52] <olli> :)
[20:52] <olli> np, sorry, this is a mess, I understand
[20:52] <barry> olli != ribru :)
[20:52] <olli> no insult taken
[20:53] <barry> olli: i hope your ribs are in better shape ;)
[21:02] <ribru> barry: oh yes, i just set up the vivid chroots today and while they seem to be "working", there's eatmydata spew everywhere.
[21:03] <ribru> barry: just for starters: https://ci-train.ubuntu.com/job/upgrade-chroot/113/console but the build jobs are even worse
[21:04] <barry> ribru: i saw that too when i set up my vivids yesterday.  haven't spent any time investigating
[21:04] <ribru> barry: I've been poking at it. infinity suggested it was because eatmydata was missing but I confirmed it's not missing. not sure what else to even check. not my specialty
[21:05] <barry> ribru: yeah, i did a naive apt-get reinstall of eatmydata in my vivid chroot and that didn't help.
[21:05] <ribru> barry: heh same. https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/85/console fun
[21:06] <barry> gorp
[21:07] <ribru> barry: ok well if it's bit you too then I'll just chalk it up to "vivid is broken" and move on to the next thing in my to-do list. lemme know if you make any progress on that one, thanks ;-)
[21:07] <barry> ribru: same back atcha :)
[21:09] <ribru> barry: I have no idea what eatmydata even does. I'd just as well disable it as fix it.
[21:11] <barry> ribru: it speeds things up by disabling fsync and friends.  of course, that means you can lose data, but who cares in a chroot?
[21:11] <ribru> ah
[21:11] <ribru> barry: so it's not something anybody would ever use outside of a chroot?
[21:13] <slangasek> ribru, mandel: the process for landing on RTM hasn't changed, anything to be landed there still has to have a full landing - and since vivid and 14.09 will now have toolchain skew, these need to be separate sources / separate builds
[21:13] <barry> ribru: not if they didn't want their data eaten.  it's aptly named :)
[21:20] <ribru> slangasek: https://code.launchpad.net/~robru/cupstream2distro/force-rtm-versions/+merge/239775 ok here's the branch that forces ~rtm version tagging unconditionally, and defaults to source syncs. We'll let sil review it tomorrow
[21:21] <slangasek> ribru: sounds good
[21:51] <ribru> AlbertA: around? I'm just investigating what happened in your silo 17 ^^
[21:51] <AlbertA> ribru: tvoss will take a look, I think what happened is an update was made to vivid but the branch was not merged to the project trunk
[21:51] <ribru> AlbertA: so it looks like location-service is also in silo 6, which claims to be in a state 'you can publish' but somehow is already in distro now. not sure how that came to be. anyway it looks like if we merge & clean that one then your build will be fine
[21:51] <ribru> AlbertA: yeah that sounds about right
[21:52] <ribru> AlbertA: want me to merge the other silo or should I coordinate with tvoss first?
[21:53] <AlbertA> ribru: go ahead and merge
[21:53] <ribru> AlbertA: sweet
[21:53] <AlbertA> ribru: thanks!
[21:53] <ribru> AlbertA: you're welcome
[21:55] <ribru> awesome
[22:02] <ribru> AlbertA: https://ci-train.ubuntu.com/job/ubuntu-landing-017-1-build/76/console ok looks like it's building now
[22:02] <AlbertA> ribru: awesome thanks!
[22:02] <ribru> AlbertA: you're welcome!
[22:37] <tvoss> robru, mind undoing the merging? I think the branches got messed up
[22:38] <tvoss> ribru, I thought the rtm referred to line 36 of the spreadsheet?
[22:41] <ribru> tvoss: not sure what you mean. 36 was definitely set for utopic.
[22:42] <ribru> tvoss: not sure what happened to that landing though. silo claimed it was ready to publish, but the package was in utopic. not sure how it got there without publishing. i guess somebody manually uploaded that
[22:42] <ribru> tvoss: I can revert the trunk commit I did, do you want the package also reverted in utopic? that's a bit harder
[22:42] <ribru> but possible
[22:43] <ribru> err, maybe not so possible in utopic, but we can rever it for vivid I mean ;-)
[22:44] <ribru> AlbertA: tvoss: https://launchpadlibrarian.net/188458283/buildlog_ubuntu-vivid-amd64.location-service_2.1%2B15.04.20141027.1-0ubuntu1_FAILEDTOBUILD.txt.gz also this is a weird build failure. missing dependencies somehow?
[22:55] <tvoss> ribru, nope, one of the tests times out
[22:55] <tvoss> ribru, okay, I will try to untangle it tomorrow
[22:55] <tvoss> ribru, what about rtm silo 6?
[22:56] <tvoss> ribru, sorry, hang on
[22:56] <ribru> tvoss: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-006 rtm 6 is unrelated ;-)
[22:56] <ribru> tvoss: utopic 6 was somehow in utopic but not merged to trunk, which is why I pushed to trunk, to try and sync those up
[22:56] <ribru> tvoss: so utopic 6 silo is free now
[22:57] <tvoss> ribru, okay, looking here, the wrong mp got merged: https://launchpad.net/ubuntu-rtm/+source/location-service
[22:57] <tvoss> or better: released
[22:57] <tvoss> ribru, seems like an autosync happened
[22:58] <tvoss> ribru, can we revert that release in rtm at least?
[22:58] <ribru> tvoss: looks like the rtm release matches the utopic release
[22:58] <tvoss> ribru, sure, but that's still not correct :)
[22:59] <ribru> tvoss: there was a translation update if that's what you mean. those auto-sync into trunk and then get included with whatever other releases happen
[22:59] <ribru> tvoss: we can revert it, I'm just not sure how it got into utopic/rtm in the first place.
[23:00] <ribru> tvoss: like it would have had to have gone past qa to get into rtm. if we revert it that presumably also needs to get past qa
[23:00] <tvoss> ribru, yup, same here. But I would like to avoid having such an artifact in rtm
[23:00] <tvoss> ribru, okay, I can lookinto it further tomorrow my afternoon, not before
[23:01] <ribru> tvoss: ok sorry, do you want me to prep a revert now? or wait?
[23:01] <tvoss> ribru, if you feel comfortable reverting, do so. If not, I can see to it tomorrow
[23:02] <ribru> tvoss: ok, I'll leave it then, as I'm not very familiar with the revert tooling. I'll write an email to sil and ogra since I think they know more about that
[23:02] <tvoss> ribru, thanks
[23:03] <ribru> tvoss: you're welcome