[00:27] Why has the https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1241539 not been released to trusty yet? [00:27] Ubuntu bug 1241539 in indicator-sound (Ubuntu) "ubiquity-dm is missing keyboard, input, sound, system indicators" [High,Triaged] [00:27] (all linked branches) [00:28] I need those fixes in the distro for the desktop installer (touch unrelated), shall I cherry-pick indicator-profile configs and upload into the archive? [00:29] xnox: I believe we're still in manual mode, ie. you need to add to the Landing Asks page [00:30] plus a lot of stuff was blocked by Mir transition which has now been just released (in proposed) [00:30] ogra_: didrocks: please release indicators, including changes introduced by merge proposals linked on the bug 1241539. [00:30] bug 1241539 in indicator-sound (Ubuntu) "ubiquity-dm is missing keyboard, input, sound, system indicators" [High,Triaged] https://launchpad.net/bugs/1241539 [00:30] Mirv: I see, thanks for the head's up. [00:31] ogra_: didrocks: and / or schedule it on the landing as appropriate. I care about my changes =) which in that bug are non-touch. [00:46] xnox: it's getting landing starting tomorrow [00:47] xnox: we needed to unscrew mir [00:47] which is the case now [00:51] didrocks: should we suggest landing indicators to sil2100 now that mir is resolved? [00:56] Mirv: right, now that discussion is over, I'm trying to put that on the landing ask [01:04] mir "INARCHIVE" \o/ [01:07] cihelp [01:08] xnox: ? [01:09] cjohnston: i thought some magic will happen and a bot will talk to me. Apperantely there is indicators-sound landing ask required to be filed (to land my change) and i'm not sure where/how to do that. [01:09] xnox: there was an email sent about it [01:10] cjohnston: the very old one - talk to your techlead and/or manager? both of them are sprinting in 7h timezone difference. [01:11] " 3. CI/trunk components: [01:11] - continue to use Landing Asks sheet for the time being" [01:11] xnox: the page to add to is https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=1 [01:11] AIUI they are still the only ones with commit access [01:11] s/commit/edit [01:12] xnox: but a large portion of the landing team is in Oakland right now too [01:12] or atleast a decent [01:12] cjohnston: i am a core dev working on ubiquity in my spare time (non-company time) and there is a savere regression in saucy installer of not showing any indicators, which is now fixed. [01:13] cjohnston: when the rest of indicators are landing from https://launchpad.net/bugs/1241539 they should land with changes across the board from that bug (all are tested & merged into trunk) [01:13] Ubuntu bug 1241539 in indicator-sound (Ubuntu) "ubiquity-dm is missing keyboard, input, sound, system indicators" [High,Triaged] [01:13] Affects Status Importance Assigned to Milestone [01:13] ​ indicator-bluetooth (Ubuntu) Remove [01:13] Triaged [01:13] High [01:14]   Dmitrijs Ledkovs Edit [01:14] Target to milestone [01:14] ​ indicator-keyboard (Ubuntu) Remove [01:14] Triaged [01:14] High [01:14]   Dmitrijs Ledkovs Edit [01:14] Target to milestone [01:14] ​ indicator-session (Ubuntu) Remove [01:14] Triaged [01:14] High [01:14]   Dmitrijs Ledkovs Edit [01:14] Target to milestone [01:14] ​ indicator-sound (Ubuntu) Remove [01:15] cjohnston: is there an email queue for landing ask at all? [01:15] xnox: not to my knowledge [01:15] note that i'm not the team/"owner" of the said components i need to get released to unbreak installer. *sigh* [01:16] * xnox will go and upload something into debian. [01:18] xnox: sorry I don't have anything better to tell you. I'm not very familiar with the process to know if there is anything else you could do [01:19] cjohnston: ok. thanks alot. I've requested it via my tech lead. And added reminder to check upon it in couple of weeks. [01:20] thanks xnox [01:33] xnox's request is landing ask #216 now === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa (Type: "cihelp" for help) | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa (Type: "cihelp" for help) | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - === vrruiz_ is now known as rvr [09:14] sil2100, where do we stand with unity8, mir and friends ? should i trigger a new image ? [09:17] ogra_: hi! You didn't get any message from Didier? [09:18] ogra_: from what he e-mailed me, it seems that mir + unity8 is tested and works, I have some landing asks TODO but these already use the new mir and unity8 [09:21] * ogra_ didnt see any message [09:21] so you mean i should wait til your stuff has landed ? [09:21] ogra_: no no, I guess we can spin a new image with the new mir + unity8 I guess [09:21] awesome, going to then ... [09:21] ogra_: btw. what image are we on now? [09:22] Since my stuff is targetted for image 7 [09:22] proposed is on 6, trusty is on 5 [09:22] ah, the next build would be 7 ... so re-target to 8 [09:22] ACK ;) [09:23] === Image #7 building === [10:22] ogra_: I used the 'adb shell system-image-cli -c trusty -b 0 -b' to switch channels. I had to resest clock from epoch to make it work but it's good now. [10:22] why the second -b ? [10:23] ogra_: it's my french accent, read it as -v ;) [10:23] haha [10:23] ogra_: yet, I want #6 or even #7, should I redo that with s/trusty/trusty-proposed/' ? (yeah, yeah, s/-b$/-v/ too ;) [10:24] if you want to be on proposed, yes, do that [10:24] ogra_: ok, I'll stick to OTA from there [10:24] ogra_: and thanks ! [10:24] np :) [11:00] * psivaa is seeing 'ERROR:phablet-flash:Installation is taking too long or an error occured along the way.' when flashing with image 7 [11:00] ogra_: ^ [11:01] installing one locally to confirm [11:07] psivaa, check if there are any crash files ... if apport kicks in on first boot it might time out before it finished [11:17] ogra_: i can't connect to the devices that failed in this way.. probably a consequence of the bad flash [11:17] hmm, yeah [11:18] what device is that ? [11:18] mko or maguro [11:18] *mako [11:18] both [11:18] oh [11:19] yea, there are 5 devices now i could not connect in the lab [11:20] all had attempted to install image 7 [11:20] mixture of mako and maguro [11:20] well, image 7 isnt existent yet [11:21] hmm, unless my terminal lies [11:21] (teh build command didnt return yet in the terminal i started it in) [11:21] bah [11:21] you are right, 7 is there [11:21] * ogra_ tries an OTA upgrade on maguro [11:26] there was an adbd update from xnox, but i think plars tested that [11:28] ok, UI is up here ... no adb [11:28] xnox, !! [11:28] no mtp either [11:28] hmm [11:29] * ogra_ wonders if this is a subjective feeling or if maguro really got faster [11:32] bah and now unity crashed [11:33] and this time maliit ... hard to get any logs in the terminal-app if everything crashes all the time [11:36] sigh [11:36] so adbd doesnt start and maliit crashes after thre chars in the terminal-app [11:37] popey: hi! [11:37] popey: are you around? [11:47] ogra_: do you have a moment for a packaging diff ACK? [11:48] ogra_: https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-sound_12.10.2+14.04.20131029.1-0ubuntu1.diff [11:50] sil2100: looks good to me. [11:51] xnox: awesomage, thanks! [11:52] what xnox said [11:53] xnox, so image 7 doesnt start adb ... nor does it start mtp ... [11:54] ogra_: i'm upgrading grouper to image 7 at the moment. [11:54] k [11:54] * ogra_ tries to grab logs via recovery [11:55] android-tools-adbd stop/pre-start, process 2027 [11:55] thats what i see in the upstart log [11:56] so it seems to hang in pre-start [11:57] * ogra_ wishes it would be easier to access the ro image from recovery :( [11:57] xnox, ! [11:58] typo [11:58] pre-start script [11:58] if [ -d /sys/class/android_usb ] [11:58] then [11:58] missing semicolon [12:03] hmm, definitely not enough [12:04] hm? is /sys/class/android_usb present ? [12:04] no idea [12:04] i have no chance to get in at all [12:04] cant start ssh because the kbd dies [12:05] ogra_: right so from terminal.app "sudo adbd" does get me adbd [12:05] i cant type that [12:06] dies after three chars for me [12:06] but it looks like you completely reversed the logic for the pre-start script [12:06] ogra_: true and the qemu grep is killing it. [12:07] why did that work during testing ? [12:07] grep qemu /proc/cmdline is killing it. [12:07] let me reboot and make the image writable [12:08] phew, i'm in via ssh [12:10] Ok guys, I go for lunch and changing locations, be back in ~2h [12:11] ogra_: testing http://paste.ubuntu.com/6323631/ [12:11] root@ubuntu-phablet:~# grep -q qemu /proc/cmdline || echo foo [12:11] foo [12:11] ah, yeah, that might work [12:13] xnox, works [12:13] though i wonder why you also broke mtp [12:13] seems that died alongside [12:14] * ogra_ reboots with the change added [12:14] lest see [12:14] probably just a coincidence [12:15] xnox, what i dont get is why it worked for the testers yesterday [12:15] hmm, adb still works, mtp still broken after reboot [12:15] ah [12:15] i spoke to soon [12:15] works :) [12:17] ogra_: i did $ watch -d adb devices [12:18] ogra_: on the host & rebooted, grouper briefly appears and disappears [12:18] yeah [12:18] the fix is fine, please upload [12:18] i'll roll a new image [12:18] ogra_: which is very odd, since in the past once up, it stayed up. [12:18] under ubuntu ? [12:19] we dont use persistent properties yet [12:19] so that theoretically cant work [12:19] (it used to work before we flipped the conatiner though, but teh flip broke that part ) [12:20] xnox, dont forget the semicolon btw :) [12:20] ogra_: where a semicolon, and why. [12:20] (or does the linewrap suffice there ?) [12:21] xnox, after the if condition, before then [12:21] it should be needed. I've tested the patch as it is here http://paste.ubuntu.com/6323631/ [12:21] ok [12:21] mine had the semicolon added after ] [12:22] but if the linewrap is sufficient then i'm fine [12:27] ogra_: how does mtp suppose to work? and why is it sometimes flacky? [12:35] xnox, it works through the same gadget device === josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht (Type: "cihelp" for help) | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [12:36] xnox, by setting additional properties for the device === cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [12:51] cjohnston, hey having a license problem with renato_ on a build here [12:52] sergiusens: I'll need more info please [12:52] cjohnston, this is the result http://paste.ubuntu.com/6323802/ if I add Collabora to the allowedlicenses in http://bazaar.launchpad.net/~private-ps-quality-team/pbuilderjenkins/trunk/view/head:/hooks/A10checklicenseheaders.in [12:52] cjohnston, but I'm not sure what the proper solution would be for the other bits [12:52] the allowedlicenses thing seems weird though; I'd imagine a list of GPL, LPGL, ... [12:53] cjohnston, this is the job btw https://code.launchpad.net/~renatofilho/address-book-service/fork-dummy/+merge/192964 [12:53] sergiusens: looking [13:04] sergiusens: we are investigating and will get back to you hopefully shortly [13:04] cjohnston, get back to renato__ directly if you want; he just pinged me as I used to do this for him ;-) [13:04] ok [13:04] hmm, so rmadison thinks android-tools is in ... [13:05] * ogra_ gives it another 10min to be 100% sure ... [13:05] hmm, no sil2100 ... [13:06] i'll mess up his image planning with my build :/ [13:07] ogra_, hi, I would like to know if you have plans to update folks and EDS packages on "Trusty" [13:07] me ? [13:08] * ogra_ has no plans regarding this ...arent we getting that via sync from debian ? [13:08] ogra_, yes bill told me to ping you :D [13:08] s/sync/autosync/ [13:08] renato__, traditionally seb128 (or his team) maintained eds [13:09] he should be online soon (at the sprint) [13:09] ok thanks [13:10] ogra_, xnox: hi... so was the adbd that went into 7 different somehow from the one I tried yesterday? [13:10] plars, well, not sure [13:10] i havent looked inside the deb yesterday [13:11] but appraently it was different. yes === josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht (Type: "cihelp" for help) | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - === gatox is now known as gatox_brb === cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [13:16] ogra_: android-tools is in release pocket. [13:17] xnox, i know [13:17] it is since a while [13:17] xnox, prob is that sil2100 is gone [13:17] ok =) sorry. [13:17] ogra_: ah, fair enough. [13:17] and he has pending stuff according to the spreadsheet [13:17] waiting for him to return from lunch [13:19] You don't need to wait once rmadison says it's in [13:19] It's definitely fine for image building then [13:19] looking at the sheet it seems only the hud fixes didnt get in yet [13:19] cjwatson, k [13:19] * ogra_ thinks we can afford one more build later this evening and just kicks off image #8 now [13:28] popey, do you know if we will revisit the app categories at some point ? the options the store offers are really odd imho [13:29] i hope so, but that's more bueno's dept === gatox_brb is now known as gatox [13:40] popey: ogra_: it feels like at the moment it's offering categories as as for .debs / from debian policy. (so copy&paste from the non-click app store) [13:41] * xnox ... maybe not policy, but wherever debian lists all possible categories. [13:43] yeah [14:02] fginther: https://bugs.launchpad.net/jenkins-launchpad-plugin/+bug/1214970 <- this is "fix released" now right? [14:02] Ubuntu bug 1214970 in jenkins-launchpad-plugin "test result URLs posted on MRs are linking to s-jenkins instead of public location" [Undecided,New] [14:06] dobey, yes, that's been fixed [14:06] was a configuration issue, not an actually code change [14:09] right [14:11] i'm doing some work to get tarmac back up to par, for where we need it to be [14:24] === Image #8 is done === [14:24] psivaa, plars ^^^ that one should work again [14:25] ogra_: you rock! [14:25] rfowler_: are the devices back up? [14:25] * ogra_ upgrades [14:31] ogra@chromebook:~$ adb shell [14:31] root@ubuntu-phablet:/# [14:31] looks good [14:31] xnox, ^^^ [14:32] * popey updates to 8 [14:53] hey sil2100, how are you? [14:54] hey ogra_! [14:54] sil2100, we had an issue with image 7 ... we fixed it and rolled #8 a bit earlier [14:54] ogra_: ah nice, you kicked an image! [14:54] (that was my question) [14:54] sil2100, i updated the spreadsheet for your stuff [14:54] what was wrong with image 7? [14:54] didrocks, adbd didnt start [14:55] ah, not nice! [14:55] issue with the upstart job [14:55] mir was in image 7 as well? [14:55] it was tested by two people ... [14:55] yeah [14:55] ok… [14:55] new mir and unity8 [14:55] excellent! [14:55] not sure how the tests did succeed though [14:55] thanks ogra_, /me won 10 minutes :) [14:55] ogra_: tests succeed? [14:55] (for the broken adbd) [14:55] I see no result on the dashboard [14:56] ah [14:56] yeah, this was landing ask #? [14:56] yeah, #7 didnt start ... no adb :) [14:56] and #8 is there since 20min only [14:56] Hello! [14:56] ogra_: I mean, I don't see the adb upload [14:56] hey sil2100 ;) [14:56] ogra_: ok, thanks :) [14:56] ogra_: in the landing plan [14:56] didrocks, oh, that was xnox , i think we might have missed adding it [14:57] but he asked popey and plars for testing ... sorry, i should have taken care of the spreadsheet [14:57] plars, rfowler_, any issues getting our devices restarted to flash to image 8? [14:57] (but it was late last evening and i forgot) [14:57] fginther: it looks like they are still not up, for image testing at least [14:58] hmm [14:58] ogra_: no worry, thanks for tracking that to the end [14:58] so Mir on maguro is *a lt* snappier after reboot [14:58] sil2100: how is the landing going? Seems well from what I see [14:58] ogra_: yeah, there is still some mem leaks [14:58] but gets really awful after starting a few apps [14:58] (visible on mako as well) [14:58] like, worse than before imho [14:58] oh really? [14:58] possible, quite a bunch of code entered [14:58] its lots and lots better after a fresh boot [14:59] yeah, feels quite sluggish [14:59] didrocks: rather well, I also tested indicator-datetime, no regressions with AP unity8 but I'm not sure how the fix is supposed to work [14:59] nearly as smooth as mako [14:59] 3386 phablet 20 0 284180 53304 37700 S 99.3 2.8 0:37.20 camera-app [14:59] didrocks: I set up an alarm and didn't see any indication of it alarming [14:59] but as soon as i have a few apps open it crawls [15:01] sil2100: argh, checkig with upstream as well? [15:01] didrocks, since youre at it, can you add robru's seed change to the plan too ? [15:01] sil2100: basically, instead of having the day, you should have a generic message [15:01] so we finally get that off the plate [15:02] ogra_: well, I want that backward compatibility to be discussed properly here before we take a decision [15:02] ogra_: I try to have that happens, it's hard for them to see that blocking us :p [15:02] at the sprint you mean ? [15:02] yep [15:02] yeah, we need a defined process how to change the API [15:02] but that one is actually safe [15:02] 3D directional audio is definitely not used by any app yet :) [15:03] right, but imagine someone start developping today [15:03] basing on our sdk 1 [15:03] sil2100: i open indicator, and it says "... Battery, Sound, Tuesday, Network, ..." which is plain odd =) [15:03] fginther: haven't heard back yet, but it looks like the devices on the image testing side are up now at least. Just started the tests [15:03] (that's with old image) [15:03] they will have a surprise :) [15:03] ogra_: ^ [15:03] fginther: can you check yours? [15:03] plars, great [15:03] ogra_: didrocks #8 seems to have broken the music app? [15:04] I get a white screen on mako [15:04] popey, oh ? [15:04] xnox: ah, this is ok [15:04] didrocks: ^ [15:04] popey, works on my maguro [15:04] hmm [15:04] (well, i have no music on it ... ) [15:04] didrocks: I mean, the Tuesday -> now it's Upcoming [15:05] plars, all are still off-line. I'll follow up with rfowler_ in case he's not aware they need attention [15:05] didrocks: but there was also a mention about the alerts being fixed [15:05] popey, "please import music and restart the app" ... on mako as well [15:05] ogra_: for me it started the first time after a reboot, showed some music and then fell over [15:05] ah, add some music [15:06] didrocks: I'm waiting for upstream to comment [15:06] sil2100: oh that one, yeah [15:06] so its more the scanning than the app [15:06] sil2100: sounds good, put it in red [15:06] dunno [15:06] didrocks: in the meantime, I check the hud maybe [15:06] scanning is separate [15:06] it could be something inside the app reading from mediascanner [15:06] yeah, that shouldnt cause a white sceeen [15:06] * popey reboots and tries again [15:07] #5 is fine [15:07] sil2100: yeah, sounds good! [15:08] popey, musci app is native C++ right ? [15:09] nope [15:09] qml + plugin [15:09] k [15:10] popey, coudl you check #6 ? [15:10] /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: unrecognized option '--file=' [15:10] /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: invalid option -- 'I' [15:10] QUbuntu: Could not create application instance [15:10] http://people.canonical.com/~ogra/touch-image-stats/20131025.changes [15:10] http://paste.ubuntu.com/6324436/ [15:10] i see mediascanner was updated in #6 [15:11] yeah [15:11] ok, will test #6 [15:12] phablet-flash ubuntu-system -d mako --revision 6 [15:12] ? [15:12] -b 6 [15:12] oh [15:12] phablet-flash [15:12] yeah [15:13] ah, needed channel too [15:13] * ogra_ is so focused on system-image-cli nowadays [15:13] INFO:phablet-flash:Flashing revision 6 from channel trusty-proposed [15:13] yay [15:13] i like that it tells me now [15:13] :) [15:13] shame it whizzes past so fast [15:14] WOAh === alan_g is now known as alan_g|tea [15:14] system-settings just crashed in my face [15:15] and doesnt start anymore now [15:16] and again [15:20] ogra_: music app works in #6 [15:20] popey, can you try if system-settings behaves for you ? [15:20] on #6? [15:20] it just vanishes for me after clicking around in it a bit [15:20] on 8 [15:21] * ogra_ wonders if anyone actually checked the impact of the boots transition for out toolkit [15:21] *boost [15:21] *our [15:21] i have visited every pane in system settings on #6 [15:21] no problems [15:23] hmm, doesnt for me anymore either [15:23] but i'm at the tenth try or so [15:25] oh [15:25] and now the G+ app crashed === alan_g|tea is now known as alan_g [15:32] wow [15:32] apps are super crashy on #8 [15:33] didrocks, do you know if anyone from the SDK team asessed the impact of the boost transition on our stuff ? [15:34] haha [15:34] ogra_, how does the whole landing ask work for the android tree? [15:34] * ogra_ just tried to start the ubuntu desktop tour on the ubuntu website in the browser [15:34] Didn't the boost transition predate the previous good image? [15:35] ogra_, can I just push stuff to the repo? [15:35] Please could you find out whether it's actually related before implicating it [15:35] cjwatson, oh, right, it was all boost updates, not the transition itself [15:35] http://people.canonical.com/~ogra/touch-image-stats/20131029.1.changes [15:35] There's a boost change in this image, but it's not the transition, indeed [15:36] ah, no [15:36] http://people.canonical.com/~ogra/touch-image-stats/20131029.changes [15:36] its also bumping from 1.53 to 1.54 [15:36] Wasn't #7 good? [15:36] (image 7 was broken) [15:36] no, adb was messed up [15:36] so the tests couldnt run [15:37] Oh. Well, please still find out whether it's related before we go trying to unwind a complxe transition [15:37] *complex [15:37] cjwatson, i only wanted to know if someone from the SDK team actually checked the potential sisk for us [15:37] *risk [15:37] * ogra_ didnt mean to point fingers or anything [15:38] That looks like only a small part of the boost transition - most of it was already done [15:39] I think that was just lucene++? [15:39] sil2100: hey man, I wonder if you could comment on this please? https://bugs.launchpad.net/autopilot/+bug/1244089 [15:39] Ubuntu bug 1244089 in Autopilot "Autopilot 1.4 trusty AP test errors" [Critical,New] [15:39] cjwatson, yeah, my path of thought wa more going towards if we potentially need to rebuild any native apps === gatox is now known as gatox_lunch [15:40] or if thats covered on the Qt level for us [15:40] There's more in http://people.canonical.com/~j-lallement/touch/changes/20131025.html, but there's also quite a lot else [15:40] (that was #6 - looks like the last promoted image was #5?) [15:40] 25 was image 6 [15:41] i ran that fro a few days without issues [15:41] OK [15:41] the breakage came between 6 and 8 [15:42] xnox, do you know what the process is for committing/pushing to the android repo these days? [15:43] * ogra_ thought that process was called rsalveti [15:43] ogra_, I have push rights; just want to know how it plays with the landing asks and all that [15:43] sergiusens: you need to push, wait for the tarball to be out, and upload [15:44] sergiusens: the tarball is done at every hour [15:44] sergiusens, ah [15:44] but you need to sync with the landing team [15:44] rsalveti, ok, I just want to push the revert for mtp [15:44] sergiusens: or just ask either me or xnox to sponsor it [15:44] ogra_: FWIW I just unpacked everything from http://people.canonical.com/~ubuntu-archive/click_packages/click_list and none of those have any direct linkage to boost [15:44] sergiusens: which patches? [15:44] sergiusens, you need to mount / rw and replace the android img file i think ... to test it [15:45] ogra_: I would have expected direct linkage to boost from apps to be strictly forbidden - the SDK team doesn't like that kind of thing :) [15:45] inside the ubuntu-system.imd [15:45] rsalveti, http://people.canonical.com/~sergiusens/mtp/0001-Revert-Disabling-mtp-for-manta.patch [15:45] rsalveti, remember :-) [15:45] cjwatson, well, system-settings is native iirc [15:45] cjwatson, as well as the browser [15:45] sergiusens: yeah, I can check it now :-) [15:45] got the new laptop in place [15:45] ogra_, I know how to test; I have my changes locally [15:45] cjwatson, i meant less the click packages ... [15:46] sergiusens: will review your other mrs today as well [15:46] ogra_: It neither directly build-depends nor depends on boost [15:46] ogra_, I just need to know what the bureaucratic part is [15:46] cjwatson, k [15:46] ogra_: Likewise webbrowser-app [15:46] sergiusens, landing ask ... have someone from the team move it to landing plan ... [15:46] ogra_: So I suppose it's *possible* something obscure there is going on but it doesn't seem like the highest-probability cause ... === Laney is now known as KruSha666 [15:47] cjwatson, yeah ... Mir and unity depend on it, if there is breakage its more likely in them, thanks for checking the apps ! [15:49] hmm [15:49] gallery-app looks really bad on the dashboard [15:50] 50% fail rate [15:50] cjwatson: can you grep for dlopen? =) [15:53] funny, locally it is actually rock solid [15:53] xnox: no matches [15:54] thomi: sure, give me a moment ;) === KruSha666 is now known as Laney === doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [16:10] ogra_: yeah, on mako and maguro too [16:11] right [16:11] ogra_, are you not on canonical irc for a reason? [16:11] sergiusens, erm, no reason except not noticing that i dropped [16:29] sil2100: I assigned you to the bug, and marked it as incomplete. Feel free to change the status once that information is added. Thanks! [16:29] thomi: sure! Thanks, will test the branch whenever it's possible [16:45] ok, I figured there was an automated system for that [16:45] thanks for your help [16:48] Mirv: tested HUD, publishing if all is ok in cu2d [16:56] sil2100: cool, and morning! [16:57] cyphermox: could you pre-ack packaging change http://10.97.0.1:8080/view/cu2d/view/Head/view/Phone/job/cu2d-phone-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_dialer-app_0.1+14.04.20131029.1-0ubuntu1.diff ? [16:57] sil2100: so you got unity8 AP also working? [16:58] hrm, sure... [16:58] Mirv: yes \o/ [16:59] Mirv: some tests are failing, but re-runs help [16:59] plars, given the crashyness of apps, i dont think it is worth to give back anything on image 8 [16:59] Mirv: those seem like problems with introspecting unity8 in overall sometimes [16:59] ogra_: agree, tests are still running so if there's anything you're curious about we can do retries in a bit, but I don't think it looks good [16:59] sil2100: yeah being able to run unity8 tests now with the new Mir with just one command is great [16:59] Mirv: btw. we have a lot of failures for one machine for HUD - you think it's still ok to publish? Other platform is better, below threshold [17:00] plars, yeah, its not woth it, we need a fix for Mir first [17:00] sil2100: I don't know, better do some validating of those? [17:01] Mirv: all good for dialer-app [17:01] I'd be a bit wary of running that on a "live" phone though :) [17:01] sil2100: have you looked that there are _1400_ autopilot errors in unity stack? [17:01] Mirv: the autopilot tests themselves scare me ;) [17:02] yeah I wouldn't suggest running the autopilot tests with SIM card.. [17:03] ci help [17:03] slangasek: :) [17:03] doanac: ^ [17:04] slangasek: no space between the two... but if there is a vanguard, they are even better :-) [17:04] oh [17:04] cihelp? [17:04] slangasek: works. what's up? [17:04] slangasek: that's the one [17:04] doanac: hi :) Just testing the system that ev is briefing us all on :-) [17:04] ticket resolved :) [17:05] slangasek: also a tip: the channel topic includes some information about who's vanguard and what critical issues are known [17:05] Mirv: I vaildated that those are not regressions if anything, still wondering why those fail [17:05] Mirv: oh, didn't look at unity stack ;p [17:05] 1400?! [17:05] :O [17:05] sil2100: maybe related to the unity stack problem... [17:05] slangasek: tell ev to explain to ping the vanguard if there is one instead of cihe*lp please :-) [17:05] Mirv: :O [17:06] doanac: ack - but ev didn't tell us to look at the topic, he just said to type 'ci help' ;) [17:06] slangasek: makes sense. we should update our alert patterns to catch that also [17:06] too late, the moment has passed, we'll have to clarify this by email later ;) [17:06] :) [17:06] sil2100: yeah, slight problems, looks like dbus also with autopilot 1.3? (you e-mailed about autopilot 1.4) [17:06] doanac: maybe support also "ci help", "CI Help!" and so on :) [17:07] Mirv: there is a reason it's what it is. :-) [17:07] not all clients support things like spaces [17:07] right === gatox_lunch is now known as gatox [17:15] didrocks: ACK please! http://10.97.0.1:8080/view/cu2d/view/Head/view/HUD/job/cu2d-hud-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_hud_13.10.1+14.04.20131029.1-0ubuntu1.diff [17:16] sil2100: +1 of course [17:16] \o/ [17:16] thanks dude! [17:16] didrocks, bug 1245958 [17:16] bug 1245958 in unity-mir "Apps crash with image 8" [Undecided,New] https://launchpad.net/bugs/1245958 [17:17] FYI [17:17] didrocks, no way to promote that one [17:17] ogra_: argh, Mirv can you handle that? ^ [17:18] didrocks, kdub and alan_g discuss it in -touch atm [17:19] but i wont be around late today so wont be able to drive that [17:19] didrocks: ok, I'll at least poll on them to get the news on a fix [17:20] ogra_: ah nice! [17:20] thanks :) [17:21] I do have some crash files in /var/crash for apps too, although from user perspective one doesn't see that much it seems [17:22] ok [17:22] marked the bug as critical as it prevents image promoting [17:30] sergiusens, added landing #288 to the landing plan for you [17:35] ogra_, thanks [17:38] oooh Mirv https://codereview.qt-project.org/#change,69368 via https://bugreports.qt-project.org/browse/QTBUG-32225 [17:42] Mirv, sil2100: i've added a reference to the bug report for Mir causing lots of app crashes in image 8 to the old unity team work spreadsheet, so we prevent to much duplicate work [17:44] popey: \o/ for progress [17:44] kenvandine: thanks [17:44] vila: can you glance at http://10.97.0.1:8080/job/autopilot-trusty-daily_release/216/ - all AP tests failing because of a dbus problem? [17:47] Mirv: EOD, doanac ? ^ [17:47] looking [17:47] seems limited to unity8? [17:48] doanac: thanks [17:56] doanac: unity7, not unity8 [17:56] Mirv: sorry those keys are too close together [17:56] doanac: I noticed upgrading to that trunk unity install xpathselect 1.4, maybe it's related? [17:58] doanac: I also saw an e-mail from Chris Lee related to problemws with Autopilot 1.4 (but we use 1.3 in the PPA) about that Unity7 "hasn't been updated to use thenewer 1.4 DBus wire protocol (Unity7 a unique beast in that the functionality that isusually provided by libautopilot-qt/gtk is part of the Unity7 source tree.)" - it says dbus but does that mean xpathselect instead? [17:58] Mirv: possibly. i was worried some of those DBUS errors seemed unrelated. but that seems feasible. [17:59] ah right [17:59] https://code.launchpad.net/~3v1n0/unity/xpathselect-1.4 - so maybe this? [18:01] I filed bug #1245988 now, updates welcome [18:01] bug 1245988 in Unity "All AP tests fail with unity - xpathselect 1.4?" [Critical,New] https://launchpad.net/bugs/1245988 [18:01] Mirv: both 1.3 and 1.4 are getting installed for xpath [18:02] doanac: the new unity-autopilot only depends on libxpathselect1.4 [18:02] doanac, Mirv, i think that's the culprit. unity is speaking 1.4, autopilot is listening to 1.3 [18:04] hi guys [18:05] thomi, o/ [18:05] so, Marco and I were looking at those branches yesterday - I didn't think he'd merged them yet though [18:05] * thomi pulls unity [18:05] it seems https://code.launchpad.net/~townsend/unity/fix-lp1243529/+merge/192381 got merged [18:05] thomi, it's been merged [18:05] oh [18:05] well [18:05] this is the problem we face - landing autopilot 1.4 and *all* the test suites at the same time takes som serious coordination :) [18:05] so is this a chicken and egg problem with moving to autopilot 1.4? [18:06] right - either we land AP 1.4 and fix the tests later, or we try and do everything at the same time [18:07] We were trying to do everything at once, but I guess I should have been clearer with Marco [18:07] so I guess the options are either to revert the unity7 change, or go ahead and land AP. I know which one I'd rather do, but I'll leave that to you guys :) [18:08] I vote for reverting the unity7 change [18:08] ಠ_ಠ [18:10] i'm pretty sure asac would prefer to revert [18:10] of course now I see the bug that was addressed: https://bugs.launchpad.net/unity/+bug/1243529 [18:10] Ubuntu bug 1243529 in unity (Ubuntu) "unity FTBFS on trusty" [Critical,Fix committed] [18:11] appears that unity7 fails to build with xpathselect 1.3? [18:12] fginther: should build fine once marcos branch is reverted [18:13] I mean, it used to build against 1.3, marco merged code to build it against 1.4 [18:14] thomi, ok, I see that 1.4 isn't in trusty anymore [18:14] hang on [18:15] so are there 2 changes that would need reverting: https://code.launchpad.net/~townsend/unity/fix-lp1243529/+merge/192381 and http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3581 ? [18:15] thomi, ah. libxpathselect 1.4 is still in the daily-build ppa [18:16] that's causing unity7 not to build (https://launchpadlibrarian.net/154760401/buildlog_ubuntu-trusty-amd64.unity_7.1.2%2B14.04.20131023-0ubuntu1_FAILEDTOBUILD.txt.gz), hence the bump [18:19] fginther: I see. [18:21] fginther: I'm not really sure what makes it land in the PPA [18:21] I guess it's some cu2d config? [18:21] * thomi shrugs [18:22] thomi, yes. whoever added the autopilot 1.3-trusty branches probably didn't realize that xpathselect was a dependency [18:23] :( [18:23] We never expected 1.3 to land in trusty. I guess the config was written assuming 1.4 would get released there [18:24] thomi, most likely [18:30] doanac, mirv, wokring on a suggestion, one moment [18:31] psivaa, plars just an update on filemanager.. 4 errors are bugs, the rest I think I've fixed [18:31] balloons: awesome, is it more consistent now too? or are the 4 bugs things that don't happen every time? [18:32] plars, the 4 remaining failures have to do with seemingly the clipboard not working [18:35] fginther: ok. indeed xpathselect was probably not in radar when reverting to AP 1.3 for trusty. [18:36] balloons: are the fixes in already with image 8? [18:36] doanac, Mirv, thomi, so we have two options: 1) add xpathselect 1.3 to trusty and revert the unity7 MP or 2) Land autopilot 1.4 in trusty and update the remaining autopilot tests [18:36] psivaa, no, i'm working on a branch [18:37] balloons: ack, thank you :) [18:37] trying to get everything working :-) [18:37] either way 2) needs to happen eventually [18:37] 2 is probably less total work also. [18:38] with 2 there will be test failures for the image and for upstream merger, but this might put more pressure on getting them resolved [18:38] fginther: who makes the decision? asac? [18:40] doanac, this might be didrock's team. they did the original change to get 1.3 into trusty [18:41] doanac, this is probably a landing pipeline descision [18:41] yeah [18:43] fginther: given they are probably in meetings, should I send off an email to summarize? [18:43] doanac, good idea [19:16] didrocks: clearly, that subtitle should have been written 'quickly improve' [20:26] fginther: it should be a revert - as discussed before all AP 1.4 changes should land at once, otherwise we block various stacks for undetermined amount of time [20:28] ogra_: are you about? the qtmultimedia/audioengine seed changes are finally greenlighted now [20:31] Mirv, I can start on the cu2d-config changes. Once that's done, can you remove the xpathselect 1.4 packages from the daily ppa? [20:37] fginther: yes, I can remove it then [20:42] Mirv, doanac, can you review: https://code.launchpad.net/~fginther/cupstream2distro-config/xpathselect-trusty-1.3/+merge/193133 [20:43] fginther: looks good [20:45] +1, deleting the PPA build of xpathselect 1.4 [20:56] Mirv, doanac, now to revert the unity7 bump of xpathselect: https://code.launchpad.net/~fginther/unity/revert-libxpathselect1.4/+merge/193137 [21:01] fginther: reading [21:02] thanks for that, hopefully we'll get desktop AP results after that. as an example, because of the problem I had to dedicate my laptop to running unity7 AP:s manually so that it would be possible to validate an libunity release, instead of getting the desktop results from jenkins. [21:02] Mirv, you remember to pack a spare laptop just for this purpose, right? :-) [21:07] yeah, my draggable trusty 5y old Dell is so fun to travel with :) [22:29] doanac: ping? [22:30] doanac: can you please explain to me what the three touch images are? There's "touch_sf4p", "touch", and "touch_custom". Why are there several images, and what do they mean? [22:32] cihelp [22:32] ^^ [22:33] thomi: one sec [22:33] thanks :) [22:34] touch == mir [22:34] custom is a custom variant [22:35] sf4p iirc is mir disabled [22:35] thomi: ^ [22:36] cjohnston: any idea what's different on the custom image? [22:36] thomi: tis a question for achiang [22:36] ok [22:37] thanks charles [22:37] oops [22:37] thanks cjohnston [22:37] ya, him too [22:37] lol [22:38] thomi: no problem at all [22:38] thomi: anytime === doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -