=== balloons is now known as Guest87130 [06:40] trainguards: hi, what's the status of silo 53? I don't understand the comment. [06:41] jgdx: your silo is not configured to publish to the overlay ppa, so when you published it, it got sent to real live vivid as an SRU, where somebody has already rejected it. [06:42] robru, how do I configure it to land in vivid+overlay and not wily? [06:42] jgdx: ^ what the night-shifter said [06:42] jgdx: you need to use the PPA field [06:42] jgdx: it's not configured to land in wily. you need to set the destination PPA field to the overlay, which is offered as a drop down if you click in it [06:43] ah [06:43] jgdx: and add ci-train-ppa-service/ubuntu/stable-phone-overlay there [06:44] Mirv, robru: great, thank you [06:44] jgdx: you're welcome [06:46] Mirv, are there any more steps I need to take? [07:11] jgdx: it should be ok to re-publish now [07:11] I can try that [07:12] Mirv, ty [07:12] jgdx: ok, it's there https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?batch=75&memo=150&start=150 - note that it happened despite the error reported [07:12] right [07:13] robru: one more error-while-actually-publishing-completed ^ (possibly due to it previously having been published) [07:13] Mirv: nope, jsondecodeerror means "failed to get a response from launchpad" [07:14] jibel: ping [07:14] robru: aha, right so it tries to decode an empty value or something [07:15] Yeah [07:15] Mirv: either a launchpad issue or network issue [07:15] Mirv: just lucky that LP got the request to do the copy and did it [07:16] ok [07:17] Mirv: https://requests.ci-train.staging.ubuntu.com/ btw, I'm starting to get excited about this ;-) [07:21] robru: wow! I think the readibility/parseability will improve a lot. [07:22] Mirv: thanks, yeah i really had an eye for mobile use this time, and also eliminating the possibility of clicking on the wrong request by mistake ;-) [07:35] Mirv: do you know who is the earliest bird from the QA flock? [07:39] davmor2: rvr: ping [07:40] bzoltan_: within 50 mins both dav_mor and ji_bel [07:40] since there's a hangout at that time [07:44] Mirv: thanks... we need to pull up the QA validation of the silo31... the OTA7 closes tomorrow and we have 3 OTA7 bugfixes in the silo31 [07:53] robru, slight suggestion on the visuals: https://gist.github.com/semafor/263e90d20c8136218075 [07:54] jgdx: let me try that, thanks [07:56] jgdx: is that supposed to be in addition to what's already there? or are you saying I should take the fixed width off .card? [07:56] robru, just an addition. If you have FF, just go to style editor and paste it in. Actually, use this instead if you wanna check it out https://gist.github.com/semafor/263e90d20c8136218075 [07:57] jgdx: wrong link? I just see a code listing, nothing to "try out" [07:58] okay [07:58] yeah there's a manual step in there (Firefox -> Style editor -> paste code) [07:58] jgdx: what's "silo n" about? [07:59] robru, it's a silo title [08:01] jgdx: hm, not fond of the lines, too many lines. [08:01] jgdx: also in my experience mobile browsers struggle with rounded corners (at least on android they get drawn wrong with weird artifacts) [08:02] robru, hey, any idea why the duplicated MP at the end in the description https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-022 ? [08:04] Saviq: uh [08:05] robru, I don't think they do, but that's fine. [08:05] Saviq: was it duplicated before and you edited it out of the request? I'm not aware of anything that would result in duplicated merges in the merge list [08:06] jgdx: I see it a lot at least on my android, weird 1px gaps between elements that should be flush, etc. [08:06] robru, I found it very hard to scan the information right now. Right aligned | left aligned tabular data is … uncommon [08:06] jgdx: hard to scan how? I really like the right|left aligned stuff since it gives a nice solid line down the middle for it to wrap around. you don't really need to "scan" the right-aligned stuff [08:07] it's the left-aligned stuff that has the actual info you care about. [08:07] jgdx: it's not really "tabular data" it's just a list of info that happens to have right-aligned labels. [08:09] robru, nope, the build job must've duped it somehow (not sure if it tries to merge it twice... checking... yes) [08:09] robru, okay [08:09] Saviq: does it cause an actual problem? or does it just go "trying to merge... nothing to do"? [08:09] robru, nothing to do [08:10] Saviq: ok, harmless. file a bug against lp:cupstream2distro and include your MP list please. I'll try to reproduce later. bizarre [08:10] tx [08:12] robru, bug #1502793 [08:12] bug 1502793 in CI Train [cu2d] "Build job duplicates MPs" [Undecided,New] https://launchpad.net/bugs/1502793 [08:12] Saviq: thanks [08:15] jgdx: I am open to suggestions but I think we need to compromise somehow, I found the lines in yours a bit cluttered visually. not sure if there's a sensible way to keep it easy to read without the lines [08:16] jgdx: I wonder eg if the labels are even really necessary in the index view (they would be in the detail view of course). [08:17] jgdx: tell me what you think of this ;-) https://www.irccloud.com/pastebin/hNrxLSBe/ [08:18] jgdx: or maybe this ;-) https://www.irccloud.com/pastebin/mj2QcM2M/ [08:21] robru, I think that reduces the clutter significantly, but relying on whitespace for visual separation between the requests is still too straining on the eye. Hence the borders, but I also agree that there were too many in my sugg. [08:22] imagine github.com/foo/bar without borders, for instance. Your eye would have to do a job to digest all the information. [08:23] Mirv: the silo14 is rady with the new package [08:23] robru, and you say you "should not do this and this", but it's not a fully conscious process, looking at a web page. [08:28] jgdx: one small border https://www.irccloud.com/pastebin/veqw66D5/ [08:29] robru, ok something's wrong here https://ci-train.ubuntu.com/job/ubuntu-landing-022-1-build/173/console [08:30] robru, it's complaining about a superseded MP that's no longer in my MP list https://requests.ci-train.ubuntu.com/#/ticket/445 [08:30] Saviq: yeah your merge is superceded [08:30] robru, yeah, except that superseded MP isn't there in the list any more [08:30] Saviq: that's the one you were just complaining was a duplicate. [08:30] likely [08:30] d'oh [08:30] robru, I take that back [08:31] robru, my fault [08:31] robru, kick ass! [08:31] jgdx: thanks [08:31] Saviq: oh so it was in there twice all along? [08:31] robru, yes [08:32] * Saviq invalidates the bug [08:32] Saviq: funny I didn't see it. but that's good news ;-) [08:32] jgdx: ok will commit that [08:32] robru, it's because it's sorted in the job log [08:33] Saviq: right, the job log sorts it alphabetically while the merge-order sorts it topologically ;-) [08:33] yup [08:33] I could probably stand to make that less inconsistent... [08:35] bzoltan_: it's currently marked as being a vivid-only SRU [08:35] Mirv: is that a problem? [08:35] bzoltan_: well if you want SRU you should have a bug and follow https://wiki.ubuntu.com/StableReleaseUpdates [08:35] Mirv: i need that package in the 15.04 chroots ... [08:35] bzoltan_: not otherwise [08:36] Mirv: I do not need it in the main 15.04 ... Overlay PPA is enough, as I am planning to push a click update to the SDK PPA what will create 15.04 + Overlay PPA chroots instead of the clean 15.04 chroots [08:40] bzoltan_: ok if you want overlay then you'll want to fill in the PPA field [08:41] Mirv: okey, just did thatű [08:56] jgdx: ok it's live: https://requests.ci-train.staging.ubuntu.com/ and it's now 2AM, goodnight ;-) [08:56] Mirv: ^ [08:56] Mirv: crap ... yet again the versioning trap - ubuntu-sdk-qmake-extras_3.5.1+15.04.20151005.1-0~7~ubuntu15.04.1.dsc: Version older than that in the archive. 3.5.1+15.04.20151005.1-0~7~ubuntu15.04.1 <= 3.5.1+15.10.20150928-0~5~ubuntu15.04.1 [08:56] robru, cool :) Good job! Gnite [08:57] robru: good job and good night! [08:57] night! [08:57] zbenjamin: would it be OK to bump the qmake extras from 3.5.1+15.04.20151005.1-0~7~ubuntu15.10.1 to 3.5.2? [08:57] bzoltan_: well at least you got your first vivid landing done. [08:58] bzoltan_: what? no don't bump the version [08:58] robru: I am open for better solution [08:58] bzoltan_: this problem is vivid/wily version in the version number, you need to branch your trunk and change 15.10 to 15.04. [08:59] bzoltan_: if you bump the version number then your changelog will read "3.5.1...wily" followed by "3.5.2...vivid" it's backwards. [08:59] bzoltan_: not to mention vivid will have a higher version than wily, it's a very wrong thing to do [09:00] Mirv: hopefully you can explain it properly I really have to go ^ [09:01] robru: it is a little bit more compllicated but i will explain it to Mirv [09:02] Mirv: what we do here is ripping off the qmake-extras package from the qtcreator-plugin-ubuntu source tree... so it is a binary package what has now a different source [09:02] bzoltan_: oh, sorry just saw it said archive, I thought this was the "build wily trunk in vivid" issue that always comes up. maybe bumping is the right way to go if vivid really has v3.5.1+15.10 in it [09:02] anyway goodnight [09:02] robru: have a good rest [09:02] thanks [09:06] cihelp: any idea why this merge which was approved 13 hours ago hasn't merged yet? https://code.launchpad.net/~ahayzen/ubuntu-weather-app/transparent-legacy-listitems/+merge/272818 [09:07] popey: let me take a look [09:07] thanks psivaa [09:17] bzoltan_: yeah I know what your plan is, even though I don't know how you're planning to execute on it (I thought at one point you actually do want full SRU:s) [09:18] bzoltan_: on PPA level things don't explode even if two sources provide the same binary - the newer one gets installed [09:27] bzoltan_: you pinged sorry issue on my mail server only just got the message :) Did rvr get back to you already? [09:29] rvr, hey, what's the story on bug 1502223? Was it found in QA or was it found in rc-proposed r129? [09:29] bug 1502223 in ubuntu-system-settings (Ubuntu) "Delay in opening system-settings from indicators" [Undecided,New] https://launchpad.net/bugs/1502223 [09:29] s/QA/silo 41 [09:30] jgdx: I found it while testing a silo, but it's in the image as well [09:31] hmmm, the nightly builds failed [09:42] ubuntu-qa: is there an ETA for validation of silo 31 ? [09:42] * sil2100 looks into that [09:43] oSoMoN: I could prepare your silo so that it temporarily builds with silo 31 so your landing can be ready when the UITK lands [09:44] oSoMoN: I'm on it [09:44] Mirv, that’d be great, if you don’t mind [09:44] davmor2: ping back about what? [09:44] Looks like the buteo landing broke stuff... [09:47] oSoMoN: ok, you can hit a rebuild now [09:48] rvr: bzoltan_ pinged about 20 minutes before I got online [09:48] Mirv, thanks! [09:53] popey: the slave that run those tests are down, I'll try and resurrect them, but I suspect that those are under fginther's account pending migration, so it could be that we'd need to wait for fginther [09:53] I mean those landings [09:53] psivaa: hm, okay, thanks. [09:54] sil2100: should I be concerned by the fact that I have done the ota test and see no buteo on the system [09:55] davmor2: rvr: Sorry, I just had a lunch :) So.. my issue is that i would like to pass by the queue for QA validation of the UITK [09:55] davmor2: rvr: I have 3 super critical OTA bugfixes in that silo and it fixes the problem why my previous landing was reverted. [09:56] davmor2: rvr: The last landing did not check mako .. and due to hiding driver bug on mako the latest UITK was crashing [09:56] rvr: ^ is that something you tested? [09:56] davmor2: yes, the images failed to build [09:56] Looks like a seed conflict... or a dep problem [09:56] Investigating it now [09:56] Really unfortunate this landed so late on Friday [09:57] sil2100: well that was a waste of time then :( [09:59] sil2100, there is no image this morning? [09:59] jibel: no, see above [09:59] Build failue [09:59] *failure [09:59] sil2100, ah sorry, thanks [09:59] Investigating it [10:00] hmmm [10:01] Oh craaap [10:02] ? [10:02] sil2100: what did you do???? [10:02] Me, nothing - the train screw up! [10:02] * sil2100 sighs [10:02] Yeah, so it seems it didn't copy sync-monitor from silo 34 [10:02] It said it did, but didn't [10:03] * davmor2 blames sil2100 and friday night at beer o'clock ;) [10:03] Need to publish it now in some sneaky way [10:07] Phew, good thing LP is smart [10:10] popey: i've just created a card for this: https://trello.com/c/i5qBlrme/650-vanguard-lp-ubuntu-weather-app-reboot-mp-hasn-t-landed-for-14-hrs. will keep track of it [10:14] davmor2, jibel: I'll kick a new image instantly once the sync-monitor gets published in the PPA [10:14] sil2100: thanks [10:15] Ok, looks good on my chroot, kicking the new image [10:20] rvr: thanks for taking the UITK, please ping me if you need any help [10:21] bzoltan_: I'll check it in mako [10:21] rvr: :) cool [10:21] Mirv, hey, would you mind retrying the failed builds in silo 59? [10:22] thanks psivaa [10:25] davmor2, jibel: new image building [10:26] oSoMoN_: on it [10:26] thanks === oSoMoN_ is now known as oSoMoN [10:31] bzoltan_: bump it as much as you want ;) [10:31] zbenjamin: it is landed already :) [10:35] brb need to reboot [10:41] bzoltan_: I'm flashing mako... how did you overcome the restarts? [10:43] rvr: it was loicm and timp who put together a workaround: https://code.launchpad.net/~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit-adreno-320-shader-compiler-workaround/+merge/273262 [10:44] bzoltan_: I mean, how can I install the packages when the phone keeps rebooting [10:44] bzoltan_: [10:44] Did you use a previous image to test? [10:45] rvr: 'stop unity8' worked for me [10:45] rvr: it seems yes... my mako is notrebooting ... what channel you use for mako? [10:45] timp: Thanks, I'll try that [10:45] bzoltan_: rc-proposed/ubuntu [10:45] rvr: I followed gerry's comment #6 from https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502093 for testing [10:45] Ubuntu bug 1502093 in ubuntu-ui-toolkit (Ubuntu) "UbuntuShape crash with latest UITK on mako/flo" [Critical,Fix committed] [10:46] timp: Ack === chihchun is now known as chihchun_afk [11:01] Ah, nice, in latest image the reboot was reverted [11:44] sil how we looking? [11:45] sil2100: ^ even [11:55] It's built it seems! [11:56] jgdx: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502872 [11:56] Ubuntu bug 1502872 in ubuntu-system-settings (Ubuntu) "Title bar empty in System Settings" [Undecided,New] [11:57] rvr, that sound page is a … hive [11:58] jgdx: That status is kept opening other pages, restarting system settings gets the title bar back [12:03] jibel, sil2100: My interwebz are down for some "Fixing" should be back up in a couple of hours, I need to go get some train tickets anyway so I'll have lunch and get them and see if I'm back up then if not I'll use my mifi, but I won't be in many channels I fear :( [12:04] davmor2: ok... the image has built if anything :) === alan_g is now known as alan_g|lunch [12:07] davmor2, ok [12:10] rvr, the new buteo sync will need some translations if it ever lands [12:10] jibel: o_O [12:10] jibel: Another freeze that melts? ;) [12:11] rvr, for example the notification is untranslated [12:11] jibel: We can issue an urgent call [12:11] jibel: Do you know the amount of work? [12:11] rvr, no idea, there is at least one string, but since it is not yet in the archive the strings are probably not available for translation [12:12] rvr, “hot” or “cold” start of USS? I.e. do I kill USS before trying to reproduce those two bugs? [12:12] jgdx: What do you mean with hot or cold start? [12:12] jgdx: I opened system settings from the indicators [12:13] rvr, hot=app already running, cold=app killed [12:22] jgdx: cold [12:23] rvr, okay, thanks. I reprod' bug 1502223. Thanks for the report. [12:23] bug 1502223 in ubuntu-system-settings (Ubuntu) "Delay in opening system-settings from indicators" [Undecided,Confirmed] https://launchpad.net/bugs/1502223 === _salem is now known as salem_ [12:42] sil2100: hey, any reason why when the branches are merged upstream, the related upstream bugs aren't marked as Fix Committed automatically? This happened in the past (when we had autolander), not anymore :( [12:44] Laney: also did you see that in my friday (deep) night I found the reason why d-feet icon wasn't scaled properly? [12:44] and that icon is almost squared... (not a square for a couple fo pixels) [12:45] Trevinho: I did see! [12:45] nice one [12:45] the classic issue you spend hours to figure where it is, and then it's just one-line fix -_- [12:46] yeah, then it doesn't look like you did much work :) [12:46] look at this slacker, changing two lines of code per day [12:48] Trevinho: is that for the Ubuntu projects? [12:49] Laney: yeah :P, totally [12:50] sil2100: well, unity tracks bugs in both Ubuntu and as upstream project [12:50] and they're independent [12:50] so... When a branch merges, I'd like even the upstream tasks to be marked as Fix Committed [12:51] (of course if merging with trunk, and the bug task matches that) [12:59] davmor2_: you're running buteo related tests on silo 034. the silo was already published on Friday by kenvandine and the silo currently has some Unity 8 landing. [12:59] All buteo stuff is now in the overlay [13:00] (since it was missing one package before) [13:00] sil2100: but the trello card is "Under Testing" ... [13:00] and davmor2_ has updated it 4h ago [13:01] bzoltan_: Approving silo 31 [13:03] Mirv: yeah, I think davmor2_ knows it's already landed, but he wants to do real tests on a real image still [13:03] (I think) [13:03] sil2100: ok, sounds good [13:04] now who'd be the friendly core-dev of the day to push button on https://ci-train.ubuntu.com/job/ubuntu-landing-031-2-publish/ ... [13:04] sil2100: what's the status on getting ota number in image? is there a file where system-settings can read it from? [13:05] rvr: \o/ [13:05] bfiller: there's a remote file right now, we don't have any solid solution on how to get it on the image - we have a proposition, but I think it needs to be consulted with barry once he's around [13:05] Mirv: specially that the debian/ changes were approved on the previous landing what was reverted :) [13:05] Since he's the main system-image client maintainer [13:06] seb128: could you help with this please? https://ci-train.ubuntu.com/job/ubuntu-landing-031-2-publish/ [13:07] sil2100: ok, even if it's hardcoded in system-image-cli for now at least there would be a consistent place u-s-s could read it from [13:07] jgdx: ^^^ [13:07] We can't pre-install it on the rootfs though [13:07] jgdx: rather it be hardcoded in some known config file than in u-s-s [13:07] until it's dynamic [13:07] One idea would be to get it downloaded from a remote URL along with the image update itself [13:08] That would be relatively safe and flexible [13:08] But I don't know how much work that would require [13:08] bzoltan_, Mirv, done [13:08] oh, it's failing [13:09] bah, my fault for not checking the box [13:09] done this time [13:09] sil2100, by s-i? [13:09] thanks seb128 [13:09] yw! [13:10] jgdx: I guess... [13:10] sil2100: should I open a bug for that thing? [13:10] But as I said, I don't know much about the s-i client, I'm only working on the server bits [13:10] Trevinho: I suppose, but I saw it was working for other projects I think? [13:11] Trevinho: if you could provide some examples it would be great [13:11] sil2100: never saw it in unity in the past year (?) === alan_g|lunch is now known as alan_g [13:11] jibel: i'm releasing oxide 1.9.5 for qa testing, btw ^^ [13:11] hm, or maybe not, since it's about the 'Fix Commited' state, right? [13:12] sil2100: what project should be that targeted to, nowadays? [13:12] Trevinho: cupstream2distro :) [13:12] sil2100: thanks [13:12] sil2100, can the server read the json you made and use that to properly generate the channel index.json file? [13:16] dbarth, great! [13:16] rvr, davmor2_ silo 16 is next on the list [13:37] rvr, I'm afraid that the "no title" bug you see in USS comes from silo 31 [13:38] sil2100, ^ did it land? [13:38] latest uitk [13:39] bzoltan_, it seems that bug 1502872 [13:39] bug 1502872 in ubuntu-system-settings (Ubuntu) "Title bar empty in System Settings" [Undecided,New] https://launchpad.net/bugs/1502872 [13:39] has been introduced by silo 31 [13:39] Looks that it landed on Friday [13:40] sil2100, I mean what rvr reverified today [13:40] jibel: sil2100: The silo31 was just tested by rvr [13:41] bzoltan_, right and I can reproduce his bug with this silo [13:41] Yeah, it's in [13:41] sil2100: jibel: I am not sure if I understand it... [13:41] sil2100, that's the upload that has been reverted because it crashed mako and that we are trying to reland [13:46] sil2100: jibel: I am check it out ... but it feels a bit confusing. I would alert kenvandine as my folks are out for a Qt event right now [13:46] bzoltan_, Friday's upload has been reverted to 1.3.1658+15.04.20151001.is.1.3.1641+15.04.20150922-0ubuntu1 and now we are verifying 1.3.1672+15.04.20151002.1-0ubuntu1 but it introduces bug 1502872 apparently [13:46] bug 1502872 in ubuntu-system-settings (Ubuntu) "Title bar empty in System Settings" [Undecided,New] https://launchpad.net/bugs/1502872 [13:46] j [13:47] sil2100, bzoltan_ jibel, ken is out this week [13:47] jibel: guys, you are a bit too trigger happy === davmor2_ is now known as davmor2 [13:48] jibel: sil2100: should not we check if System Settings should be fixed ? [13:48] that might be simpler [13:49] jibel: Ah, you reproduced it with the silo [13:51] rvr: jibel: Guys, please take it easy :) the silo31 is empty since it is landed... and you reverted the Overlay PPA... so with what package should I test and find a solution? [13:53] jgdx, ^^ maybe you can also look [13:54] bzoltan_: Installing image 141 without the silo [13:54] bzoltan_: jibel couldn't reproduce the issue without it [13:54] bzoltan_, test with [13:54] qtdeclarative5-ubuntu-ui-toolkit-plugin: [13:54] Installed: 1.3.1672+15.04.20151002.1-0ubuntu1 [13:54] -- [13:55] ubuntu-ui-toolkit-theme: [13:55] Installed: 1.3.1672+15.04.20151002.1-0ubuntu1 [13:55] But I already saw this problem on Friday, although it was hard to reproduce [13:55] bzoltan_, open USS and go to sound settings [13:56] rvr, maybe you reproduced before the revert [13:56] It may be also 41 [13:56] jibel: do not that app have AP tests to cover these cases? [13:57] Hmm [13:59] jibel: rvr: it does not happen with other System Setting headers... [13:59] wifi it happnes, cellular/bluetooth not [14:00] brightness busted too === karni_ is now known as karni [14:01] bzoltan_: When system settings is in that state, I have to restart it to get the headers back [14:02] rvr: yes, I see... [14:02] rvr: sound, wifi, brightness settings are busted, other work. I am positive that the System Settings does something nasty there... [14:07] rvr: jibel: sil2100: the Ubuntu System Settings app is using 0.1 UITK ... it is archeology in action [14:07] jgdx, ^ [14:07] Maybe seb128 or jgdx could help? ^ [14:09] bzoltan_, sil2100, is there a practical issue? [14:09] uitk should keep working [14:09] we have an 1.3 branch but we didn't land it because there was disagreement on how stable 1.3 is and on it breaking compat and apps in the store [14:10] seb128: well... if you ask me... it is waaaay much safer to use 1.3 then the historical 0.1 [14:11] bzoltan_, why? I though we have those versions so the code would be compatible and not break existing apps? [14:11] seb128: I would not start academical argument about that :) Let's simple agree on the fact that bugs do exist and 1.3 is certainly more fixed then 0.1 [14:12] bzoltan_, anyway, is there a pratical issue/real problem [14:12] or is that arguing for the sake of arguing? [14:13] seb128: :D no way... I am figuring out about that issue [14:13] seb128: the Sound/Wifi/Brightness pages are busted by the rev1672 UITK... the hedaer text is not visible. All other headers are fine [14:14] bzoltan_, does bumping the import version fix it? [14:14] seb128: no idea yet.. just about to figure out [14:14] k, let me know [14:14] seb128: But I assume that it isnot about the version but about how the header/page is used [14:15] bzoltan_, well, it's used in a way that used to work ;-) [14:16] pete-woods1: ping :) [14:19] seb128: chaning 0.1 to 1.2 in SoundPage does not help... [14:20] k [14:43] charles: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502926 [14:43] Ubuntu bug 1502926 in indicator-transfer (Ubuntu) "Indicator title not translated" [High,New] [14:43] charles: This is new [15:46] cihelp: are we still having problems with AP on mako devices ? it seems that a lot of stuff fails in the AP tests here https://code.launchpad.net/~uriboni/webbrowser-app/topsite-previews/+merge/269771 but i find it hard to believe it is related to my changes [15:47] cihelp: especially the settle_before and settle_after failures [15:48] nerochiaro: we're all in a meeting at the moment, we'll try to take a look at them, once the meeting is over [15:48] psivaa: no rush [15:48] psivaa: and thanks [15:51] seb128: hey! If you have a moment, I'm looking for a core-dev to publish https://ci-train.ubuntu.com/job/ubuntu-landing-041-2-publish/19/console <- it's a FTBFS from the wily test-rebuild [15:51] s/FTBFS/FTBFS fix/ [15:56] seb128: strange that this system settings issue is with those pages that are hooked up to the indicator [15:56] bzoltan_, I doubt it has anything to do with indicators, maybe just when a subpanel is directly open? [15:57] bzoltan_, I would test but seems since dual landing stopped pushing to wily I don't have the buggy uitk version... [15:57] seb128: not sure ... but sound-wifi-bluetooth-brightness ar ethe four settings available from indicator [15:57] sil2100, disabling tests rather than fixing them seems wrong [15:57] seb128: the SDK Staging PPA has it [15:58] bzoltan_, well, if you start "system-settings sound" you likely get the same issue [15:58] bzoltan_, or try "system-settings background" [15:58] seb128: it's not disabling tests [15:58] seb128: tests are still running [15:58] sil2100, well the valgrind check at least? [15:58] seb128: it's just that we're not explicitly using valgrind when running them as Qt has some internal issues reported by valgrind [15:59] well, fix qt and valgrind is happy again [15:59] seb128: multiple people report false-positives [15:59] hum, k, I'm not going to right over this one [15:59] but it seems wrong [15:59] since pete-woods approved it let's land [16:00] that codebase is not used nowadays anyway, right? [16:00] seb128: no, not really, and as mentioned it's not an issue in the application itself [16:00] right [16:00] ok, publish button clicked [16:00] Thanks! [16:00] yw! [16:02] seb128: ubuntu-app-launch ubuntu-system-settings hotspot just works [16:03] weird [16:05] grrrr [16:05] f** the request website [16:05] when I paste something in test plan the merge proposal entry empty itself [16:06] and vice-versa [16:06] jibel, I've just marked silo 28 ready for QA (contains a better fix for lp #1496894) [16:06] Launchpad bug 1496894 in Canonical System Image "media-hub-service leaking 2 FDs for every text/phone call" [Critical,Fix committed] https://launchpad.net/bugs/1496894 [16:06] jhodapp, ^^ [16:07] jibel, it has my approval [16:08] alecu: awe_: could you fill in a test plan for the silo request ^ ? [16:09] do we have one? [16:09] * cyphermox also curious how much QA you want on it [16:09] AFAIK no such plans exists [16:09] I don't know that we do, no [16:09] still, what better time to define one? [16:09] I think what we need is a specific test case for the change being mae [16:09] s/mae/made/ [16:10] basically, figure out a way to force a phone into the state where a reboot loop would occur [16:10] then test with the changes watchdog jobs [16:10] and confirm that the boots happen at the new interval [16:11] awe_, cyphermox davmor2 knows how to test it [16:11] as does dobey [16:12] can one of them add the details to the silo 'Test Plan;' then? [16:12] pmcgowan: jibel added a comment onthe bug too I think [16:16] awe_: yes [16:22] ubuntu-qa: why is ticket 444 marked "next milestone" ? it’s for ota7 [16:22] oSoMoN: because the bug say ota8 [16:23] davmor2, darn, that must be a mistake, let me check [16:23] pmcgowan, can bug #1356516 be re-targetted for ota7 ? [16:23] bug 1356516 in webbrowser-app (Ubuntu) "consider shipping apparmor profile for webbrowser-app" [Critical,In progress] https://launchpad.net/bugs/1356516 [16:24] oSoMoN, sure [16:24] thanks [16:43] awe_: the main problem i had with forcing the phone into a state where a reboot loop could occur, is apport kept getting re-enabled, and it would cause the service restarts to be just slow enough to not trigger the watchdog (which is probably also what was killing performance in the first place) [16:44] dobey, ack [16:45] davmor2, do you have the secret sauce on how to test? [16:45] anyway, i updated the test plan portion of the request to document basically what i did. [17:00] barry: ping :) [17:01] barry: hey! Two things: did jgdx poke you earlier about the s-i client OTA numbering concept? [17:02] barry: and second! https://bugs.launchpad.net/debian/+source/wheel/+bug/1502941 <- is it still ok to sync a package to wily, or should we somehow work-around this FTBFS in wily for now? [17:03] Ubuntu bug 1502941 in wheel (Ubuntu) "FTBFS on amd64 due to pytest.py error" [Undecided,In progress] [17:03] barry: I suppose we could force using unittest discover on amd64 as well somehow? === alan_g is now known as alan_g|EOD [17:22] robru: request 471 on silo, when I press assign it says it's already created silo-19 but that doesn't seem to show up on the page [17:22] at least I don't see it === DanChapman_ is now known as DanChapman [17:37] bfiller: looking [17:39] bfiller: this assignment you ran worked: https://ci-train.ubuntu.com/job/prepare-silo/6296/console [17:39] bfiller: not sure why it didn't show up in the request [17:40] bfiller: anyway this is like the third or fourth time this happens so it's clear now that "assign already assigned request" should not be an error but should instead set the requestid and say "success! I found your existing assignment!" [17:40] bfiller: fixed it for you manually for now though [17:41] robru: thanks [17:41] you're welcome [17:54] slangasek: so sil2100 can't make the meeting, do you want to sync with just me? or should we cancel? [18:09] pmcgowan, looked at it, couldn't repro. Guess I need the silo [18:09] barry, could you /cc me in any response to sil2100's ping? Thanks :) [18:13] jgdx, the sdk guys and seb made some progress [18:32] jgdx: The Staging PPA of our team has the version what can reproduce it [18:32] https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/staging/+packages [18:42] bzoltan_, I just saw it now in silo 49, rc proposed. “WARNING - file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.2/MainView.qml:188: TypeError: Cannot read property '__tabBar' of null” [18:43] seems I got a uitk deb at silo install: 1.3.1672+15.04.20151002.1-0ubuntu1 [18:46] brightness, wifi and sound [19:14] popey, the core-apps jenkins (http://91.189.93.70:8080/) issue has been fixed. MPs are being processed again. [19:18] thanks fginther [19:26] jgdx: Yes, that is the problem we are tacking [19:30] bzoltan_, rog [19:34] jgdx: it would worth a try to see this MR in action https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/1_3_deprecations/+merge/268090 [19:39] bzoltan_, that was blocked for some reason, I can't remember why. [19:41] jgdx: it was blocked by ken because he was affraid to use 1.3 as he thought that it is risky ... well, it is not :) or not more then using mixed 0.1-1.0-1.1-1.2 imports all over [19:46] bzoltan_, okay, we should document that. Sure, we can change it quickly for USS, but what about app developers? [19:47] would be bad if app headers started going blank :| [19:50] bzoltan_, I dont think we can fix it in just settings as jgdx says other apps could break [19:50] do we understand the root cause [19:51] pmcgowan: the question is what I can not yet answer if it is the settings app what is doing something illegal or not... mixing archeology imports is surely something what we do not suggest. [19:52] bzoltan_, but what changed with the latest landing to cause the symptom [19:52] bzoltan_, or was it other landings than uitk that caused it? [19:54] pmcgowan: Most probably it is the refactoring of the header component what uncovered something what the settings app should not have used [19:54] pmcgowan: so it is the UITK's fault.... no question. [19:54] pmcgowan: I think it is the version separation what causes that [19:55] bzoltan_, ah, the header has multiple implementations for the versions now? [20:07] jgdx: i do remember chatting about this, but i thought i'd given the answer: you guys figure out what numbering system you want to use, we add that to the server side generation, and the clients get that through the si .Information() dbus api [20:08] pmcgowan: Yes, the older/stable versions are frozen [20:09] bzoltan_, was asking what "version separation" meant [20:11] pmcgowan: version separation means that there is no cross reference and cross importing betwen 1.2 and 1.3 for example .. so theming and other features do not mix. [20:11] pmcgowan: but I sense here a bug... so i am affraid that the new hedaer implementation could have leaked someting to the 0.1 space ... and that could cause problems. [20:12] bzoltan_, ok lets take the time to understand then [20:12] I will figure it out tomorrow morning.. [20:12] good [20:17] barry, so the system is more like an employee doing this manually. And the format is an arbitrary string (OTA-7, OTE-9). [20:17] over-the-ether update 9 [20:19] jgdx: seems like there might be a scaling problem, but i guess if it doesn't happen to often, it's not a big deal. and anyway *i* don't have the needed access on the server so it's not *my* scaling problem :) the information only needs to get into the channel.ini file (for si 2.5) or an /etc/config.d/*.ini file (probably 01_channel.ini) [20:24] barry, right. Łukasz proposed either to include it in the rootfs, but deemed that too invasive; or to have s-i download a json file with this information in it. You're saying we should do the former? [20:25] barry, what if we signed a file, e.g. http://people.canonical.com/~platform/touch/ota-bindings.json — could s-i download it for us? [20:25] jgdx: how would the server code know which json file to download? [20:25] oh i see [20:26] i suppose that could work, though tbh it seems like that should really go in the server config somewhere. the only reason it wouldn't is because too few people have access to the server and presumably more would be able to update that mapping. [20:28] hm, i see. [20:30] bfiller, ^^ we have to choose: 1) change the server, 2) have s-i download the file, 3) let system settings deal with it [20:30] (the file being this json http://people.canonical.com/~platform/touch/ota-bindings.json ) [20:31] jgdx: ftr, i do not want the si-client to have to download anything that doesn't come from system-image.ubuntu.com, and i also do not want it to have to download another file. it should all be done on the server when a new image is published, and vended through the si client using the existing bits [20:31] Jgdx: System settings should be reading from a file and that file needs to get updated automatically somehow [20:31] bfiller, or read from the Information dbus endpoint, which is alternative 1) [20:32] barry, that's what I figured when I looked at the s-i code (which is neat btw) [20:34] jgdx: thanks! [22:31] kyrofa: let me know if you need help with this ^ === ljp is now known as lpotter [23:28] robru: after I press "Create new request" not seeing how I enter the info on new site? [23:29] bfiller: uh? giant form should fill the screen [23:29] robru: just seeing blank space with no fields to fill in [23:30] bfiller: are you logged in? try reloading the page? send me a screenshot [23:30] robru: I am logged in, let me send you a screenshot [23:30] using chrome [23:30] bfiller: oh god I didn't test in chrome [23:31] robru: will try ff [23:32] bfiller: form shows fine for me in chromium [23:32] robru: just sent you screenshot [23:33] bfiller: oh it looks like you have cached HTML or something, try reloading a couple times [23:34] robru: ok [23:34] bfiller: the new rollout also includes a check for when there's been new rollouts and forces a hard-reload of the page so this shouldn't happen again ;-) [23:35] robru: works in chromium, will try chrome again after reloads [23:35] great [23:36] robru: working now in chrome too, sorry about that, just needed to reload a few times [23:37] bfiller: no worries, this has bit people a few times hence I made it check for that from now on ;-)