[00:20] so has monitor mode on the broadcom chips inside of nexus 7's been figured out yet? [00:20] hi btw :) [00:24] hy [00:25] ubuntu touch will not be released for nexus 7(2012)? [00:25] pirea, apparently not [00:25] that's what a news release says [00:26] Well, not really. [00:26] Also, we've already released 1.0 for the N7 :) [00:28] RAOF: News say there will be official ubuntu Touch phone in 2014? [00:28] And it's not like the N7 will immediately cease to work. It's just that it'll no longer be one of our primary development targets. It'll be easy enough for someone else to pick up and make 2012-N7 images. [00:28] OttOmanTR: So they say :) [00:29] I was expecting to see it in CES 2014 [01:33] hello === duflu_ is now known as duflu [01:47] Greetings, It seems to be difficult to find information on my question, try as I might.. but is it possible to access ubuntu-touch on my Nexus 7 without having to use ADB/SSH commands from my Mac? As in plug it in, and have it show up as a device on OSX? [01:59] charles: are you still around? [02:00] fishscene: if OS X supports MTP, then yes, it should be automatic. [02:00] If not, then no, there probably is no way. [02:01] ah ok. I'll check into OSX support for MTP as currently, it doesn't show up as a device. Thanks! [02:01] :) [02:02] mhaines: http://apple.stackexchange.com/questions/106156/does-mavericks-support-mtp (In case this question ever comes up again) === chihchun_afk is now known as chihchun [02:40] where exactly does the sources for 3.0.0-3-maguro live? neither the CM mirror nor does the ubuntu kernel repo seems to have that particular kernel source [04:20] fishscene: fantastic. Thanks! [04:25] is there any plans for official samsung galaxy s4 9505 support ? [04:25] DjMadness: no. [04:26] Canonical is going to support as few device as possible. Samsung probably doesn't care about Ubuntu right now. [04:27] DjMadness: the Nexus line was designed to do what we need hardware to do [04:27] which makes it the obvious choice for development and testing right now [04:27] Google only supports 4 Android hardware platforms, and Canonical is dropping support for all but 2. [04:28] a shame, powerful phone, would be nice with it... guess ill need to study the current port and see what i can fix [04:28] we're adding support for at least one [04:28] It's the hardware OEM's job to port and support any particular OS to a phone. On the other hand, there's nothing preventing community support from popping up too. :) [04:29] +1, we need community help to bring Ubuntu to a larger number of phones [04:29] and we will continue to offer whatever support we can to those community ports [04:29] mhall119: if Canonical would keep building Ubuntu for the current platforms without official support, that would be a huge help. [04:30] nhaines: that's one of the options being discussed [04:30] mhall119: it sounded awfully hypothetical on the ubuntu-phone ML. [04:31] nhaines: we just started those discussions this morning [04:32] Pledging to discontinue all support for maguro (as an example), and then starting a discussion about maybe continuing builds is not promising. [04:32] maguro has other issues, it's not going to get a KitKat update from Android [04:32] which means to maintain it we'd need to maintain two versions of the Android stack [04:32] Okay then. Pledging to discontinue all support for grouper (as an example), and then starting a discussion about maybe continuing builds is not promising. [04:33] I know TI still supports the maguro drivers for Android. In about a week or so I'll probably look into that situation if no one else looks like they're going to. [04:34] nhaines: I can't undo the past, but dholbach and I are currently working on it [04:35] Don't get me wrong, my KitKat ire over maguro is directed squarely at Google. But automated builds for the 13.10 supported platforms would be a big help. Maguro has other issues. [04:36] nhaines: at a minimum we will make it easy for anybody to build their own images for the N7 and N10 using the latest Ubuntu [04:37] I think if goldfish gets a good x86 port that'll make a huge difference. I really do hope that the feature roadmap takes off at a much, much faster rate than it currently is. [04:38] well, we only have so many man-hours, and we'd like to put most of them towards improving Ubuntu rather than maintaining Android [04:39] we already have 1 ubuntu image, and multiple device images [04:39] Yes, I understand what a time sink platform support can be. But Ubuntu 13.10 under-delivered, 14.04 is way behind schedule, and the SDK version plans for the click app store are a guaranteed failure. [04:40] So I really, really hope that dropping platform development allows the OS development to get back on track. [04:41] This sounds kind of negative. Dropping hardware support is really disappointing, but isn't really important in the long run. It's the OS and SDK development that's really critical. [04:42] And that's the progress that worries me. I'm hoping that there's a dramatic speedup in the next couple of weeks. [04:46] is there a tag or a way to finding the corresponding sources for an image? [04:47] (and no, the apt-get source doesn't seem to do the right thing) [05:06] barry: the qt5.2 eta depends on how quick all those build failures get fixed. address-book-app is slightly later in the dependency chain, see http://pad.ubuntu.com/qt52-dependencies - but I notice one of the dependencies at least hasn't been even tried to rebuilt yet, so I'll try that which may make address-book-app buildable [05:14] oh, it had been tried but failed === vying is now known as Guest89211 [06:33] barry: progress! address-book-app's dependencies and it itself got compiled now, unlike 4 days ago. slightly less red now. [08:05] good morning [08:06] morning === shuduo is now known as shuduo|afk === shuduo|afk is now known as shuduo [10:07] thostr_: actually, we have found a HUD regression [10:07] psivaa: can you give details, please? ^ [10:11] thostr_: didrocks: so from image 126 onwards with the introduction of 13.10.1+14.04.20140108-0ubuntu1 hud version messaging ui smoke test is failing on maguro [10:11] http://ci.ubuntu.com/smokeng/trusty/touch/maguro/126:20140113.1:20140107.1/6050/messaging-app-autopilot/663980/ is the failing link [10:12] reverting the hud, libhud-client, libhud2 from 13.10.1+14.04.20140108-0ubuntu1 to 13.10.1+14.04.20131205-0ubuntu1 makes the test pass [10:13] thostr_: are you able to get those fixed? I would be in favor of reverting for now to let you more time investigating the issue [10:13] psivaa: thanks for finding it out :) [10:14] didrocks: yw :) [10:14] psivaa: just one remaining! :) [10:14] right on that now === tsdgeos_ is now known as tsdgeos [10:29] didrocks: yes, we'll be looking into it right now [10:29] thostr_: ok, direct upload for reverting meanwhile, ack? [10:29] (I don't change trunk) [10:31] didrocks: is this really hud? [10:32] didrocks: the log says: "Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable." [10:32] thostr_: well, it's linked to HUD change, see what psivaa pasted ^ [10:32] "11:12:55 psivaa | reverting the hud, libhud-client, libhud2 from 13.10.1+14.04.20140108-0ubuntu1 to [10:32] | 13.10.1+14.04.20131205-0ubuntu1 makes the test pass [10:32] " [10:33] didrocks: sure, isn't it more that case by hud now doing proper checking revealed an issue somewhere else? [10:34] didrocks: the environment variable is used by other services as well, so it should be set [10:34] thostr_: that's possible. I'm not the one knowledge for those env variable. Hence the "need more investigation", right now, we are trying to go back to a promotable image ASAP [10:35] thostr_: note that messaging-app is a deb, not click app [10:35] so I guess it doesn't have APP_ID [10:35] didrocks: right [10:36] didrocks: ok, then revert and we'll get in touch with other guys and try to get it resolved [10:36] thanks thostr_, doing [10:37] xnox, good morning. I'm trying out the emulator, (on Trusty, amd64, Intel graphics) and all I get is a black screen such as http://ubuntuone.com/3nKQs3TFjEiIYxEFFrVMEc - any ideas what could be causing this? I can see a warning about decreasing the amount of memory allocated in the log, but I'm not sure it's got something to do with it - http://pastebin.ubuntu.com/6755473/ [10:37] Hi all... got some questions re: security if anyone is happy to answer them or point me to some documentation. [10:37] dpm: he's apparently away this week [10:38] Basically need info on security and crypto support from a networking perspective [10:39] ah, thanks Laney for the heads up [10:45] kalikiana, tvoss_: if you have some time in the next days, I'd appreciate some criticism for https://code.launchpad.net/~pitti/qtubuntu-sensors/integration-tests/+merge/201742 [10:46] kalikiana, tvoss_: should I fix the broken outputRange() (and enable the corresponding test) in that MP, or in a subsequent one? [10:46] pitti, a subsequent one, review for your branch is at the top of my list [10:46] ack [10:47] tvoss_: not *that* urgent, please don't drop something else for it :) [10:47] thostr_: HUD revert uploaded [10:47] didrocks: ah, found the regression that broke images? [10:47] pitti: for messaging-app yeah, remaining rssreader one [10:50] didrocks: not sure if it's hud... when looking at the the test case code it's not using HUD anywhere... [10:51] thostr_: maybe a side effect? did anyone try the same revert than psivaa did? [10:51] will be a first step I guess ;) [10:52] didrocks: we're running autotests... trying to figure out where it fails [10:52] thostr_: the list of changes in the image messaging-app is the following one: http://people.canonical.com/~ogra/touch-image-stats/20140113.1.changes [10:52] s/in the image messaging-app/in the image messaging-app started to fail/ [10:54] didrocks: pete-woods is on it [10:55] ..okay. Looking for some information regarding serious crypto support for ipsec style networking for Ubuntu Touch and whether reliance on the android low level layer will come with the same inherent vulnerabilities. If any kernel devs can give some insight and point me to some info on launchpad 'd be greatly appreciated as I'm trying to work out whether I'll be needing to fork Android, attempt to fork Tails for ARM, or whether I [10:55] Will very happily contribute upstream for any code from the project I'm working on. [10:58] dpm: the emulator takes a LOOOONG time to start [10:59] i get a black screen for ages [10:59] ah, good to know [10:59] * dpm re-runs it [11:00] didrocks: the messaging app autopilot tests pass for me using the newest HUD on my N4 [11:00] popey, it's alive! :) [11:00] ☻ [11:00] is there something I'm missing? [11:00] pete-woods: see the test results, it's maguro only [11:00] d'oh! [11:01] Morning all [11:01] I don't have a galaxy nexus to try on :/ [11:03] pete-woods: maybe check on the emulator just in case? [11:03] I'll try it [11:04] thx [11:05] didrocks: if it is maguro only I can run the tests to look into it but it could be the issue I highlighted the other day if it is only maguro [11:05] davmor2: can be, can you reproduce and chat with psivaa about the revert he has done on the HUD? [11:06] didrocks: will do, let me run through my incoming first and then I'll get on it [11:09] didrocks: that autopilot test doesn't even use HUD [11:09] it does look like the environment isn't being set up correctly, http://ci.ubuntu.com/smokeng/trusty/touch/maguro/126:20140113.1:20140107.1/6050/messaging-app-autopilot/663980/ [11:09] Could not determine application identifier. HUD will not work properly. [11:09] Provide your application identifier in $APP_ID environment variable. [11:09] pete-woods: as told, can be a side effect, we need to investigate why the revert worked reliably for psivaa [11:10] fair enough [11:10] pete-woods: is it provided for .debs? [11:10] (see the discussion I had with thostr_ above ^) [11:10] didrocks: it is [11:10] remember that messaging-app is a .deb [11:10] ok [11:10] * pete-woods thought he'd been very thorough with this HUD release, I ran like *all* the autopilot tests I could find :/ [11:11] does anyone know if networking is supposed to be working with the emulator? I don't get any list of existing networks or connection to the access point my host PC is connected to [11:12] dpm: network works for me [11:12] its transparent. [11:12] didrocks, morning, I'm wondering if there is a way to fix the following CI fails https://jenkins.qa.ubuntu.com/job/ubuntu-download-manager-trusty-amd64-ci/161/console that are due to the speed of jenkins instead of increasing the timeout, is a little ugly to keep increasing the timeout when in a local machine there are no issues [11:13] i.e. open the browser and you get ubuntu.com load, without selecting a network [11:13] mandel: this question is for the CI team, you should ping cihelp in #ubuntu-ci-eng [11:13] didrocks, ok, thx! [11:14] davmor2: didrocks: pete-woods: what i did was to remove hud, libhud-client, libhud2 first and then installed all of them of 13.10.1+14.04.20131205-0ubuntu1 version [11:20] popey, ah, cool, let me try that. Any other caveats you've run into with the emulator worth mentioning? [11:25] dpm: it doesnt seem to update [11:25] i dont know if that's intentional [11:26] popey, ok, thanks, good to know [11:29] popey, what I've noticed as well is that the left swipe to reveal the launcher is extremely sensitive. You have to be very accurate to hit a narrow pixel area to reveal it [11:30] yeah the emulator doesn't do edge swipes [11:33] tsdgeos: zsombi1 might be able to fill in where the tests fail on his computer. I think he even had so that one run failed and the second one succeeded. [11:35] Mirv: that was with the text inputs [11:36] didrocks, heh, seems pitti didnt read your "hold the line for touch" mail [11:36] (we need tags for email subjects ;) ) [11:36] ogra_: ah, ubuntu-touch-meta? [11:36] let's put Blink back! [11:37] well, it's sdk-libs, they are not installed by default? [11:37] I can add a propagation blocker bug if you want [11:37] pitti, yeah [11:37] i doubt thats needed though [11:37] but it didn't seem like something which would be installed by default [11:37] err [11:38] indeed ubuntu-sdk-libs is installed by default [11:38] good ;) [11:38] everything depends on it ... thats our API [11:38] argh, I read a NOT [11:38] heh [11:39] hum, ok, will had a little noise then, normally new components shouldn't regress anything existing though, let's hope ;) [11:39] sdk libs holds all of Qt, sensors html etc support [11:39] ah, ok [11:39] its only html5 stuff anyway [11:39] now, we can add a propagation blocker [11:39] pitti, nah, i doubt html changes do anything to the tests [11:39] we dont have specific html5 app tests yet [11:39] (we probably should though) [11:43] didrocks: so I can exactly reproduce the issue on the rss app so I'll start digging there but it is looking like it thinks a state is missing and it can't search for canonical which might be the header or a list items view so I'll get back to you when I know more [11:44] davmor2: thanks! did you try the messaging app as well? [11:44] with reverting the HUD? (to have a confirmation) [11:46] hi guys. fyi: http://phandroid.com/2014/01/13/ubuntu-touch-devices-2/ === zsombi1 is now known as zsombi [11:47] didrocks: that I'll be running in a minute once I get the tests pulled for the rssreader so I can see what it is attempting to do and try to reproduce it manually [11:50] seb128, could it be that your last gstreamer merge added a dependency for libgl1-mesa-glx on arm ? (we are trying to make out why http://people.canonical.com/~ogra/touch-image-stats/20140110.1.changes exploded) [11:50] didrocks: hmm that;s not a good start http://paste.ubuntu.com/6755753/ === _salem is now known as salem_ [11:54] (neither glu nor glx should ever be on arm) === MacSlow is now known as MacSlow|lunch [11:57] ogra_, could be, Laney did those [11:57] Laney, ^ [11:57] ogra_, what happens if you try to uninstall libgl? [11:57] e.g what wants to be removed? [11:57] hmm, havent tried yet === alan_g is now known as alan_g|afk [11:58] * ogra_ twiddles thumbs ... [11:58] i totally forgot how slow apt is [11:58] (on the device) [11:59] Reading package lists... 38% [11:59] *twiddle* [11:59] just wanted to note big thanks to popey for his help today. Now running version 121 after flashing. Many thanks. [12:00] looks like it [12:00] Laney, can we revert that ? [12:00] KathyReid: yay [12:00] it made the image 10M bigger (compressed, i bet its a lot more uncompressed) [12:00] revert, everyone's favourite word [12:01] popey: thanks heaps! That command worked a treat. [12:01] let's find out why and then have a look [12:01] Laney, ok [12:01] * ogra_ still sits in front of 38% [12:02] ahm finally http://paste.ubuntu.com/6755787/ [12:04] ogra_, you have your answer then [12:04] Laney, ^ [12:04] so it's via opencv [12:04] is that new plugin? [12:05] it's only being built now [12:05] seems like [12:06] easy solution would be to disable that option [12:06] right [12:06] is that the right thing to do? [12:06] I don't even know what opencv is [12:07] if we didn't use it until now and it was not an issue I doubt that's something we really need [12:07] well, you could make it not hard depend on glx/glu on arm [12:07] it's a computer vision library for doing feature detection [12:07] yeah, if somebody wants to "fix" opencv that's alright === alan_g|afk is now known as alan_g [12:08] not sure how much work that is, I would prefer us to not spend too much efforts on stuff we don't need [12:08] i'm not concerned by opencv, just by the GL libs that are of no use (and might bend our alternatives in a direction we dont want) [12:08] I think the word 'we' is dangerous in situations like this [12:08] the archive doesn't exist only to support the Ubuntu Touch effort [12:08] GL and GLU on arm are pointless [12:09] ogra_: can you give nested a try with grouper? [12:09] I'm not denying that it's a bug [12:09] rsalveti, i would love to, my battery misbehaves since i got up ... it still reboots as soon as i unlock the screen (just tried) .... but i plan to once it works again [12:09] Laney, it goes back to the old difference of opinion on whether we should spend ressources on fixing the whole universe (nothing specific to touch, we had the same argument about !desktop before) [12:10] ogra_: ok, cool [12:10] Laney, we could spend our life fixing every un-used package in universe, or we can focus on what benefits most users (e.g the default images) [12:10] Laney, but we already have that discussion and agreed that some of us disagree, so let's not have it again [12:14] I'll try disabling opengl on armhf [12:16] Laney, thanks [12:16] ogra_: I'd appreciate it if you could report a Debian bug about it with rationale [12:16] not something I'm particularly familiar with [12:17] well, there is no opengl HW on arm so it is pointless ... needs to use gles or should be disabled [12:18] Laney, i'd like to heard someone like jhodapp on that case first ... [12:18] sounds like a good basis for a report :-) [12:18] i'm not a graphics guy either :) [12:18] buh [12:19] (but i know that our (not debians i think) mesa packages fiddle with the alternatives a lot ... my fear is simply that some GL path gets bent in a way that breaks our setup) [12:21] didrocks: hi, could ofono-phonesim and ofono-phonesim-autostart have been updated as transitive dependencies of the ones listed in (http://people.canonical.com/~ogra/touch-image-stats/20140113.1.changes) ? [12:22] pete-woods: no, the only packages that changed on the images are all listed by ogra_'s script [12:22] pete-woods, then they would be listed [12:22] it's just that if I say, install messaging-app-autopilot, it brings in a lot of other packages [12:23] including those two I listed [12:23] what I mean is, those packages aren't in the image [12:25] pete-woods, because we dont want to ship all the test packages [12:25] we'll soon do a cleanup and rip all autopilot stuff out [12:25] I don't expect them to be in the image [12:26] what I mean is, does the script report version changes in them, as they are not part of the image [12:26] no [12:26] the diff gets created for the image manifest files, it only compares image changes [12:26] so they could change version, break something, and that script would not list them as potential suspects? [12:26] right [12:26] we only care about image changes here [12:27] that's fine, I just want to understand the information I've been given [12:27] if you want external stuff compared i guess QA would have to set something up for this [12:27] didrocks: I'm in the rss app trying to reproduce the steps bit by bit and the keyboard isn't appearing that might make it trickier to work with I'll reboot and try again from scratch but if that is happening in the test that might explain why it is failing to find a topic it can't type it in [12:27] walking down the autopilot dependencies and list version changes there or some such [12:28] that sounds like a sensible thing to have set-up [12:28] it's the dependencies of each of the autopilot test suites we care about [12:28] right [12:29] Laney, hmm, looking at CMakeList.txt in opencv i wonder why GL is used at all ... [12:29] OCV_OPTION(WITH_OPENGL "Include OpenGL support" OFF IF (NOT ANDROID AND NOT APPLE) ) [12:29] shouldnt that force it off ? [12:30] davmor2: yeah, then, please join your effort with psivaa with his revert results [12:30] oh, debian/rules overrides it [12:31] ya [12:41] psivaa: okay can you run me through this step by step. Make the phone writable, remove hud, libhud-client, libhud2, then install hud, libhud-client and libhud2 from 13.10.1+14.04.20131205-0ubuntu1 ? does that sound about right and then run the tests on the device if they will let me === alan_g is now known as alan_g|lunch [12:44] davmor2: yes, that sounds good for maguro message app test failure [12:45] psivaa: okay cool thanks [12:45] davmor2, not sure you need to remove, installing the old version should be enough [12:46] seb128: thanks [12:53] ah, finally a sign of life from my grouper === MacSlow|lunch is now known as MacSlow [12:57] hello everybody, i have just installed ubuntu touch, after rebooting the device i dont see anything no log in or something else. The device is a google nexus 10 === sebastien is now known as Guest7445 [13:00] didrocks: we can now reproduce the hud failure... however, it fails also for the old hud :( [13:01] didrocks: do we have another list of changes happened between the images, not package changes but rather test or setup changes? [13:01] thostr_: interested, not sure this env variable is linked [13:02] thostr_: we know messaging_app tests didn't change itself as there was no messaging_app release [13:02] and the tests are in upstream code [13:03] any changes to ap itself? [13:04] you would have seen it in the package list === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === alan_g|lunch is now known as alan_g [13:35] ogra_: next image should also be a bit faster on grouper, as I added back the hwcomposer [13:35] rsalveti, whee ! [13:36] ogra_: but for it to work properly we need mir to land as well [13:36] * ogra_ just noticed he had his image default to SF [13:36] don't know the current status of that [13:36] gah!!!!!! why will this test not run damn it [13:36] ogra_: system-image? [13:36] afaik cdimage is still booting with SF by default [13:36] rsalveti, we switched it around saucy release [13:37] the released image had Mir by default [13:40] ogra_: right, but just system-image [13:41] I flashed cdimage yesterday and it booted with SF [13:41] oh, indeed [13:41] * ogra_ doesnt use that old cruft [13:41] I use it when I need to build large packages [13:47] rsalveti, [13:47] root@ubuntu-phablet:/# ps ax|grep unity-system [13:47] 1240 ? Sl 0:02 unity-system-compositor --file /tmp/mir_socket --from-dm-fd 8 --to-dm-fd 13 --vt 7 [13:47] looks fine [13:47] UI is up and usable [13:48] ogra_: great [13:48] hmm should the flickering bug be gone ? [13:49] i dont see any strobe like flickering anymore, thats great [13:49] ah, there it is [13:49] davmor2: it could be outdated but some steps in http://pastebin.ubuntu.com/6213423/ might be helpful to run the AP test locally.. [13:49] starting a webapp triggers it again [13:50] ricmm_, did we have a fix for that in the pipe ? ^^^ [13:50] psivaa: figured it out I was trying to run a specific case rather than the suite D'oh [13:50] ogra_: it's already fixed in mir's trunk [13:50] davmor2: ack [13:50] rsalveti, ah, thanks [13:50] that's why I said we need latest to land [13:51] yeah [13:51] didrocks, so i can confirm that all devices now work fine with nested Mir mode, but we need another Mir release to land it then [13:51] ogra_: triggers what? [13:52] ricmm_, strobe like flickering of the display [13:52] ogra_: ok, it was planned for tomorrow (if we can promote an image today) [13:52] on what device [13:52] ricmm_, grouper [13:52] ricmm_, seems rsalveti knows about it and there is a fix, so ignore me [13:53] you mean apps not launching? [13:53] and the shell flickering forever in total edath? [13:53] death* [13:53] ricmm_: the screenshot issue [13:53] right [13:53] ricmm_, i mean the whole display flickering like a strobe right after i start the first app [13:53] yea, its in trunk [13:53] lp:mir [13:53] right [13:53] helease it [13:53] all fine then [13:53] i wish i could [13:53] go fix that rss reader [13:53] all landings are stopped [13:54] I landed like 4 branches yesterday and a large unity-mir patch [13:54] and it was flawless [13:54] ricmm_, awesome, so we'll get that in 8 weeks on the images :P [13:54] isnt it just rss reader blocking it? [13:54] yeah [13:54] my packages are in since 128 [13:55] go fix it then [13:56] didrocks: any updates on rss reader? I took a stab at it but frankly I cant see anything obvious from our side of things [13:56] ricmm_: psivaa is still reverted one by one [13:56] and davmor2 as well is investigating AFAIK [13:57] hi folks [13:57] any success for some of you about using it on galaxy s3 ? [13:58] didrocks: so I can confirm that I am not getting a failure now on messaging running phablet-test-run -p messaging-app-autopilot messaging_app [13:58] davmor2: what's the difference with the CI? seems that psivaa is getting the failure quite reliably (and we have it everytime since image 122 on all runs) [13:59] didrocks: no this is with the reverted hud [13:59] didrocks: ricmm_: i'm reverting the last bit for the rss reader failure. no luck yet. not sure if any format change in the feeder page could cause this type of failure [13:59] davmor2: ah ok, sorry, mixed my brain [13:59] davmor2: thanks for confirming :) [13:59] thostr_: ^ [14:00] psivaa: ah, can be… [14:00] didrocks, should I hold on the calendar app test changes? [14:00] sergiusens: yes please, just prepare it so that we can get that in once we can promote an image [14:01] didrocks: http://www.canonical.com/rss.xml is the link, not sure who maintains that. probably IS? [14:02] balloons: do you know? ^ [14:02] didrocks, it's all prepared; just not in store; as in store == in next image [14:02] sergiusens: ok, perfect, thanks! I'll keep you posted :) [14:03] but the test isnt failing at the xml itself [14:13] ahhhh [14:13] ? [14:14] didrocks: psivaa the error comes from a format change in the page [14:14] the feed name changed from Canonical to Insights [14:14] and the autopilot test is poking at a hidden object field [14:14] not the visible "Canonical" thats on screen [14:14] Ran 1 test in 93.418s [14:14] OK [14:14] phe [14:14] phew [14:14] why does the test not use a local feed that autopilot ships ? [14:14] you can test by fetching rss.xml from web archive from the 9th [14:14] ogra_: because its a broken test [14:14] obviously [14:14] asac: ^ [14:15] now promote me an image [14:15] heh [14:15] ricmm_, http://ci.ubuntu.com/smokeng/trusty/touch/maguro/129:20140115:20140107.1/6080/ ... [14:15] can we put a call out to test devs for mocking stuff instead of pulling live unreliable data? [14:15] calendar app doesnt look good atm [14:15] because what if theres a network problem, then all this stuff will fail when the apps themselves may be working just fine.. [14:16] ricmm_: ah that explains it then I was looking at it seeing the canonical and thinking it is right there you dumb ass app ;) [14:16] ogra_: that is an issue on the maguro opening and closing the app repeatedly it locks up I discovered that one [14:16] so the test is broken in two parts [14:16] 1. using the live XML feed [14:16] 2. poking at a non-visible QML element [14:16] davmor2, right, but we cant promote it as is [14:17] ogra_: but there is no way to easily fix it as it is a massive can of worms of race conditions [14:17] sergiusens: I guess its normal that android-emulator is to be removed when installing ubuntu-emulator? [14:17] lovely [14:17] ogra_: everyones favourite [14:18] davmor2: whats the can of worms? [14:18] calendar app breakages? [14:18] ricmm_, yeah [14:18] how come [14:18] jdstrand, android-emulator is a virtual package [14:18] 128->129 changelog should be null, or very small, no? [14:18] ogra_: I've manually run the tests and it is fine, it's just when autopilot runs them you get the races [14:18] arent landings stopped [14:18] ricmm_, http://people.canonical.com/~ogra/touch-image-stats/20140115.changes [14:18]