[00:05] ribru: yep. i think that's i386 [00:05] ribru: we'll see if it'll succeed. anyway, i'm going to watch a bit of the world series and check in now and then [00:06] barry: ok cool. I'm nearing EOD but should be around later if anything comes up [01:06] trainguards: any idea what this is about: https://ci-train.ubuntu.com/job/ubuntu-landing-026-1-build/12/console ? === fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru broke 3 ribs [01:23] boiko: no, I've seen that before but haven't been able to figure it out yet. I think the package was uploaded in the PPA though, so if you just do a WATCH_ONLY it should be fine. [02:56] barry: just noticed your build failed with a bunch of timeouts, so I retried it [03:04] === trainguards: RTM IMAGE 138 building (started: 20141030 03:05) === [03:05] You know you need to go to bed when... "imgbot says..." [04:21] ribru: hey, still around? thanks for the retry. looks like it's now built === chihchun_afk is now known as chihchun [05:11] mornings [05:19] barry: bedtime soon ;-) need something? [07:16] sigh for adding new Qt private header users [08:53] sil2100: ^ so Zoltan is on holiday, I made a branch and preparing for landing. I just don't have any history on the topic other than I remember he mentioned it during the spring and there is a "stupidly easy fix". at least it affects only tests, so maybe if UITK AP is fine it could be considered for releasing... [08:55] * sil2100 looks at the change [08:56] Mirv: yeah, I think it's reasonable to only check autopilot results for UITK in this case [08:56] that's the comment #5 from dandrada on bug #1382414 [08:56] bug 1382414 in Ubuntu UI Toolkit "New qtmir makes UITK AP tests fail" [Critical,In progress] https://launchpad.net/bugs/1382414 [08:56] But I already remember a branch from ricmm I think [08:56] sil2100: but but, are "our" blockers approved by product team, I was wondering? [08:57] sil2100: there's nothing attached to the bug report though. [08:57] no UITK branches at https://code.launchpad.net/~ricmm/ [08:57] Mirv: infrastructure blockers are a bit different, but I'll make sure PT is aware [08:57] sil2100: ok, thanks === chihchun is now known as chihchun_afk [09:09] hmpf ... seems we have lockfile issues on the image builder === karni is now known as karni-brb [09:17] Morning all [09:19] Morning [09:19] davmor2: good to hear that currently we have just that unity8 blocker :) [09:19] + the autopilot one I personally added [09:20] hmm, i just got an SMS with no sound [09:21] oh, volume was turned down ... [09:21] (turning it up again restarted my session though) [09:22] ogra_: haha yeah that fix really needs to land :) [09:23] davmor2, well, if we only could build any images now :P [09:23] ProtocolError: for all images ... yay [09:24] ogra_: man you developers you are set on destroying the world with your code ;) [09:24] lol [09:24] this time it is datacenter admins, not developers [09:25] yay for lockfiles [09:25] ogra_: yeah cause there is no code stored in a datacenter right.......wait a minute, you're trying to trick me ;) [09:25] :P [09:30] woah [09:30] my session *didnt* restart [09:30] * ogra_ just noticed the phone is still on the spinner [09:30] * ogra_ reboots hard === karni-brb is now known as karni [09:48] o_O [09:55] ogra_, who's the best person to ask how to deal with the idle level issue? [09:55] ogra_, assuming it's being calculated correctly [09:56] brendand, i guess plars has dug deepest into it from a test side ... or do you mean for deciding about raising the value ? [09:57] ogra_, yeah - if the test is telling the truth then we either need to fix something in the system to make it better, or raise the value [09:58] ogra_, do we even know if one component is at fault? or it could be many [09:59] brendand, well, i think we should invest a day and go through all topbefore/after logs and grep out the top consumers to get some heuristics [09:59] and on that base make a decision [10:00] (assuming the numbers are right) [10:02] ogra_, http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/433/artifact/clientlogs/sudoku_app/topbefore.log/*view*/ [10:03] ogra_, unity8-dash - 81.8%! [10:03] yeah [10:03] the question is for how many iterations [10:03] ogra_, nearby 64, news 34 [10:03] remember, each top loop is only a snapshot [10:05] brendand, we should grep the first 5 lines out of each loop, collect the top consumers from that and take the average ... [10:05] if we do that for a bunch of runs we should find the bad guy [10:05] (thats why i said we should invest a day, i meant that literally, it will take time to collect) [10:06] ogra_, hmm yeah. it's only that high for the last couple of iterations [10:06] and we should compare to mako === chihchun_afk is now known as chihchun [10:06] if the same process does the same there but simply stelles faster then i guess we cant do much about it (except make the app faster or some such) [10:07] *settles [10:07] in that case i would vote for adjusting the value (but also let the app owner know) [10:09] wget -O- -q http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/433/artifact/clientlogs/sudoku_app/topbefore.log/*view*/|grep PID -A3|grep -v ^PID [10:09] brendand, that gives us the three top consumers of each run [10:10] ogra_, is mako ok? [10:10] hmmmm I guess this is a bad thing right 15138 phablet 20 0 275220 48168 25044 S 95.5 4.9 17:55.60 system-set+ [10:10] how do you mean ok ? [10:11] ogra_, i'm wondering is the negative value in this run being ignored? http://dashboard.ubuntu-ci:8080/smokeng/utopic/touch_stable/krillin/136:20141029.1:20141028-3ca60be/643/sudoku_app/225287/ [10:11] ogra_, by ok i mean do settle tests fail there or not? [10:11] it think they do but sinificantly less [10:11] ah, wait [10:11] wget -O- -q http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/433/artifact/clientlogs/sudoku_app/topbefore.log/*view*/|grep -v "top -c -b -d 6 -n 5"| grep PID -A3|grep -v ^PID [10:12] this is a better command ... filterin out top itself first [10:16] wget -O- -q http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/433/artifact/clientlogs/sudoku_app/topbefore.log/*view*/|grep -v "top -c -b -d 6 -n 5"| grep PID -A3|grep -v ^PID|cut -d' ' -f9,12 [10:16] and that gives us a nicer formatting [10:16] * Saviq split up the unity8 mega silo, only includes what's already in rtm now [10:16] (cpu percentage and processname) [10:17] brendand, so using that line above over a bunch of topbefore/topafter logs should give an impression what is keeping the system busy [10:18] * ogra_ ponders ... [10:18] how about we cut out everything starting with 0. [10:20] brendand: https://code.launchpad.net/~psivaa/ubuntu-test-cases/skip-unity-8-for-utopic/+merge/235791 is a sample of how we skip tests for a certain channel. similar could be done but as you could see it's a little ugly [10:21] psivaa_, well yeah it is a bit hacky, but if that's the best we can do for now with the system we have [10:21] sil2100: this is what i have for the vivid test setup from plars: [10:21] plars> fginther|away, josepht: so it looks like we might have vivid images in devel-proposed soon, going to try to update stuff tonight but there's no new distro-info-data package yet, so have to hack around that for now [10:21] ogra_: if you cut out 1's too that get rid of all the binary ;) [10:22] sil2100: plars is at a conference, i'll ping him about the progress when i get hold of him later [10:22] psivaa_: ok, thanks :) [10:22] davmor2, lol [10:24] brendand, so looking at it with the ablve command (and ignoring the first three runs where the session still settles down) i see dbus-daemon, upowerd and indicator-power being the busy ones ... with an occasional spike of unity8 [10:25] which makes me think if mako would look different that krillin is simply very chatty with upowerd [10:25] keeping the dbus noisy [10:25] thats just a guess thogh, we have to compare mako [10:32] ribru: Binary syncs aren't discouraged in any kind of long-term way, and are often still appropriate; the probability of failure is just a bit higher than usual since vivid and 14.09 are diverging a fair bit at the moment. I'd appreciate you not ripping out that code. [10:32] A package with long build times but uncomplicated and easily-analysed dependencies is still likely to be appropriate for binary syncing. [10:33] ogra_, i run it on my krillin and nothing seems to ever take more than 2% [10:34] ogra_, except for unity8 on a couple of occasions [10:34] ogra_, but it still fails [10:34] ogra_: any news on the image builds? [10:36] ogra_, i think i understand what's going on now [10:40] sil2100, can I get silo for row 30 please [10:40] ogra_, so basically the script wants the system to reach a certain idle level, for some reason krillin can't do that [10:40] ogra_, spikes shouldn't affect the outcome [10:41] Saviq: oh no, is that a new one? [10:41] ogra_, rather one of the things you mentioned is keeping krillin constantly above that level [10:41] * sil2100 prepares the manual prepare_silo job [10:41] sil2100, it is, I needed to split the big one [10:41] ogra_, the question is whether we can fix that or it's just something we need to accept [10:42] sil2100, it was too big to understand issues that we've noticed [10:42] ogra_, i'm not that knowledgable about these things, but any chance the lower clock speed could make a difference? [10:43] Saviq: assigning [10:43] Mirv, ogra_, asac, ribru: I guess it's time to draw the line [10:44] NOTICE! Landings going on halt! === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CI Train on halt! No non-blocker landings accepted until image promotion! [10:44] sil2100, awwww [10:47] Mirv, did that camera-app landing make it in? [10:47] sil2100, thanks [10:47] Mirv, it has test fixes that are wanted [10:51] brendand: I published it since that was a pre-requirement for newer .click to build, kicked a .click build and asked bfiller to have it uploaded when it's ready. I'm not sure if it made it in, but if not I can also upload it. [10:51] it's over here http://s-jenkins.ubuntu-ci:8080/job/camera-app-click/149/ [10:52] Mirv, yeah it would be nice to fix those tests - but i guess landings are frozen? [10:53] sil2100: are they ^ [10:54] Mirv: see topic [10:54] oh, topic [10:54] :) [10:54] * sil2100 prepares an announcement e-mail [10:55] can I have a silo for row 92 please [10:55] there are two bugs from the wishlist list and three bugs not there [10:57] correction, three bugs from previously accepted rtm critical fixes, two not === psivaa_ changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: psivaa | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CI Train on halt! No non-blocker landings accepted until image promotion! [11:01] sil2100: will you send mail on the halts? [11:01] thanks [11:01] or are we happy enough with /topic nowadays [11:01] (could be :)) [11:02] psivaa_, how does ci handle the lock screen? [11:02] psivaa_, does it disable that completely? [11:02] brendand: that's unlocked for every test suites [11:02] reboot and unlock [11:03] psivaa_, ah - and what kind of security is set for it? is it passphrase? [11:04] brendand: i think it's u-d-f --password [11:04] psivaa_, yeah - this is bad [11:04] psivaa_, there is a huge bug ATM caused by that [11:05] psivaa_, it could have an unknown impact on our smoke tests [11:05] brendand: bug caused by using password? [11:05] psivaa_, any chance it can be changed to pin? [11:05] psivaa_, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1373985 [11:05] Ubuntu bug 1373985 in maliit-framework (Ubuntu) "foreground app doesn't get activated after we leave the lock screen" [Undecided,In progress] [11:06] asac: yes, just sent one :) [11:06] psivaa_, it's a maliit bug so doesn't happen with pin [11:07] As mentioned above, it was still in the works [11:07] brendand, davmor2, ToyKeeper, elopio: just so you remember - no landings besides blocker landings o/ [11:07] * sil2100 is still waiting for some info from ogra_ regarding image builds [11:07] brendand: i dont think changing it to pin is difficult, but altering the flashing just to overcome a bug does not seem to be right [11:08] psivaa_, no far better to fix the bug [11:08] i'm sure i'll be asked a lot of questions when i try to do this change :) [11:08] sil2100, this bug is causing smoke testing failures too now - and lot's of functional issues - https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1373985 [11:08] Ubuntu bug 1373985 in maliit-framework (Ubuntu) "foreground app doesn't get activated after we leave the lock screen" [Undecided,In progress] [11:08] sil2100, would be good to have it on the email [11:09] * sil2100 looks [11:18] sil2100, should work again [11:18] sil2100, colin removed the isotracker check for the moment [11:19] === trainguards: RTM IMAGE 138 DONE (finished: 20141030 11:20) === [11:19] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/138.changes === [11:19] see :) [11:20] You don't have permission to access /~ogra/touch-image-stats/rtm/138.changes on this server. [11:20] because it doesnt exist :P [11:20] checking [11:20] heh [11:21] pardon my ignorance - so the train is on halt, does this also affect click on vivid? i.e. I would like to make a new release soon(ish) of click. but the train on halt means that we also stop vivid images, right? [11:22] i would hope vivid is still flowing :) [11:22] but i might be wrong [11:22] what is vivid? [11:22] hmm [11:22] * Wellark hides [11:22] * ogra_ doesnt see 1030 at http://cdimage.ubuntu.com/ubuntu-touch/ubuntu-rtm/14.09/daily-preinstalled/ [11:24] trainguards: I have fix for two top blockers for RTM waiting for a silo and I see plenty of them available for rtm. *wink* *wink* :) [11:24] i wonder if there is more fallout from the inccident :/ [11:24] line 92 [11:25] ogra_: seems we can build images again? [11:25] well done! [11:25] ogra_: which incident? [11:25] asac, well, only partially ... seems the roootfses dont reach the cdimage server ... [11:26] kk [11:26] there is a lot of stuff down atm [11:26] (no idea how that would affect rsyncing the images from nusakan to cdimage though, it shouldnt) [11:26] ogra_,sil2100: for the record I didn't remove it, I just made cdimage carry on if it can't contact the tracker at all [11:27] cjwatson, ah, thanks ... would perhaps be good to have a switch for the future in case you are not around [11:27] ogra_: (a) you could have made the very same change, it didn't particularly require me (b) no need for a switch [11:27] ok [11:29] Hm, I wonder if I didn't quite get it right [11:29] is sync-mirrors using similar checks [11:29] or the wrapping call ... [11:29] Not sync-mirrors, but there's a stage in between I missed [11:31] ogra_: fixed harder, synced mirrors [11:31] thanks :) [11:33] popey, try now [11:33] It's there! [11:33] :) [11:33] and indeed system-image goes off the local filesystem so should have been unaffected [11:33] yeah, only the changelog generation uses cdimage [11:34] i should move that some day ... [11:34] Wellark: you have silo rtm-003. rtm-013 is probably not going to land. [11:34] (like i should move the bot) [11:34] Mirv: not going to land? [11:34] tvoss: ^ [11:34] Mirv: thanks! [11:35] * ogra_ points to Wellark's inbox :) [11:40] Wellark: word back, 013 might land too but it's anyway not yet upstream tested so if you're quick 003 might land first... [11:41] psivaa_, did one krillin (krillin-09) fall over in 138 smooketesting ? [11:41] or is that an older dashboard entry [11:42] oh, seems to be older [11:42] ogra_: so, is the 138 progressing? [11:42] seems like [11:42] i dont see all tests listed yet [11:43] ogra_: yes, it did. let me kick that one again [11:43] Wellark, on rtm-proposed, my sim is not recognized anymore. Is that a known issue? [11:43] did you run out of credit ? [11:43] tvoss: krillin? [11:44] Wellark, ack [11:44] * ogra_ has both sims here (though i'm one image behind) [11:44] ogra_, sim with contract [11:44] ah [11:45] * ogra_ upgrades to 138 [11:45] ogra_, my sim is pin-locked, too [11:45] i have one locked and one open ... [11:45] (open one is prepaid ... the other one is contract) [11:46] tvoss, some people had that issue in mako, but never ran into it with krillin [11:46] tvoss, what does indicator-network show? [11:46] abeato, offline for both sims [11:47] sil2100: it does not look like I'm getting a full UITK AP run.. I've now been running after --bootstrap flashing my mako with latest rtm release, but it simply seems to stop at some point. do you think someone else could test it? maybe krillin, if the results would be easier to obtain than on mako? [11:47] tvoss, ok, could you paste the output of /usr/share/ofono/scripts/list-modems ? [11:47] abeato, Wellark http://pastebin.ubuntu.com/8745974/ [11:48] sil2100: among symptoms I have /lib/systemd/systemd-udevd keeps respawning all the time, while when it "halts" (Unity8 still works, but tests don't proceed) there seems to be a mirscreencast process that doesn't go away (hanged?) [11:48] ogra_: "The Product Team will probably still consider some exceptions" [11:48] if I kill the mirscreencast process (needs -9), I get unity-system-compositor crash and unity8 restarts [11:48] sure [11:49] please considersilos rtm 013 and rtm 003 as exceptions [11:49] tvoss, hm, looks like you were in flight mode [11:49] Wellark, we are not the product team [11:49] tvoss, is that the case? [11:49] wrong channel [11:49] ogra_: who is? [11:49] dude [11:49] the guys that bllock your landings since two weeks :P [11:49] sorry, haven't seen a org chart [11:49] nobody has blocked anything on me [11:49] I only have TOP BLOCKERs ;) [11:49] victor, olli, pmcgowan as announced serveral times over the last two weeks [11:50] well stuff in 013 and 003 fix only top blockers [11:50] so if anyone krillin wants to test UITK, please see silo https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-011 to your sources.list , apt upgrade to it, apt install ubuntu-ui-toolkit-autopilot, and run phablet-test-run [11:50] they decide what goes in ... talk to one of them to get an exception [11:50] doesnt help to moan in here ... [11:51] * ogra_ notes his location indicator is gone on 138 [11:52] tvoss, smells like there still is some race [11:52] ogra_: they are all offline, so where else could I moan ;) [11:52] dis/enabling location in system-settings makes it show up [11:53] + they usually hang out on this channel, so.. [11:53] Wellark, victorp usually comes online around this time ... try #phablet [11:53] ack. [11:54] ogra_: if it is disabled in system-settings and you open a location based app does it show up then? [11:54] davmor2, dunno, i just tied to get the indicator back ... now it is there again [11:55] let me reboot, perhaps i hit the same race again [11:55] it wasnt off or anything ... just the indicator missing [11:56] nope, this time it is there [11:59] * Mirv physiotherapist, and Qt telco immediately after that [11:59] * sil2100 goes off to prepare lunch [12:00] abeato, probably [12:01] tvoss, then just unset flight mode ;) [12:01] abeato, flight mode isn't active in the indicator and urfkill says false for flight mode [12:02] tvoss, using the urfkill script? [12:03] abeato, according to http://pastebin.ubuntu.com/8746071/ [12:03] ok [12:05] tvoss, following in #phablet? [12:06] abeato, sure === chihchun is now known as chihchun_afk [12:29] sil2100, is vivid silo 12 configured correctly https://ci-train.ubuntu.com/job/ubuntu-landing-012-1-build/55/console ? [12:43] brendand, http://paste.ubuntu.com/8746386/ .... (i guess i should one day make a branch of all these tools i use) [12:44] brendand, very interesting: the last mako rtm build had a dropping-letters hang that has systemsettle issues ... the output is pretty informative with that: http://paste.ubuntu.com/8746387/ [12:50] Mirv: shall I upload the camera click now? [12:53] bfiller: according to topic we'd be frozen for blockers only, so my understanding would be that no [12:54] Mirv: ok, I think I'll upload it and then we can wait to approve until deemed open. I was approved for the wishlist anyway.. [12:57] ogra_: on 138 if you slide down the battery indicator do you see auto brightness? [12:57] trainguards, can you please publish vivid silo 9 for me [12:57] davmor2, yep [12:57] trainguards, and reconfigure vivid silo 5, added qtmir there [12:58] then how come I don't sanity test blocker number 2 :( not looking good guys [12:59] davmor2, i think the autobrightness thing is old ... there was a thread about it on ubuntu-hone quite a while ago (two weeks perhaps) [13:02] Saviq: o/ [13:03] ... [13:04] Saviq: ok, so I reconfigured the wrong silo, but well, nevermind that! [13:04] sil2100, should be fine after a watch_only, no? [13:04] Saviq: yeah, let's wait for it to finish reconfiguring, but my brain mixed up the order [13:04] Good thing I didn't publish the other one [13:04] ;) [13:08] hey trainguards, is there a chance that I can get a vivid silo for line 94 (click)? [13:08] mvo_, you have access to the assign function no? ;-) [13:09] bfiller: ok. [13:09] seb128: hmmmmmmm [13:09] seb128: I guess I do === alan_g is now known as alan_g|lunch [13:11] mvo_: ;) [13:12] * mvo_ assigns himself a silo or two === josepht changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: josepht | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CI Train on halt! No non-blocker landings accepted until image promotion! [13:14] https://docs.google.com/a/canonical.com/document/d/14L2Be36VRMQoWvbhguQu4D_lNQlhtmb3oMwbaGsAj2M/edit#heading=h.z2457fdjyl35 [13:14] zbenjamin, Mirv ^^ [13:16] Mirv, is that you? hard to hear [13:17] sil2100, publish 9 please [13:17] pmcgowan: android emulator based [13:18] ribru, olli so, rtm/4, what's next? === karni is now known as karni-lunch [13:23] pmcgowan: ^^ perhaps [13:27] pmcgowan: thanks for the doc [13:27] ogra_, so that looks like an actual bug [13:27] ogra_, whereas the krillin thing is maybe something more fundamental [13:28] brendand, yeah, just wanted to demo how it looks with an actual hanger [13:29] brendand, if i find time on the weekend i'll probably write a parser that pulls all top logs autmatically and generates us a regular report [13:29] (for one image run) [13:30] Saviq: puiblishing! [13:30] Saviq: btw. spreadsheet was b0rked and your silo didn't want to get marked as ready for release [13:30] thostr_, silo 15 doesn't look related to what we discussed? [13:30] sil2100, ^ [13:30] sil2100, b0rkiness! [13:31] sil2100, ah, unapproved, checing [13:31] sil2100, ready agan [13:31] +i [13:32] olli: why 15? [13:32] thostr_, because i can't read [13:32] I guess you said 5 [13:32] oops [13:32] sil2100, ^ [13:32] :) [13:33] thostr_, but how does #5 relate to blank scopes? [13:33] olli: that's the qtmir fix to not suspend dash [13:34] silo 5... I read ubuntu-push-qml [13:34] Saviq, ^ is that possibly #10 [13:34] olli: it's vivid silo 5 [13:35] and rtm silo 13 [13:35] that's the kind of mess... [13:35] olli, thostr_, yes vivid 5 (that's in flux right now) and rtm 13 [13:36] *no* [13:36] rtm 10 [13:36] 13 is just for crashes [13:36] :) [13:36] so, to summarize: rtm 5 and 10 is what we need to make the image stable...hopefully [13:36] no [13:37] f..ck [13:37] lol [13:37] nice... [13:37] that's blank scopes, totally no scopes aka black scopes is something I don't know yet where's it coming from, but both rtm 10 and 13 have potential there [13:37] straightforward as it seems [13:37] Silo 13 is what we need for unity8 crashes [13:37] rtm 10 and 13 that is [13:37] ↑ [13:37] thostr_: what does silo 10 fix? [13:38] sil2100: that's the qtmir things, no? saviq? [13:38] sil2100, yeah, that's me, it's syncing rtm with unity8 trunk [13:38] sil2100, and now's the time when you tell me I can't do that [13:38] and I go to a corner and slit my wrists [13:39] * ogra_ brings a bucket [13:40] this got real dark real fast [13:40] i just want to save the carpet of our chatroom [13:44] sil2100, I'll have to redo vivid silo 5 then to only include changes relevant for rtm blockers [13:44] sil2100, and do a sync silo from that [13:45] * olli hands ogra some episodes of Dexter [13:45] :) [13:49] traingaurds: what do i need to do to actually rebuild the packages in a silo ppa that have already built/published in that ppa? i can't seem to get the train to force new package uploads [13:49] tvoss, is 13 going to be ready for sign off soon? [13:49] dobey, which silo? [13:49] brendand, yup [13:50] Saviq: ubuntu/landing-014 [13:50] brendand: once 13 is in, you might want to champion 3 :) [13:50] brendand: has a fix for this: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419 [13:50] Ubuntu bug 1374419 in indicator-network (Ubuntu RTM) "[TOPBLOCKER] Threading issue with the MenuModel Updates" [Critical,In progress] [13:50] but needs 13 to go in first [13:50] Wellark, i do like 3 (and not just for the gratuitous Symbian reference) [13:51] Wellark, but i think we want to land just the blocker fixes first [13:51] dobey, that's a sync silo [13:51] dobey, once it's built, it's there [13:51] dobey, you'd have to bump version to rebuild [13:52] dobey, why do you need to rebuild it btw? [13:52] brendand, so i went though all systemsettle issues on 137 with my script ... upower clearly keeps dbus busy ... sometimes there is pulse on the list ... i think we shoulld a) raise the threshold a slight bit ... *but* ... have a bug to reaserch why upower keeps the bus so busy ... [13:52] ogra_, let's drag rsalveti in :) [13:52] Saviq: it was built before the new u-d-m landed in vivid, and now that it's in vivid, we need to rebuild against it as it was an abi break [13:52] brendand, i think ondra- did some reasearch of that before [13:53] brendand, and here is the topafter from the unity8 test on krilllin rtm 137 ... this is really interesting http://paste.ubuntu.com/8747221/ [13:53] dobey, then you need to ask a trainguards to bump the ubuntu$ version in there and reupload to force a rebuild [13:54] ogra_, that's our friend unity8 crash no :) [13:54] yeah [13:54] dobey, and then you'll have to sync that bump to your trunk [13:54] the interesting bit is that it keeps media-hub runnint at 100% [13:55] *running [13:55] that is broken :-/ [13:55] which will most likely cause later crashers [13:56] brendand, but this is the only systemsettle where we really have some high consumer ... all the others are just upower dbus noise [13:57] Saviq: why can't the jenkins build job just grab the existing builds through launchpad api, and do retry() on them? [13:57] so i think we are good for adjusting the test as long as we keep an eye on that bit [13:57] (and if we find something ... lower tthe test value again) [13:57] dobey, because they're not failed? [13:58] dobey, and you can't have two binary packages with the same version in any ubuntu archive [13:58] sil2100, see backlog of the last ten mins (about systemsettle) [13:58] dobey, there's no "overwriting" packages [13:58] ogra_: doing in a moment [13:58] take your time, not urgent :) [14:00] * sil2100 has a meeting now so it might take a moment [14:00] ;) [14:03] * Mirv back from meeting [14:04] === trainguards: IMAGE 299 building (started: 20141030 14:05) === [14:04] maybe we should just cheat here, since u-d-m cheated too [14:04] davmor2: brendand: do you have any krillin free time to test (UITK AP only) the rtm-011? [14:05] davmor2: brendand: on mako I'm not getting them to finish, even if unity8 would not crash. seems a possible Mir(screencast) issue or such. [14:05] ogra_, sergiusens: should we just copy+rebuild unity-scope-click from rtm -> vivid directly, since ubuntu-download-manager was done that way? [14:05] Mirv: nope I'm testing on mine [14:05] uh [14:05] ignore the imgbot [14:05] * ogra_ is switching it over to vivid [14:06] davmor2: ok [14:06] Mirv, can you publish vivid silo 9 for me please [14:07] Saviq: yes [14:07] Mirv, maybe - just double checking a few things for davmor2 [14:09] brendand: ok, thanks for trying. I'll experiment with UITK testing with ro image, but I guess that's not possible since we don't have autopilot on the image anymore. [14:10] Mirv, thanks! [14:12] dobey, is unity-scope-click newer inr rtm than it was in utopic ? [14:13] ogra_: yes [14:13] if it doesnt have a ~rtm version string etc that should be doable then [14:13]