[01:06] cyphermox_, buh, spreadsheet is borked again [01:54] robru: ah you guys already on the spreadsheet issue.... [01:55] sadly my build succeeded but no ppa ...guess the spreadsheet does the copy [02:05] robru: looking... [05:21] davmor2: ask the multimedia team to land qt 5.2 support :) === bfiller is now known as bfiller_afk [07:49] anyone else see bug 1280124 ? [07:49] bug 1280124 in linux-mako (Ubuntu) "kernel log getting spammed every 10s with battery notifications" [Undecided,New] https://launchpad.net/bugs/1280124 [08:07] Mirv: thank you for the handbook ;) [08:11] Mirv: you are back next Monday, right? [08:11] sil2100: you're welcome :) [08:11] sil2100: yes, 24th [08:16] didrocks: morning! [08:16] morning [08:16] Oh god... google's doing it again it seems [08:17] didrocks: I see a lot of ERROR fields in our spreadsheet, tried manually re-running syncstatus and it failed with an error ;/ [08:17] ah [08:17] not sure, no time to debug it [08:17] * sil2100 is afraid again [08:18] seems that already some packages could be published [08:18] Yes, I'll try publishing something and see if it unblocks and/or works [08:19] anybody to reconfig silo5? [08:20] thostr_: I can, in a moment [08:28] didrocks: sil2100 FYI, dogfooded 182 and it's good - only one bug filed bug 1280124 [08:28] bug 1280124 in linux-mako (Ubuntu) "kernel log getting spammed every 10s with battery notifications" [Undecided,New] https://launchpad.net/bugs/1280124 [08:29] popey: can you try 181, seems we won't ever have results on maguro for 182 [08:29] maybe a quick debug then :p [08:29] and nobody in the CI team is able to rerun them as psivaa isn't around and vila doesn't know the procedure [08:29] asac: FYI, we do have a gap ^ [08:30] Bah [08:30] I specifically did these early because I have lots of other things to do [08:30] popey: sorry, or we can say "discare maguro". Anyway, nobody is fixing the flaky tests [08:37] didrocks: we have nobody in eu timezone who can manage CI? [08:37] didrocks: packaging ACK - http://162.213.34.102/job/landing-008-2-publish/lastSuccessfulBuild/artifact/packaging_changes_address-book-service_0.1.0+14.04.20140213-0ubuntu1.diff (new deps) [08:37] popey: apparently not with psivaa away [08:37] That seems sub-optimal. [08:37] it is [08:38] like in image 181, we will never know if the unity8 new failures are legit or not [08:38] I'll just disregard them [08:38] * didrocks is tired to be the only one pushing [08:38] sil2100: +1 [08:39] * sil2100 tries debugging google scripts [08:39] But so far it seems to be the same absurd thing like a few days ago [08:39] sil2100: you sohld rather publish what can be published I guess [08:39] http://paste.ubuntu.com/6930076/ ffs [08:39] I would call this a server-side issue, my RT is still not answered [08:40] popey: mtp restarted in between? [08:40] possibly [08:40] * popey retries [08:40] didrocks: yes, but the spreadsheet doesn't update when things are published [08:40] sil2100: ah… [08:41] didrocks: I'm afraid that it would lead to confusion once I do that ;/ [08:41] at least i have office wired internet on my side [08:44] sil2100: last edit -> 8 hours ago [08:44] so same issue [08:44] my RT is still unanswered anyway [08:45] didrocks: I noticed something strange though [08:46] didrocks: refreshSiloStatus() seems to work for the first rows - it goes through those correctly, updating the status as needed - then suddenly around row 27 it failed [08:46] didrocks: oh [08:46] didrocks: ok, it came back to life ;p [08:47] * didrocks still sees #ERROR [08:48] sil2100: reconfigured? [08:49] didrocks: right, ERROR is back... and now I can't even scroll the bottom sheets since instead of the < > I have 'try out new google spreadsheets' [08:49] thostr_: I'll try it now, we have sheet issues [08:49] didrocks: 181 taking an aaaaaaaage to first boot as it does apparmor stuff [08:50] popey: I didn't see an apparmort change between 181 and 182 though [08:50] well, I'm going backwards from 182 to 181 [08:50] finally done [08:51] thostr_: reconfigured [08:51] sil2100: thanks. silo 11 is ready for publishing [08:53] thostr_: saw that, let me publish, seems like the first few rows can be published safely even when those google problems appear [08:53] sil2100: great [08:57] odd issue with 181 [08:58] if i tap the power button, I never get back to the welcome screen [08:58] and if i hover my hand over the light sensor, it's like the phone is on a call, the screen dims [08:59] popey: weird, I would have said it's due to Mir [08:59] but I don't see anything to fix it in 182 [09:00] * popey reboots [09:01] fine after a reboot [09:01] ⍨ [09:02] http://popey.com/~alan/phablet/device-2014-02-14-090226.png [09:02] check out that battery drain [09:03] although with no scale on either axis the data is somewhat meaningless [09:07] didrocks: two additional packaging diffs in a moment, these are a bit big so I'm trying to figure them out completely [09:07] thostr_: you know what's up with all that 'lets remove libubuntudownloadmanager1' ? [09:09] sil2100: no, i'm confused there as well [09:10] good morning [09:11] Morning [09:11] sil2100, hey there, can I get a silo for l. 34 in the ci train spreadsheet? [09:12] tvoss: let me check [09:12] didrocks: done dogfooding 181 [09:12] popey: all good after this reboot? [09:13] tvoss: hm, might be a problem with that, since the spreadsheet seems to be encountering some google-infra problems and the lower rows of it seem a bit brokish [09:13] yes [09:13] (like your graph btw) [09:13] thanks popey [09:13] sorry you had to redo the testing [09:13] np [09:13] sil2100, working fine here [09:14] tvoss: you don't see any ERROR fields? [09:14] sil2100, nope [09:19] thostr_: ok, so, the packaging doesn't seem right [09:20] thostr_: I don't think we can release silo 11 for now [09:20] thostr_: the thing is, the u-d-m version there adds all the 'breaks' and 'replaces', but it adds them according to a version that was not released into ubuntu [09:21] thostr_: so, if you consider this package and the one in Ubuntu, it's breaking and replacing non-existent packages, and not dealing with the ones that are actually in Ubuntu ;) [09:22] thostr_: let my try talking to mandel about this [09:22] sil2100: mhhh, I think I don't understand ;) [09:23] sil2100: I just added this package to ci, and this shouldn't have changed anything to my understanding [09:23] so the problems have been there before? [09:24] or did mandel and co not release any recent version of u-d-m for a long time? [09:24] thostr_: so, it for instance states that it breaks package ubuntu-download-manager-common1, while ubuntu-download-manager-common1 does not exist in the archive anywhere ;) As this binary package was never built in the archive [09:24] thostr_: I think it's the latter indeed [09:27] sil2100: is mandel online yet? [09:28] can somebody check why J doesn't pick this up? https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/fake_app_fixture/+merge/205916 [09:28] Morning all [09:28] mandel: ping, could you poke me once you're up? [09:28] kalikiana: you mean, for automerging? [09:29] kalikiana: there's no automerger anymore for projects using CITrain ;) [09:30] sil2100: I didn't think we were switched yet since the training is expected for monday [09:30] we don't have the test plan set in stone either [09:30] kalikiana: I think you're switched already since we already made one release using CITrain [09:31] kalikiana: at least a silo was prepared [09:31] k, I'll poke around in the team [09:31] Ok ;) [09:40] didrocks: packaging ACK, seems ok: http://162.213.34.102/job/landing-012-2-publish/lastSuccessfulBuild/artifact/packaging_changes_mediaplayer-app_0.20.5+14.04.20140213-0ubuntu1.diff [09:41] asac, didrocks: I noticed Maguro is running slower with nested mir and the newer mirs. So it might be that the device is locked up/crashed or just timing out. It might be sensible to concentrate on landing the 4.4.2 stuff and dropping the maguro sooner rather than latter. Just a thought. [09:42] tsdgeos: ^ [09:43] sil2100, I cna give you a hand with those [09:43] can* [09:43] sil2100, let me grab a cup of tea and we can do a hang out, sounds right? [09:44] \o/ Tea [09:44] sil2100: +1 [09:45] mandel: sure ;) [09:51] didrocks: found that silo 009 is *probably* ready for release, will try publishing it then [09:51] sil2100: ok [09:51] sil2100: please update with comments on the main spreadsheet [09:51] sil2100: mandel: could you forward the hangout link? [09:51] didrocks: too bad the backend doesn't have the 'Testing: Yes' info, as it's frontend only ;) [09:51] yep [09:51] sil2100, thostr_ https://plus.google.com/hangouts/_/76cpjc6h5o6i7sn5mtls4anf1k?hl=en-GB [09:51] mandel: be there in 5 minutes [09:52] sil2100, didrocks I'm trying to maintain the symbol files in dbus-cpp but I don't think that the amount of effort I/we have to put into it is reasonable [09:53] tvoss: how are you maintaining them? [09:53] sil2100, manually? [09:53] it's working for quite a lot of upstreams have stable ABIs though [09:54] didrocks, sil2100 you might remember that I had to switch to a different compiler version last week, and this is just not doable [09:54] didrocks, sil2100 again, I don't think we should assume api or abi to be stable for certain components or alternatively not force things into main [09:54] you should try to get help maybe from doko to reswitch to the latest get all symbols in place again [09:55] tvoss: so, in that case, you should bundle everything using that non stable apis in the same source [09:55] no need to separate things if you can't maintain clear boundaries [09:55] but we already had this discussion too many times I guess [09:56] didrocks, so you are effectively saying we shouldn#t share code? interesting pov [09:56] didrocks, well, we don't find a resolution [09:56] tvoss: if you want to share code, define an API and try to stabilize it [09:56] didrocks, you are off reality here [09:56] didrocks, my 2 c [10:00] didrocks, I just checked boost 1.55, unity-mir and a few other c++ packages. None of them has symbol files. Mind elaborating? [10:00] sil2100, ^ [10:00] tvoss: unity-mir is an issue, we should add it, not sure for boost, check with the maintainer [10:02] didrocks, I guess I'm asking for the policy here that is not clear to me [10:02] tvoss: it's really hard to do with C++ code, could you show me the current state of the symbols files that you tried preparing? [10:03] sil2100, it's your branch that I took and mp'd [10:03] tvoss: packages in main should have a symbol file to track (but that doesn't cover everything) ABI breakage, or we should ensure upstream really knows what they do and bump the soname at every breakage [10:03] didrocks, which I'm happy to do [10:03] didrocks, symbol files are just not an option from my pov at this point [10:04] sil2100, https://code.launchpad.net/~thomas-voss/dbus-cpp/force_gcc_4.7_and_symbols/+merge/206359 [10:04] tvoss: if you are doing the testing manually and rebuild everything yourself in your slot each time you break ABI, I guess that's fine. I think to avoid having you testing everytime manually, you should at least have some integration tests to detect breakages between your different components [10:05] didrocks, that is what the ap tests are for, aren't they? system-level integration tests that catch abi issues and such [10:05] tvoss: geh, crap, let me look into what's up there [10:05] tvoss: yeah, we need those though for location and so on. There is none AFAIK [10:06] didrocks, sure, let me just point out that we never suffered any functional regression or abi breakage with either dbus-cpp or location service. It was a compiler version mismatch that caused trouble in the end [10:07] tvoss: yeah, but dbus-cpp was rebuild against that compiler version mismatch which created issues on location-service [10:07] and that was uncatched [10:07] tvoss: ok, now this is something absurd, I wonder what dpkg-gensymbols does there on that jenkins machine since it doesn't make sense what I see [10:09] didrocks, you couldn't have detected the issue even with the symbol files in place as we learned last weeek [10:09] sil2100, yup, I actually lost track what is causing the issue [10:09] sil2100, stuff works fine locally, I send it off, it breaks [10:09] tvoss: yeah, but with AP tests, we would [10:10] sil2100, please take a look => https://code.launchpad.net/~mandel/ubuntu-download-manager/fix-packaging/+merge/206377 [10:11] didrocks, that's a different statement than saying you have to maintain your symbol files, both semantically and in terms of time and effort [10:11] tvoss: come on, I told that if no symbol file, I'm happy if he had a way to detect ABI breakage [10:11] and AP tests would be one of them [10:11] but it seems we would have none if we remove symbols [10:11] tvoss: normally I would check if it builds in a PPA and then land it if all is OK, but this would basically mean we won't have CI working for dbus-cpp ;/ I'll try to investigate with Francis later I guess [10:12] Since this seems to be somehow related to the CI setup [10:13] didrocks, sil2100 I'm quite confused now: we did the archive upload without a symbols file and both of you were adamant about having a symbols file for the next regular upload, which is why sil tried to help, too [10:13] tvoss: right, as long as we don't have AP tests covering/using your code [10:13] didrocks, at least I wasn't aware of that. sil2100 ? [10:14] tvoss: it's one of the other, the function I want is "be able to detect ABI mismatch" [10:14] sil2100, I need to go for a few mins to try and fix my laptop or find another machines, will me back in 20 mins or so.. :-( [10:14] we know symbols won't cover it 100% and that AP won't cover it 100% either, but at least we need one of the 2 [10:15] sil2100: I saved the backend script and the issue is gone [10:15] on the spreadsheet [10:15] :O [10:15] sil2100: removed your comment [10:15] mandel: thanks! [10:15] uh oh, indeed it looks fixed [10:16] sil2100, awesome, let me know in a few mins to make sure :) [10:16] didrocks: I still ahve the 'last edit 10 hours ago' though [10:16] sil2100: same [10:18] mandel: it's building now ;) [10:21] Ouch [10:21] didrocks: Exception: ['sudo', '-E', 'cowbuilder', '--execute', '--bindmounts', '/srv/juju/vol-0000011d/var/lib/jenkins/silos/landing-011', '--bindmounts', '/var/lib/jenkins', '--', '/srv/juju/vol-0000011d/var/lib/jenkins/citrain/chroot-tools/buildsource-chroot', '/srv/juju/vol-0000011d/var/lib/jenkins/silos/landing-011/ubuntu-download-manager', '--gnupg-parentdir', '/var/lib/jenkins', '--uid', '106', '--gid', '65534', '--gnupg-key [10:21] link? [10:22] http://162.213.34.102/job/landing-011-1-build/19/console [10:22] Link wink wink [10:22] apt-get: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory [10:22] above [10:22] so yeah, setting up the rootfs failed [10:24] "apt-get: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory" O_o (https://launchpadlibrarian.net/166268254/buildlog.txt.gz) [10:24] Mirv: woha! Same error I had? [10:24] didrocks: haha, without reading backlog! [10:24] didrocks, cf #ubuntu-devel [10:24] sil2100: yeah, I didn't read backlog and just pasted what seemed really weird for me elsewhere [10:24] Mirv: ahah, thanks for not stopping at the last line :p [10:24] sil2100: it's a distro issue [10:24] right, what seb said [10:25] ;) [10:31] didrocks, what if we made dbus-cpp a src package? much like gmock? [10:31] tvoss: I thought you wanted to share it. So I would prefer if you don't want to maintain ABI, that we use AP tests to detect a failure [10:31] cihelp: ev: can anyone help resurrecing mako tests? [10:32] err mako devices [10:32] didrocks, it's not that I don't _want_ to maintain ABI, it's a question of time and resourcing [10:32] tvoss: so AP tests I would say [10:35] didrocks: I am done with the silo tests [10:36] bzoltan: so, everything pass? no tests failing? [10:37] didrocks: I give you the list of tests I run ... the notes tests are unreliable (2 fails out of 5) [10:39] * didrocks waits for the link :) [10:42] didrocks: http://pastebin.ubuntu.com/6930475/ [10:42] didrocks: but the notes were fine after all [10:43] ev: so, asac is telling me that there is someone that can rerun the unity8 from your team? [10:43] test* [10:43] bzoltan: hum, I see no unity8 and a lot of tests are missing compared to the dashboard [10:43] bzoltan: not sure about your skip, it doesn't fail on the daily smoke testing for ubuntu-keyboard and such [10:44] bzoltan: I guess you tried on mako, you can refer to http://ci.ubuntu.com/smokeng/trusty/touch/mako/181:20140213.3:20140115.1/6579/ [10:44] didrocks: I skipped everything what failed on a stock image [10:44] bzoltan: they don't fail in what we run everyday though [10:44] see the link above [10:45] didrocks: did you rune from CLI on your machine or you just look at the levitating spacecraft with jedi engineers around it? [10:45] you ran 13 test suites instead of 27 [10:45] bzoltan: we did run them ourself for your release for the past 8 months [10:46] didrocks: I would loooooove to get my dirty fingers on the script you use. Why I can not run the same? [10:46] bzoltan: the landing team is running the APs all the time [10:46] unity etc. are now runn by kgunn and friends more often [10:46] bzoltan: the script that the CI team is using is part of the wiki page that you got linked to [10:46] asac, didrocks: is there any reason why I can not see the exact same script what you use? [10:47] didrocks: this one -> https://wiki.ubuntu.com/Touch/Testing ? [10:48] bzoltan: they run the phablet-test-run command; there is no single script [10:48] asac: guys ... we went thru this already [10:48] bzoltan: however, as i told you, ask folks and update wiki with missing details [10:49] Mirv: can you tell bzoltan how we run APs? [10:49] sil2100: ^^ [10:50] Mirv: sil2100: he says he cannot reproduce a green dashboard [10:50] asac: you still think that "I hold it wrong" right? :) [10:50] bzoltan: i am not thinking anything [10:50] bzoltan: all i see is that i connected you to ogra [10:50] and didnt hear any further complains yesterday [10:50] and you made good progress [10:51] Ok [10:51] asac: I do not complain ... I run the tests... the very same tests I got from Mirv and some of them failed on the stock 181 image ... so I skipped them from the testing of the UITK silo [10:51] bzoltan: i am thinknig you are not working well with the team ... you seem to try to solve things on your own and then ignore them rather than reaching out for help [10:51] bzoltan: yeah, dont skip them [10:51] bzoltan: uitk is central enough that we cant leave any gap open [10:52] its actyally the most central compnoent we have with potential for regressions [10:52] asac: I need 5 minutes f2f with yoou [10:52] sure [10:52] bzoltan: the smoketesting we do actually runs on normal hardware and uses phablet-test-run as well, so it shouldn't fail when ran on the local device ;) This might mean something's wrong [10:52] asac: yes I told bzoltan my method yesterday. I think he's actually running some extra tests that are not on the dashboard. [10:52] asac: https://plus.google.com/hangouts/_/calendar/em9sdGFuLmJhbG9naEBjYW5vbmljYWwuY29t.g04rj4pc565qsh6humb980bt1k [10:52] Mirv: bzoltan: cant you guys just solve it here? [10:53] i really would prefer to be not involved at all [10:53] We're reverting libgcc1, will be sorted soon [10:53] thanks cjwatson [10:53] yay [10:53] cjwatson: thanks! :) [10:53] asac: you are involved [10:53] bzoltan: i have no permissionm for that HO [10:53] asac: as far as I understood everything but notes was already passing now, so it seems it starts to be in order aside from finding out what's wrong with running those tests. I suggested removing /home/phablet/autopilot and rerunning. [10:54] asac: invitation posted [10:55] bzoltan: i am not allowed still [10:55] killed plugin etc. [10:55] bzoltan: https://plus.google.com/hangouts/_/canonical.com/alexander [10:55] try that one [10:55] asac, are you logged in anywhere with your private G+ account ? [10:55] in a HO? [10:55] hangouts dont work anymore if you are [10:56] no, in G+ anywhere ion the same browser [10:56] * ogra_ always has to log out in all tabs where he has his private account in use to use HOs [10:56] (as long as they were started with a company account) [11:00] didrocks: to highlight my point I just closed the click app I installed and the phone is locked [11:00] huh [11:01] davmor2: so maguro is in a bad state on 181? [11:01] smells like it doesnt like the new Mir [11:02] didrocks: no just slow it will unlock again in minute....talking of which [11:02] ogra_: that nexus 7 i flashed yesterday.. can I OTA update it? [11:02] davmor2, can you take a look at top and see if there is any swapping [11:02] davmor2: ok, apart from that, all good? [11:03] popey, once we have official images you will be able to (you need to do it once from the cmdline with system-image-cli to initialize) [11:03] didrocks: yeap good, but that could easily explain why it is dying during autom ation [11:03] ah okay [11:03] davmor2: indeed [11:03] thanks ogra_ [11:03] popey, OTA needs the images on the server indeed :) [11:04] asac: kgunn: I guess we need to take a decision today on maguro (new Mir slowing it down a lot) [11:04] ogra_: give me a minute I'll run top and open and close some apps and see if I can get it back into that state [11:06] ogra_: makes sense when you say it out loud ☻ [11:07] Mirv: have time? [11:08] asac: I haven't had lunch and it's over 1pm, otherwise yes [11:08] so the answer is I guess "depends" :) [11:10] Mirv: can you come now in a HO? [11:10] asac: ok [11:10] https://plus.google.com/hangouts/_/canonical.com/alexander [11:11] Mirv: https://plus.google.com/hangouts/_/canonical.com/alexander [11:11] tvoss: ^^ [11:11] i am in there [11:11] ogra_: ^^ [11:12] didrocks: it seems the spreadsheet works, but I still get the "Ooops" message every time I update some cell... [11:12] didrocks, ogra_: that would explain it. ubunut-loc I'm assuming ubuntu location is using 92% cpu [11:13] davmor2, ouch [11:13] asac, gimme a sec, need to go back to the office [11:13] didrocks: really worrying, but at least it doesn't seem broken completely [11:14] davmor2 again? :/ [11:14] davmor2: ok, can you try to revert what enter in that image one after another? [11:14] What the hell [11:14] davmor2: reboot and look at top again [11:15] didrocks, ogra_: 845 root 20 0 115136 6856 5292 S 101.8 1.0 23:00.74 ubuntu-loc+ [11:15] davmor2: you didn't have that on the last image? [11:17] sil2100: the whole device is slower with nested mir but running the location stuff just doesn't help. [11:18] sil2100: can you help davmor2 to bisect the image, removing one by one what was new on the last images? [11:18] didrocks: ACK [11:18] thanks [11:19] didrocks, sil2100: so no top is looking much healthier. [11:25] didrocks: so even with location off now I would say that maguro is 10-20% slower than it was, without opening an app just moving around the unity scopes and scrolling. [11:25] but now it is flashing las t promoted : [11:25] ) [11:25] Yeah ;) [11:25] didrocks: we want to try last promoted image as a starting point [11:26] why doe sit take 3 years to flash maguro [11:27] biab [11:29] sil2100: sounds good [11:39] davmor2: I wonder if the same was happening in the image before we upgraded Mir, i.e. 2 images ago [11:39] FYI a more completely commented version of how I do testing: http://pastebin.ubuntu.com/6930701/ [11:40] davmor2: since this seems like the problem we had before, and platform-api is a dependency of location-service - maybe another gcc mismatch? [11:41] Looking at the build logs [11:47] davmor2: doesn't seem so [11:47] At least not gcc [11:49] didrocks: http://162.213.34.102/job/landing-010-2-publish/lastSuccessfulBuild/artifact/packaging_changes_camera-app_2.9.1+14.04.20140213-0ubuntu1.diff <- unity8-ap dep addition and icons for desktop, safe [11:50] sil2100: +1 [12:00] davmor2: did it downgrade already? [12:02] didrocks, sil2100: hum, I added a line to CI train this morning that vanished since, do you know what happened? [12:03] seb128: maybe the google issue [12:03] should I just add it back? [12:03] yes please [12:03] interestingly, I still had it before I refreshed the page [12:04] shrug [12:04] I noticed it's still failing a bit in syncing properly [12:04] got an oops again [12:04] grrr, another oops [12:05] seb128: yeah, that's what we are getting since this morning [12:05] well, added the lines, but 2 of the columns gave me oops errors [12:05] line [12:05] thanks seb128 [12:05] seb128: I see it, thanks [12:06] thanks [12:14] morning [12:15] Morning [12:16] hey rsalveti [12:21] ogra_: what do I do wrong -> http://pastebin.ubuntu.com/6930884/ [12:21] davmor2: give me a sign how it goes [12:21] ogra_: nothing happens after that... not a character on the consol [12:22] phablet-config autopilot --dbus-probe enable usually takes a while to finish for the first time [12:24] ogra_: it moved :) and did something not nice http://pastebin.ubuntu.com/6930891/ [12:24] sil2100: ^ [12:25] hm, it seems to want to download the latest UITK from the archive, which he should fetch from the PPA instead [12:25] yeah [12:25] bzoltan: you have the silo PPA added on your device, right? Just in case [12:25] yes [12:25] I'm aftaid phablet-test-run might not be smart enough ;/ [12:26] Mirv,sil2100,didrocks: modulo whatever mirroring may be involved, the libgcc1 thing should be reverted now [12:26] and we're building the real fix [12:26] sil2100, ogra_: I have 0.1.46+14.04.20140212-0ubuntu1 UITK from the silo PPA [12:26] asac, ev, didrocks: mako and maguro are continuing now. Maguro had another device failure and mako was complete except for the unity8 tests didn't run to completion it seems. [12:27] plars: do we konw what stopped the unity8 tests? [12:27] great, cjwatson [12:27] didrocks: not yet, it's a bit chaotic at my house right now (getting 4 kids ready for school) but I'll be able to check on it in a few minutes [12:28] sorry it took longer than it should have done, unfortunately it collided with a battery swap on the lp master db [12:28] cjwatson: thanks :) [12:28] * sil2100 already noticed it might be reverted properly as his build job worked [12:28] plars: thanks! [12:28] cjwatson: thanks as well :) [12:29] sil2100: right I'm back now, sorry m-i-l meds time [12:29] davmor2: ok [12:31] sil2100: ogra_: Mirv: I was using the lines from Mirv and the phablet-click-test-setup --click com.ubuntu.calculator type of commands fail [12:31] bzoltan, check again that you did all of the preparation stuff [12:31] bzoltan: right ;/ I think it wasn't ready for the case of testing a new UITK [12:33] sil2100: before http://paste.ubuntu.com/6930927/ [12:33] Looking at pull-lp-source now [12:33] davmor2: ok, so try this: [12:33] ogra_: is the latest image broken because of the libgcc1? or still good? [12:33] davmor2: could you update all the mir bits on your maguro? i.e. mir packages, platform-api and unity-mir? [12:34] rsalveti, 182 looks ok on my maguro [12:34] great then [12:34] sil2100: after http://paste.ubuntu.com/6930935/ [12:34] well, at least it started, didnt play with it [12:34] davmor2: since I have a hunch that it might be the cause - especially platform-api [12:34] i think davmor2 has some speed issues [12:34] After? [12:34] davmor2: after what? ;) [12:34] ogra_: I had performance issues with mako as well [12:34] sil2100: before enabling location and after [12:35]