[00:01] 2) PACKAGES="PACKAGES=python-autopilot autopilot-touch libautopilot-qt libautopilot-gtk python-gi ubuntu-ui-toolkit-autopilot friends-app-autopilot" ./scripts/run-smoke -P ppa:ci-train-ppa-service/landing-006 -a friends_app [00:01] thomi: ^ that's a simplified version of whats running, but should be a little quicker and still result in the unlock_screen failures [00:02] ok.. do I really need 'PACKAGES=' twice? [00:02] thomi: oops -typo [00:02] just once [00:02] ok :) [00:02] will that flash my device? [00:02] yes. [00:02] cool - will give that a whirl [00:04] doanac: ERROR: NETWORK_FILE, /home/ubuntu/magners-wifi, not found [00:05] ah - you have to specify the "-n " [00:05] sorry [00:05] where is that? [00:05] in /etc somewhere? [00:05] thomi: /etc/NetworkManager/system-connections/ I think [00:06] doanac: run-smoke doesn't have an -n option, or any network-related options AFAICS [00:08] thomi: apologies. i've been rushing. you have to set NETWORK_FILE=.... in your environment [00:09] ahh ok [00:09] i was about to leave for the day and am not being helpful. [00:09] no worries [00:10] well, it's downloading things, so that's a good start === doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: vila | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [08:12] sil2100: didrocks: is the ci spreadsheet broken? [08:12] thostr_: I'm seeing 2 ERRORS, not sure what was done yesterday though [08:12] thostr_: anything else you note? [08:13] well, I'm just wondering what silo 1 and 3 is right now? [08:13] can I click merge and clean there? [08:15] thostr_: interestingly, if I copy the spreadsheet, there is no more timeout [08:15] like https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dDFGQ1dGNmR1Qy04YmxWQ0pwTEszdEE#gid=1 [08:15] (yeah, you can clean the silo anyway) [08:21] didrocks: welcome, did you recover well? [08:21] Mirv: hey! yeah, still catching up though, but everything's fine. How was your flight back? [08:22] sil2100 should be able to fill in the problems of yesterday and what he tried with those [08:22] didrocks: excellent, I didn't even get redirected to Sweden or anything. there was a risk of that because of extreme fog. [08:22] that'd have ruined the weekend, but now instead I could actually spend a weekend :) [08:23] although the subway took really long, it was good that I left the office 3h before flight [08:23] oh? [08:23] no strike at least? [08:23] (I know they are used to that in that country… hem :p) [08:31] no strike, this time I even get to eat in the plane unlike the last time when catering was striking [08:35] hi ci-train people, http://162.213.34.102/job/landing-002-1-build/26/console says it committed r134 and it looks successful to me, now what needs to be done to have r134 really pushed to trunk where it is still r131? [08:36] jibel: they need to have it published and then click on merge and clean [08:36] jibel: this is up to the lander to finish the transaction that way [08:37] jibel: on that case, this one is not even published [08:37] didrocks, I don't understand, publish what to where? which click on merge and clean? [08:38] didrocks, there is nothing that can be done until Bill wakes up? [08:38] jibel: this is exactly why we teach people how to use CI Train :) [08:38] jibel: yeah, he even didn't test the build, so it's not in distro [08:38] (and so, not in trunk) [08:39] hm, well integration doesn't seem really continuous :/ [08:39] I'll wait for him then [08:39] jibel: trunk == ubuntu [08:39] this is the CI Train [08:39] as long as it's not in ubuntu [08:39] it's not in trunk [08:41] didrocks, give it the definition you want, but the thing is that we are blocked until this rev is in trunk because conflicts cannot be resolved without last rev [08:41] anyway... [08:42] jibel: maybe checking why the tests didn't pass for bfiller (and so avoiding having the trunk broken) would be a first step [08:43] rather than "continously breaking trunk, even if tests don't pass" [08:46] didrocks, np, I'll check with Bill [08:47] thostr_: have you run M&C finally (you didn't answer)? [08:47] didrocks: sorry, yes I did the M&C [08:47] ok, thanks thostr_ [08:47] * didrocks starts to be frightened by the google times out [08:59] oh, right, I need to flash back to Qt 5.0.2 since I heard a rumor I'll be releasing ubuntu-ui-toolkit today :) [09:00] didrocks: can you evaluate if ^ that can be added to the landing plan? apparently bzoltan had heard from ogra that I'll handle it. [09:01] Mirv: let's discuss that in ~30 minutes? they are green to release today? [09:02] err what ? [09:02] i told zoltan that i would mention his landing in the meeting ... [09:02] nothing more [09:02] your name was never mentioned [09:04] interesting deformation of infos ;) [09:07] didrocks: ok. they're green from their point of view and have reportedly run a lot of AP tests too. I'd naturally rerun all. [09:07] let's discuss it in the meeting, meanwhile I'm preparing my phone [09:07] ogra_: :D [09:07] :) [09:23] thostr_: you're right, someone broke the spreadsheet, looking deeper [09:23] (btw, your scopes landing is in NEW I guess) [09:24] didrocks: we had some strange problems with the spreadsheet yesterday already [09:25] sil2100: seems someone changed data validation first on the pending spreadsheet, I wonder if not other things were changed [09:25] didrocks: like, google was offsetting all rows by 1 once, then we reached the limit of number of landings, then something else etc. [09:26] I guess there was a bad copy/paste [09:26] I would have maybe to lock down the cells [09:26] but then, results will be unreadable :/ [09:27] getSiloMatrixRange() returns null [09:27] weird [09:27] did someone touched the metadata spreadsheet? [09:28] didrocks: I didn't, although I was hiding unhiding it when looking for things [09:28] didrocks: but essentially I had nothing to change in the metadata spreadsheet [09:28] ss.getRangeByName("siloMatrix"); returns null… why? [09:29] didrocks: all I did is change the other 2 ranges that were defined [09:29] the range name still exists though… [09:29] 2 ranges? [09:29] didrocks: to increase the number of rows being considered in the main spreadsheet [09:29] ah, don't change the range [09:29] SiloAssignment and PendingUID [09:29] just expand a blank line [09:29] that should consider everything [09:30] Well, someone was adding new landings and things weren't working ;p [09:30] Since the range didn't expand and things were broken [09:30] interesting, all formulas changed [09:30] not sure, someone really changed something :p [09:30] ok, I'll need to look [09:30] in the call in 2 minutes [09:32] hum [09:32] didn't get the link [09:32] https://plus.google.com/hangouts/_/calendar/Y2Fub25pY2FsLmNvbV91cTRvNmQyMWJvNmJ0bm1mcW9xZWtsNTdnOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t.us2orfbhb8ssqjui2u15tajj3s [09:32] ;) [09:33] thx! [09:54] Laney, plars: btw, I talked to thomi yesterday, he found the issue with u-s-s/u-d-m/utf/autopilot and he fixed it (just confirmed that the current version in the landing silo works), that was another bug that the one fixed earlier [09:54] the log was coming from syslog [09:54] seb128: woot [09:55] not stdout/stderr [09:55] a missing decode somewhere else then? [09:55] Laney, http://bazaar.launchpad.net/~thomir/autopilot/trunk-fix-non-unicode-app-output/revision/429 [09:55] that's the fix [09:55] O_O [09:56] Laney, the fix was added to https://code.launchpad.net/~thomir/autopilot/trunk-fix-non-unicode-app-output/+merge/205522 [09:56] that might have more context ;-) [09:57] hello gents ... I have heard that somebody had an idea not to release the UITK :) [09:57] Laney, mandel also said he has a landing pending which fixes the service outputing non unicode chars in the logs [09:57] didrocks^ [09:57] so it should be fixed for good [09:58] seb128: cool, hopefully we can get them in soon [09:58] bzoltan: we can do it on Monday [09:58] once you are bootcamped [09:58] didrocks: too late [09:59] so that you are self-servicing [09:59] bzoltan: how too late? you didn't release for 2 months [09:59] didrocks: I need the UITK this week [09:59] and now, you need to release in the 2 days? [09:59] didrocks: that is past, now is now [09:59] didrocks: I need it today [09:59] bzoltan: this is quite an assertion [09:59] bzoltan: without any first-notice [10:00] you know that people prepare their landings [10:00] and ask for it [10:00] didrocks: I did prepare and I did ask [10:00] not sure why uitk needs something *NOW* [10:00] bzoltan: when, and where? [10:00] didrocks: in the landing asks? [10:00] when? [10:00] didrocks: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc&usp=drive_web#gid=1 [10:01] sorry to repeat, but when? [10:01] didrocks: sorry.. I have checked the doc history -> Feb 10, 4:00 pm EET [10:01] ok, so 1 day and half ago [10:02] didrocks: #176 dogfooding done, looks good [10:02] didrocks: yes ... a [10:02] popey: \o/ [10:02] bzoltan: that's quite ackward, we have to do a lot of work for you, any reason you need it asap? [10:02] and not Monday? [10:04] didrocks: because for the app Showdown the SDK need to be released this week [10:04] sad that was really not planned in advance [10:04] and we have to rush 2 months of work [10:04] bzoltan: I'm happy to help you release it asap even if you are not transitioned, but please coordinate in the future with both asac and pat so that this ackward situation doesn't reproduce again. [10:04] bzoltan: however, I'll ask you doing the testing [10:04] if Mirv has some free slots [10:05] didrocks: I do not find the situation awkward [10:05] which is unsured [10:05] bzoltan, are you prepared for nightshifts in case it gets decided to rip it out again because it has failures ? [10:05] bzoltan: I do find it horrible, you are not the only one busy [10:05] we are as well [10:05] ogra_: you can see the test output attached to the landing ask from Monday [10:05] bzoltan: yeah, you will have to rerun the tests though with the final products [10:05] didrocks: I am sorry [10:06] bzoltan, if it has failures or regressions inm real life, the order from asac is to rip out the landing, have it fixed and to land it again [10:06] didrocks: no prblems with any sort of testing. I am here to do any kind of work needed at any time [10:06] so why dont we go through CI train with this? [10:06] ogra_: whatever it takes :) [10:06] bzoltan, you should really plan a week at least for landing such a big thing the next time [10:06] asac: do we have the CI train? [10:06] asac: I propose that sil2100 or Mirv to "push buttons" [10:06] bzoltan: didrocks: I'm taking time off from Qt 5.2 to run all tests against the new UI Toolkit. the only potential problem so far (if all AP:s pass) is that cu2d shows a lot of failures on desktop side, but maybe there's something wrong with cu2d/autopilot/daily-buildPPA [10:06] having bzoltan running the tetss [10:07] and then we publish for them [10:07] ogra_: we had a Sprint last week ... [10:07] didrocks: also fine [10:07] asac, Kaleo told me he doesnt want to ... i guess you need to convince him [10:07] doesnt want to do what? [10:07] not land? [10:07] :) [10:07] bzoltan, we do sprints too :) [10:07] I do like to see device AP tests with my own eyes, and it mostly just takes away my device for a bit to assure of that [10:07] bzoltan, thats no reason to not warn the landing team in advance [10:07] bzoltan: didrocks: it's good anyhow that SDK Team is assuring to have made tests on their own [10:08] ogra_: I know :) [10:08] did you guys test the binaries that are in the daily-build ppa? [10:08] bzoltan: ? [10:09] asac, kaleo said the MP tests that run during merges would be enough for him [10:09] seems they run some AP tests there or some such [10:09] ogra_: sure, but thats not enough to land [10:09] so he can deliver into trunk, but not image [10:09] i tried to tell him ... but it was late and i gave up at some point :) [10:09] asac: I tested against the devel-proposed image on nexus4 [10:09] bzoltan: but which .debs did you install? [10:09] bzoltan: where did you take them from? [10:10] asac: what deps? [10:10] debs [10:10] debian packages [10:10] asac: I flashed the device...I did not take any debs... only the UITK deb [10:10] bzoltan: where from? [10:10] :) [10:10] where did you download that UITK deb from [10:10] asac: https://launchpad.net/~ubuntu-sdk-team/+archive/testing [10:11] bzoltan: if your stuff is in trunk, the right debs are in the daily-unity ppa [10:11] the current toolkit in daily-build is https://launchpad.net/~ubuntu-unity/+archive/daily-build/+sourcepub/3907912/+listing-archive-extra - I also now cancelled the next run (no changes in bzr trunk) so that those deb:s stay [10:11] asac: I made a source package, dput it there and installed on the device [10:11] anyway [10:11] so what I propose [10:11] we assign bzoltan a silo [10:11] build for him [10:11] anyway, let didrocks explain [10:12] right [10:12] then, he can test all AP running [10:12] turn it to yes once ok [10:12] and we publish [10:12] this is for this time [10:12] also manual testing the device :) [10:12] and we'll track [10:12] yeah [10:12] basic smoke tests [10:12] * Mirv takes a note and goes back to qt 5.2 [10:12] Mirv: can you add a line for bzoltan? [10:12] we'll need an empty MP to flush trunk [10:13] didrocks: ok [10:13] Mirv: don't assign yet, let me debug the issue on the spreadsheet first [10:13] thanks! [10:14] ok, spreadsheet fixed [10:14] rerunning the script, thanks google :) [10:16] hi, is there any reason why the boot speed tests don't seem to have been updated since last year? http://ci.ubuntu.com/bootspeed/arch/amd64/ [10:18] cking: (use cihelp to raise ci team awareness i, I almost missed your query ;) No, I don't think that's expected, let me check some bits [10:18] cking: yeah, its operationally hard for us to ensure those happen until the overall success/fail gets fed into the main dashboard (if you remember that discussion) [10:19] same as with mem event etc. [10:19] ev had taken that on during core sprint [10:19] think he is back tomorrow [10:19] asac, ok, thanks [10:19] cking: asac knows more than me :-} [10:20] cking: just ping him tomorrow so we ensure this didnt get dropped [10:20] asac, i'll add it to asana [10:20] yeah [10:20] thats good [10:20] * asac still isnt really good at asana [10:20] it can be a pain, but it's OK once one gets the hang of it [10:20] cking: paste me the url when you're done [10:21] didrocks: are we done? Is there anything I need to do to help landing the UITK? [10:21] asac: thanks for stepping up [10:22] didrocks: I am running all the available app autopilot tests right now [10:22] bzoltan, read the backlog ? [10:23] bzoltan: you need to wait there's a landing PPA you can test from [10:23] it will be (as an example) https://launchpad.net/~ci-train-ppa-service/+archive/landing-004 [10:24] Mirv: how different it will be from the PPA we land the UITK now? [10:24] Mirv: Whatever... I am fine with it [10:24] didrocks: ooops, just setting testing to green (combobox) gave me "The action you're trying to perform is causing a fatal error and cannot be performed." [10:26] bzoltan: it's different in the way that it's an ensured version that will be directly copied to the archives when ready [10:26] didrocks: so now a fake merge against UI toolkit? [10:27] vila, I added you onto the follower of that task, you will get automatic emails. I can't figure out how to share the URL (bah, asana) [10:27] cking: just copy/paste it [10:27] cking: but it's ok, I got it via notifications [10:30] sil2100: was empty merge enouh, was it tested, or do I need to do some whitespace change? https://code.launchpad.net/~timo-jyrinki/ubuntu-ui-toolkit/trunk_bzr935/+merge/205925 [10:31] Mirv: yes please [10:31] thostr_: yeah, something is broken in the spreadsheet, I'm looking at it. it was in which landing? [10:32] Mirv: empty is enough ;) [10:32] bzoltan: you will need to rerun all the AP test with the debs that we'll provide to you + dogfooding [10:32] bzoltan: and ensure that there is no failure [10:32] bzoltan: we'll keep you posted [10:32] didrocks: thanks, i will do that [10:34] didrocks: the line 77 would need some love so that the status formula would work (and I guess line 76 too) [10:35] Mirv: we're fighting the spreadsheet right now [10:35] sil2100: ok, I'll wait, thanks [10:35] sil2100: and yes thanks, empty merge it is then :) [10:43] didrocks: so, maguro reruns still have failures, but different ones than earlier one and 175. error/fail count is also confusing. [10:44] i'll let doanac know about that [10:44] psivaa: ok, so usual apps not starting you think on the failures? [10:46] didrocks: not sure. i think it was a qmlscene crash that was causing the apps not to start. but this crash has now been fixed. so not sure why the failures are [10:53] psivaa: I explained that qmlscene crash was a consequence [10:53] not the cause [10:53] psivaa: we still need to know why some apps are not starting sometimes [10:56] didrocks: ok, the logs dont say anything about apps failing to start: [10:56] http://ci.ubuntu.com/smokeng/trusty/touch/maguro/176:20140212:20140115.1/6553/address_book_app/761857/ [10:57] psivaa: can you check with osomon by any chance? maybe he would have an idea [10:58] didrocks: ack [10:58] thanks! [10:58] davmor2: please dogfood latest image on mako :) [10:59] maguro* [11:06] both ! [11:06] :P [11:08] balloons: could you take a look at the clock app failures on maguro pls: http://ci.ubuntu.com/smokeng/trusty/touch/maguro/176:20140212:20140115.1/6553/ubuntu_clock_app/ [11:09] renato_: could you take a look at the clock app failures on maguro pls: http://ci.ubuntu.com/smokeng/trusty/touch/maguro/176:20140212:20140115.1/6553/address_book_app/ [11:10] didrocks: for unity8, osomon said to contact Saviq, who does not seem to be online [11:10] didrocks: that was landing silo 10 but now it seems to work again [11:13] psivaa: sure [11:13] thostr_: yeah, all should be good spreadhseet-wise [11:13] (well, we have some backend warning from google, weird) [11:13] * sil2100 is scared of the spreadsheet [11:19] hmm, getting this again http://popey.com/~alan/phablet/device-2014-02-12-111914.png [11:23] didrocks: welcome back [11:24] didrocks: I'm kinda stuffed for mako at the minute because it is being used for the 4.4.2 testing I can test the latest on maguro though? [11:26] davmor2: popey did the mako testing, maguro is enough [11:27] so something is noisy on our images since yesterday [11:27] didrocks: cool I was playing with 175 with the nested mir on it last night it seems to all be working but I'll grab the latest now [11:27] settle showing up here and there [11:28] https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1279298 technically a regression since 174 [11:28] Launchpad bug 1279298 in unity8 (Ubuntu) "Header title sometimes disappears" [Undecided,New] [11:30] asac, yes, seems unity-system-compositor keeps a few cycles after testing, i'll talk to kgunn once he shows up so his team can take a look [11:30] (thought its also indicator-power ... they seem to hand off to each other, looking at the logs) [11:35] (though here it seems to rather be ofono-phonesim https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/30/artifact/clientlogs/unity8/topafter.log/*view*/) [11:37] i wonder if it would just need some timout adjustments of the settle_after test since it might take more time to quiet down now [11:39] right, but only if we have an explanation i feel [11:39] and its confirmed to be a feature [11:41] well, i wouldnt call it "a feature" :) but its a factthat there is one process more in the graphics layer with nested [11:42] i wonder if powerd needs adjustment for nested though ... given that indicator-power is one of the three processes i can see in the log keeping the system busy [11:42] but thats just wild guesswork [11:46] didrocks: can you see if and what the autopilot guys did last night? did they manage to flush their silo? [11:46] asac: they were not published yet [11:47] asac: we'll do that as soon as we can get back to production [11:47] debugging o nfire right now [11:47] (spreadsheet <-> google) [11:47] Googleeee! [11:47] didrocks: ok... spreadsheet problems? i wont bother you then :) === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [12:04] asac: yeah, we're trying to resolve it somehow... [12:05] w-bi [12:05] sigh [12:06] (that was a fragment of a shell command eaten by focus stealing, if anyone's wondering ...) [12:06] cjwatson: ;) [12:19] asac: I fear it's a google deployement issue… [12:22] grrr [12:22] didrocks: whats the issue? nothing works? [12:26] asac: yeah, it has some very bad side-effects [12:26] like can't free silos, nothing [12:28] didrocks: you looking to promote 176 or did you just want the tyres kicking due to the new mir stuff landing (I'm assuming) [12:28] davmor2, yes [12:29] ogra_: you know there are 2 parts to that question :P === MacSlow is now known as MacSlow|lunch [12:29] davmor2: we are looking forward to promote the image [12:30] but so, that includes evaluating the Mir stuff as well :p [12:31] didrocks: as a general quick tyre kicking everything looks good although the movement on the system seems slower but nothing has died yet. And I will start filling in the Spread Sheet now [12:32] ok [12:33] asac: even executing a script is slow, it seems they are getting a breakdown, do we have support for that? [12:36] asac: and everything is working without any error if I copy the spreadsheet [12:41] popey: can you try this again https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1262711 I've only got 1 album on currently plus some additional tracks and this is working fine for me, I'll double check how many I have in a second and add it to the bug [12:41] Launchpad bug 1262711 in unity8 (Ubuntu) "Unity crashes with lots of music displayed in expanded music category in home scope" [Undecided,Incomplete] [12:42] didrocks: forget about support. we have support, but that doesnt give you anything :) [12:43] davmor2: crashes #174 [12:43] we had that with linaro as well... you can file a support ticket [12:43] :) [12:43] asac: well, I'm stuck for 3 hours into this now, and it really seems to be backend related [12:43] asac: I don't have any solution/workaround at hand [12:43] didrocks: did you try to reset your cookies and get a new IP? [12:43] asac: it's not just me, it's everyone [12:43] and the backend scripts in particular [12:44] waow, the spreadsheet is reverting to older state even [12:44] like 8 hours ago [12:44] ok asking on #is if there is a support escalation path [12:45] but i wouldnt hope much. i know what kind of support you get: you can file a ticket and thats it [12:45] you can only hope they see statistical indication that there is a problem [12:45] popey: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1240408 again here this is working for me on Happy(preview from u1Music) and from local music [12:45] asac: ok, we lost some tickets I guess [12:45] Launchpad bug 1240408 in Unity 8 "unity8 crashed with SIGSEGV in QCoreApplication::postEvent()" [High,Triaged] [12:45] asac: and I won't continue on this, just hoping this will get fixed [12:45] Mirv: can you set your ticket in again? [12:46] yeah. google usually knows about these things unless its really just us [12:46] popey: this is on 175 for me [12:46] asac: I'm more afraid that we lost some status and that doesn't match reality anymore [12:46] davmor2: why are you on 175? [12:46] popey: 176 even [12:46] which is the case for some already [12:47] davmor2: my 176 phone is busy, will test in a mo [12:47] popey: no worries [12:47] didrocks: you mean the UITK line that's seemingly removed from CI Train spreadsheet? [12:47] didrocks: so making a copy doesnt help you to workaround? thought you said that [12:47] Mirv: right [12:47] popey, davmor2, i think i have seen that with some 16* image on maguro [12:47] ok [12:48] asac: well, what is lost is already lost, and people are not going to use the new one [12:48] didrocks: done [12:48] ogra_: yeah I'm pretty sure it was happening before but on 176 it isn't :) [12:49] oh [12:52] cking, vila afaik bootspeed tests are still owned by the qa team. Max was looking into it. [12:53] bzoltan: please try https://launchpad.net/~ci-train-ppa-service/+archive/landing-001/ to run all AP tests [12:53] bzoltan: and some dogfooding [12:53] that on latest proposed image [12:53] (176) [12:53] if all pass, just tell us [12:53] on mako and a tablet [12:53] if there is any failure, (even flaky) ensure they are already known [12:54] didrocks: Tablet I do not have, I will use Nexus4 [12:54] didrocks: thanks for setting up the silo === alan_g is now known as alan_g|lunch [12:54] bzoltan: yw [12:54] didrocks: do you have a list of AP tests you usually do? I have one good set. [12:55] bzoltan: all those: http://ci.ubuntu.com/smokeng/trusty/touch/mako/176:20140212:20140115.1/6550/ [12:55] didrocks: half of them fails on a device test [12:55] didrocks: ona stock image [12:56] bzoltan: this is a stock image on device test [12:56] bzoltan: you can check with the CI team, but they are testing real things [12:56] :) [12:56] didrocks: started from a desktop with phablet-test-run? [12:56] following the wiki [12:57] they use the exact same tests [12:57] yeah [12:57] https://wiki.ubuntu.com/Touch/Testing [12:57] https://wiki.ubuntu.com/Touch/Testing#Testing_your_Ubuntu_Touch_Code_before_submission even! :) [12:57] yeah [12:57] details :P [12:58] ogra_: didrocks: I did that and 1 out of 4 it fails [12:59]