[00:12] robru-sick, hey, are you the only one doing slots? Given that you are sick [00:15] kgunn, looks like it merged on it's own, and yes I should be eod === fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3 | Known Issues: - [00:22] robru-sick, can I cancel sot 3 (as it's blocked) and get a slot for L47? [00:28] sergiusens, sure [00:30] robru-sick, one more for l48 as well; which is desktop as well [00:30] sergiusens, can they be in the same silo? we're a little short right now [00:30] robru-sick, I guess; even if not related [00:30] but also not exclusive [00:30] sergiusens, yeah, would be easier for us. [00:31] want me to bundle? [00:31] sergiusens, yes please [00:32] robru-sick, done [00:33] sergiusens, thanks. just waiting for silo 3 to finish purging [00:34] robru-sick, going to retry that one once unity8 can land again, should I leave that comment? [00:35] sergiusens, sorry what? [00:35] robru-sick, what used to be in silo 3 is going to get retried as soon as stuff can land freely again [00:36] sergiusens, oh right, yeah you can change the comment to be more meaningful. thanks. [00:37] sergiusens, ok, you got silo 3, please build. [00:37] thanks [00:38] you're welcome [00:49] robru-sick, btw, do you have perms to mark https://code.launchpad.net/~ps-jenkins/goget-ubuntu-touch/trusty-proposed as abandoned or mature? [00:49] oh wait [00:49] that's train [00:50] no former daily release [00:50] nvm [01:15] sergiusens, yeah, and I don't have permissions on that account ;-) [01:30] robru-sick: I need to drop one of the MR's from silo 2 request, what's the best way to do that? [01:32] robru-sick: I've taken it out of line 36 already [02:17] bfiller_afk, sorry, i can do that now [02:20] bfiller_afk, rebuilding for you since you're afk [03:19] bfiller_afk: yeah dropping is a reconfigure with a complete rebuild as robru-sick did [03:19] or is doing [05:14] asac: ping [05:15] asac: I have dropped a mail to you and to a bunch of people... not a big drama, but I would like to understand what I do wrong. [05:16] robru-sick: hello there... what was with the linenumber 35 landing ask? I marked it "No" and I commented there why I do not like it ... why it was processed? [05:19] asac: at the same time I have an MP with 13 branches [08:02] brb, need to jump out for a moment [08:06] didrocks: ping [08:06] bzoltan: pong [08:07] didrocks: I put you to the To: in my mail... I am confused and so worried a bit [08:07] didrocks: no big drama, but I wish to understand what just happened [08:07] bzoltan: there is nothing new, I'm not sure why you are raising the same thing again [08:07] apparently, you already pinged asac at the time [08:08] he and I sent an email to robert about it [08:08] didrocks: because an MR landed without our approval [08:08] and he excused and understood what happens [08:08] bzoltan: right, what you raised 3 days ago? [08:08] bzoltan: but it was already landed [08:08] didrocks: yes... and the MR is merged now. [08:08] bzoltan: yeah, it was already pushed [08:08] as I told you [08:08] didrocks: without testing? [08:08] (or if you read the phone ML emails) [08:08] apparently he did the sdk testing [08:09] so yeah, appart from emergency, this shouldn't happen, as told 3 days ago [08:09] but it was already too late [08:09] already in proposed [08:09] as my 3 last emails on the phone ML is telling [08:10] didrocks: How did it land? The tests were not marked as "done" on the Silo sheet [08:10] the only thing that changed is that it reached the release pocket (because of beta freeze) [08:10] bzoltan: right, again, same thing than 3 days ago [08:10] not sure why you reraise the same issue as it's the one that happened 3 days ago [08:10] didrocks: I still do not get it... how and why an MR lands what is not tested? [08:11] grumble [08:11] do you read the phone ML? [08:11] or not? [08:11] seems not :/ [08:11] didrocks: I do [08:11] well, so as told there [08:11] 3 days ago, robert did land a renato's fix for alarm clock [08:11] you raised it then [08:12] asac and I poke him to get more details [08:12] and he apologized to not have followed the process [08:12] but the thing was already published [08:12] and stuck in proposed [08:12] (as told in my emails) [08:12] the only thing which changed since yesterday is that it reached the release pocket [08:13] didrocks: I still do not understand why robru-sick lands anything from renato and what do we do to avoid it in the future? [08:13] bzoltan: human error, he thought that was proposed by a sdk team member [08:13] and he tested it before landing [08:14] didrocks: Human error to land an MP without tests? [08:14] bzoltan: seems so [08:14] didrocks: the Silo sheet said that "testing done" - No [08:14] bzoltan: yeah, and I raised it [08:14] he didn't flip the switch [08:14] which is an issue [08:15] didrocks: Human error to create a silo for for an MP not requested by the lander? [08:15] bzoltan: any lander can land other components in case of emergency and the primary lander isn't there [08:15] didrocks: human error not to check if the MR is approved? [08:15] but they are taking the risk and accept responsability [08:15] bzoltan: yeah [08:16] didrocks: this is 3 human errors with one case. [08:16] and? [08:16] what's your point? [08:17] didrocks: what do we do to avoid it in the future... you made a very strict and riggid (and so good) CI process. What good it is if people can just do shortcuts whenever they need so? [08:17] bzoltan: we need then to educate people [08:17] so that it doesn't reproduce [08:17] rather than arguing on the same issue than happened 3 days ago [08:17] nice you have time for that, I don't though [08:17] didrocks: I am not arguing [08:17] I've already take actions [08:17] as told [08:17] 3 days ago [08:18] the landing didn't create regressions, hopefully [08:18] (or we would have revert) [08:18] and fixed an issue [08:18] didrocks: it did for us [08:18] bzoltan: which regression, do you have a bug? do we need to revert? [08:20] didrocks: I pull zsombi|afk in to explain [08:20] just point me to a bug report === zsombi|afk is now known as zsombi [08:20] and tell me if I need to revert [08:20] but then, you have to fix the alarm quickly [08:20] and only the alarm [08:20] or I'll have to revert sdk even more [08:20] as your latest landing created that regression [08:21] didrocks: what regression was created by what? [08:21] didrocks: I don't get this... [08:21] bzoltan: https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1282129 [08:21] Ubuntu bug 1282129 in Ubuntu Clock App "Clock and calendar tests fail with static void QOrganizerEDSEngine::itemsAsyncListed(ECalComponent*, time_t, time_t, FetchRequestData*) " [Undecided,New] [08:21] bzoltan: that's what they tried to fix apparently [08:22] didrocks: yes, but it WASN'T a regression! [08:22] zsombi: it was, we didn't get the crash before and we got it then [08:23] didrocks: they wanted to increase the performance as alarms fetching was slow [08:23] seems that some tests started to fail because of that [08:23] zsombi: so, what regression did it create to you? [08:23] didrocks and you haven't seen the crash before? that code in SDK wasn't changed for ages, so how was it a regression? [08:23] zsombi: no, we haven't seen the crash before in the daily testing at least [08:24] didrocks: with the fix you cannot fetch alarms that are created to a due date > 7 days [08:24] zsombi: hum, but you did approve yesterday the MP? [08:24] so you approved (even if it was after it landed) a regression? [08:24] didrocks: my previous MP was tested against the calendar_app and it gave green light. [08:25] didrocks: but for the Clock app this is NOT a regression, because there you cannot create > 7 days alarm anyway [08:25] zsombi: what on the image is creating a 7 days alarm and have tests? [08:25] didrocks I approved so the fix can go to MWC if needed, and we are already working on the fix [08:25] ok, so sounds you know how to fix it [08:26] and no urgency to revert that one [08:26] as nothing on the image is using the > 7 days, right? [08:26] didrocks yes, I know... believe me approving the MR was a compromise I had to take... I was completely against it, but we had to do this... so no App should be affected, maybe test cases are. [08:27] you have tests that are failing? [08:27] didrocks: what bothers me was that the MR wasn't top-approved, and was still taken. [08:27] zsombi: this is what I discussed with bzoltan 3 days ago [08:27] happy that the SDK team can talk about the same issue for 3 days [08:27] but meanwhile, there is an image that I need to go back to green, so I don't have the luxury [08:28] and speaking of which, the Qt crash raised 4 weeks ago to your team [08:28] didrocks: we do not have any tests failing, atm [08:28] and dimissed by "we are going to switch to 5.2" is now hitting us badly [08:28] zsombi: you should probably then test that [08:28] and how can we speek for 3 days on teh same topic if the whole stuff got landed today? [08:29] zsombi: it was already in 3 days ago [08:29] read the phone ML [08:29] didrocks: yes, I'm adding more tests to alarms now as we speek [08:29] great [08:29] from 25.02.14: [08:29] 10. The alarm creating issues on clock apps (Robert). [08:29] -> Half of the fix is in the release pocket, the other half (the sdk part) is stuck in proposed due to beta-freeze. Robert is looking if that can goes to the release pocket. [08:29] didrocks: I did... and I found the first occurrence about this MP yesterday, on the 25.02.14 landing mail... [08:30] zsombi: it was posted 2 days ago [08:30] as the fix landed 3 days ago [08:30] today is 27th, so only 2 days are gone since then :) [08:30] (well 2.5) [08:30] zsombi: right, but this is a recap email [08:30] and bzoltan started to speak about it at the 25 in the morning [08:31] when it was already landed [08:31] didrocks: and still went in... [08:31] zsombi: it WAS in [08:31] didrocks: I have flagged out the problem with that MP before 25.02 and before that mail... [08:31] and you say that landing caused image not to be green? [08:31] bzoltan: ? [08:32] 2014-02-25 08:44:47 bzoltan didrocks: In the Self service CI (CI train) I watched the line nro 38 with some surprise. Does robru know that the UITK [08:32] releasing belong to me and my team? He was about to release an MR what was not even approved yet. [08:32] bzoltan: ? [08:32] I hope you don't infer I'm changing the dates on my logs? [08:32] oh, let's take public logs even [08:32] didrocks: the sheet did not say that it was landed ... the mail did not say it was landed. [08:32] if you don't trust me [08:32] bzoltan: it said it was migating to destination [08:33] so in the proposed pocket [08:33] didrocks: I do trust you... I wish to understand where from I should have known that it was landed? [08:33] * didrocks looses time for prooving bzoltan that he spoke on the 25 [08:33] no no [08:33] seems you don't agree [08:33] so, let's get public logs [08:33] didrocks: m,an, I branched the trunk yesterday, and the FIX wasn't there... how come it landed on 25th then? [08:33] zsombi: you should learn how ubuntu is working… [08:33] didrocks: dude, I remember I talked to you... I just wonder why my words were ignored. [08:34] bzoltan: they were not [08:34] man [08:34] bzoltan: http://irclogs.ubuntu.com/2014/02/25/%23ubuntu-ci-eng.html#t07:44 [08:34] so do you still say "09:31:37 bzoltan | didrocks: I have flagged out the problem with that MP before 25.02 and before that mail..."? [08:34] or do you infer I cheated on the public logs as well? [08:35] I don't have access to irclogs.ubuntu.com if you ask me === zsombi is now known as zsombi|afk [08:36] didrocks: I still do not get how something can land when the Silo tests are not done. My only problem is that I see the CI Train sheet and I see the IRC ... and it seems that an MR just landed on a shortcut without giving me any visibility [08:37] bzoltan: you don't answer the question… [08:37] when did you flag it BEFORE the 25? [08:37] didrocks: I meant that line what you just linked [08:37] asac: (about your questions yesterday evening): 001 is CSS files and removing some private APIs for HTML5 apps; very self-contained if you want to land/purge the silo [08:37] bzoltan: ok, so, it was the 25 [08:37] not before the 25 [08:37] Back [08:37] so now, let's get back in time [08:37] and rehash again [08:38] as it seems you don't know what a pocket is and don't read the phone mailing list [08:38] in the european night, between the 24 and 25 [08:38] robert did land that MP [08:38] without flipping the testing done to yes [08:38] then, it was in the proposed pocket [08:38] didrocks: I read the mails and yes I have no idea what the pocket is... I take that an MP is not landed before the Silo sheet has green cell on the testing line. [08:38] "migrating to destination" [08:38] in the spreadsheet [08:38] once it's in proposed, it's in ubuntu [08:38] it's too late [08:39] the package was blocked in proposed due to beta freeze [08:39] (not just for a couple of hours, but a day) [08:39] then, you raised it to me [08:39] asac and I sent an email to robert [08:39] and he apologized and thought renato was on the sdk team [08:39] testing was done by him and nicholas [08:40] I reported that the component was blocked in proposed in my 25.02.14 email [08:40] then, it was unblocked from proposed and so migrated to the release pocket [08:40] and lands into an image [08:41] what I reported on the 26.02.14 email [08:41] so again, nothing was pushed/changed since you raised it [08:41] s! [08:41] as I'm explaining it to you for the past 35 minutes… [08:41] didrocks: I admit I did not pay attention to "migrating to destination" because I thought that if an MP line has no testing plan and not asked by the lander and the tests are not flipped inthe Silo ... then it does not land. [08:41] bzoltan: not if you force the publication [08:41] bzoltan: people has to push "publish" [08:42] then, if they do not follow rules… [08:42] so that was part of that email we sent as well [08:43] all clear now? [08:43] didrocks: from the mail I understood that the SDK part is "stucked" due to the freez ... and I was happy to see that, because the MP was bogus anyway [08:43] bzoltan: stuck in proposed [08:43] but it means, already in distro [08:44] didrocks: I do not know what is "proposed" sorry for that [08:44] bzoltan: yeah, you should learn after working on ubuntu for months now how the distro is working [08:44] didrocks: That is true... I should [08:45] didrocks: sorry, by watching the sheet and reading the mails I was under the impression that this MR is not landed yet. [08:46] bzoltan: they had "migrating to destination" is when things are moving to distro [08:46] didrocks: I do admit that I am not fully at home with the distro lingo [08:46] that's what I didn't use the pocket name in that "migration" sentence [08:46] so the sheet was telling it was already published (just didn't hit the final destination) [08:46] didrocks: "migrating to destination" I ignored because I could not imagine something landing on the distro without tests and without the lander [08:47] bzoltan: well, as told, other people can land your work, that's why you have a wiki page [08:47] but that should be in coordination with the primary landers [08:47] and the landing team shouldn't take that decision apart from extreme cases [08:47] and testing was done [08:47] the switch wasn't flipped [08:48] (4th time…) [08:48] didrocks: I am not that stupid :) [08:48] didrocks: sorry if you think I waste your time... [08:48] why are you repeating the same sentence over and over then? [08:48] bzoltan: well, you can help getting us back to green now [08:49] bzoltan: remember that qmlscene crash that was dismissed because rare 4 weeks ago (crash in v8 engine)? [08:49] didrocks: what can I do for you? [08:49] seems (as you probably saw on the phone mailing list), that it's all over the place now [08:49] didrocks: yes [08:49] I'm afraid of adding on top of the android 4.4 migration the Qt 5.2 ones [08:50] so I guess we should really invest in a wokaround at least [08:50] workaround* [08:50] so any help to get that one down will be really a tremendous gain [08:50] * didrocks adds this example on his "I told you to not ignore it, it will strike us back" bag :) [08:51] (bzoltan: last word on the sdk landing, I archived it in case you are looking for it as everything landed, it's in the archive tab, same spreadsheet) [08:53] didrocks: OK, I will see what can I do with that qmlscene... thanks for explaining the whole story of the mess ... [08:54] bzoltan: no worry, just trust me for next time that I don't try to do anything on your back. If I told you I dealt with it, it's really that I dealt with it :) [08:54] didrocks: you I do trust ... [08:54] and if you see a landing you didn't expect, just poke me, not sure we need to "escalate" or whatever before gathering further infos [08:55] bzoltan: to come back on this qmlscene crash (in the V8 engine), I only see the multithreading/scheduler changing in android 4.4 getting us into that situation way more… === psivaa-afk changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3 | Known Issues: - [09:31] popey: where are you? we miss you! :) [10:05] sil2100: yeah, invite me if you have a hangout pls === psivaa-afk is now known as psivaa [10:10] popey: hi! psivaa will just send me the test-executing script from the dashboard for now [10:14] sil2100: ok === zsombi|afk is now known as zsombi [10:32] sil2100, hey there :) [10:35] didrocks: oh, one thing I forgot - the idea was to do direct syncs from Debian for the majority of Qt modules - this clashes with the PPA preparation idea.. [10:35] sil2100, is l22 not getting a silo due to the freeze? (indicator-datetime bugfixes, for issues that impacts mostly the desktop though) [10:35] didrocks: the list is at https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjuCdq68GSyVdFI4QzNQdWpfME5aMEV2VXo0cUpOMkE#gid=19 [10:36] didrocks: the alternative is not to do so but use ubuntu1 for everything like I've done in the current PPA already [10:36] you can sync to PPAs [10:36] Laney: \o/ [10:36] Mirv, please don't do that, what Laney said [10:36] lp:ubuntu-archive-tools copy-package [10:36] Mirv: yeah, if it's ready already from debian side, please do that :) [10:36] excellent [10:36] Mirv: is it already in? [10:36] thank you, thank you [10:37] didrocks: yes, I checked today that everything we need was put to Debian experimental during my vacation [10:37] excellent [10:37] so yeah, start the sync :) [10:37] tell me if you need any help with copy-package [10:37] is the no landing rule still on? [10:38] Laney: for stuff in touch? yep [10:38] Laney: see the ML ;) [10:38] it's too hard to keep track [10:38] yeah, so I upload qtbase and then four syncs, one upload, sync, two uploads, 10 syncs.. something around that [10:38] because the status updates are just in random emails [10:38] Laney: random emails? [10:38] can you put it in a /topic somewhere? [10:38] Laney: all my emails start with it? [10:38] "Landing team xx.yy.zz" is pretty random to me [10:38] didrocks, is l22 blocked by your freeze? [10:38] Laney: date of the day [10:39] seb128: desktop bug reports, I would say no [10:39] good [10:39] thanks [10:39] * seb128 waits for sil2100 to be around [10:39] Laney: read at least the first 3 lines, I've been careful to state it as the beginning of each email [10:39] "Not a lot to add compared to this morning status email, we still hold the line on touch landings which are not targeting fixing the current image issues. " [10:40] " Some desktop only update are still flowing in through CI Train, however, we are still blocked by not being able to get one image promotable." [10:40] 'we are still blocked' is the key there? [10:40] seb128: I can assign it ;) [10:40] didrocks, I think his point is that having to catch emails is not as convenient as a dashboard/topic [10:40] sil2100, thanks [10:40] seb128: when I saw it I was thinking 'uhh, ok, desktop only but still - indicators' [10:40] Laney: yeah [10:40] seb128: well, we need a web ui for the landing [10:40] stating that [10:41] but we need to have the CI work on it [10:41] /topic in here or touch would be ok for me [10:41] right [10:41] I don't have /topic rights here I think [10:41] here isn't locked [10:41] touch is, don't know why [10:41] not any more! === didrocks changed the topic of #ubuntu-ci-eng to: "Ubuntu CI Engineering Team | Vanguard: psivaa | CITrain support - US: robru, [10:42] hum [10:42] ! [10:42] haha [10:42] Ooooo [10:42] Didier broke the topic! [10:42] RUN FOR YOUR LIVES === didrocks changed the topic of #ubuntu-ci-eng to: "Ubuntu CI Engineering Team | Vanguard: psivaa | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3. Landing frozen for Touch until we get one promotable image | Known Issues: -" [10:42] Oh, it's back again [10:42] Nevermind [10:42] no fun :p [10:42] ;) [11:25] didrocks: so it looks like unity8 is locking up randomly, also shutting down bluetooth from the indicator kills the phone reboot into unity8 which I though was a qt5.2.1 issue but it seems not. There is a bug assinged to qt5.2.1 for the bluetooth issue and the random lock ups is being worked on already I think [11:25] didrocks: other than that 210 seems okay [11:27] didrocks: I'm assuming that the unity8 random locks ups won't help the autopilot tests either so if you get some that fail on ci but pass on rerun/local that might be a cause [11:28] davmor2: do you have a bug for the random locks up (which happens even with qt 5.2.1), and who is working on it? [11:29] om26er: psivaa: any news on the screen unlock? :) [11:30] didrocks: no this isn't on qt5.2.1 this is on standard, I didn't see the lock up on qt5.2.1. But I'm assuming it would effect 5.2.1 I just didn't hit it. Let me dig into it I'm sure I have heard talk of it though [11:30] didrocks: just saw om26er :) [11:31] didrocks: https://bugs.launchpad.net/bugs/1277206 this is the bluetooth bug [11:31] Ubuntu bug 1277206 in unity8 (Ubuntu) "QT5.2: Disabling bluetooth crashes unity8" [Undecided,Confirmed] [11:31] davmor2, does it only crach the UI or the phone as a whole ? [11:32] ogra: it only seems to relaunch unity8 [11:32] phew, fine then :) [11:32] ogra, didrocks: it looks like it only happens on a first run after a fresh flash too [11:33] I couldn't reproduce after re-enabling bluetooth [11:33] hmm, interesting [11:34] I'm going to reflash it so I have a clean slate and see what info I can get about it [11:37] davmor2: ok, so maybe your lock up is linked to the crash we have :) [11:37] phew [11:37] * didrocks was afraid of another issue [11:38] didrocks: could be [11:38] well, might be intersting to see if an extra reboot in the test runs would fix it [11:39] probably something in the session isnt completely set up on first boot that causes this [11:39] i assume we immediately start testing without any additional reboot [12:00] didrocks: so on initial start up there is a crash for _usr_lib_arm_linux_gnueabihf_upstart-app-launch_desktop-hook.32011.crash I'm guessing that isn't the start you want. However I've cleared that off as I want a nice clean slate for the bluetooth killer [12:01] didrocks: I'm assuming it might be the start guide [12:01] davmor2: can you retrace that one? [12:02] didrocks: no I killed it but I can reflash in a minute and do it then [12:02] davmor2: that would be awesome! [12:02] ogra: on flo the screen unlocking for ubuntu-system_settings had failed on my rerun as well. so kicked it again. [12:03] thanks [12:03] the frequency of screen unlock issues appears to be more on flo [12:03] * sil2100 fights his phone [12:06] psivaa: so, the plan is om26er to add more debug infos and running it? (or give the utah script so that he can reproduce?) [12:06] didrocks: still waiting to hear from om26er. just received an email from him saying starting late today [12:07] ok [12:17] psivaa, flo is faster and more responsive than mako [12:17] i actually assume that many of these issues we see are because android 4.4 is also significantly more responsive than 4.2 was [12:18] so timing critical things that didnt race before might now ... [12:18] ogra: yea that would make sense. [12:19] so indirectly didrocks is right in blaming android 4.4 ... but after all it only exposes breakage in our tests that didnt show up due to slowness before [12:20] ogra: yeah, see why we shouldn't never give up on races :) [12:20] it would help if we could ask unity8 if the screen is actually unlocked and get a proper response for this [12:20] right [12:20] didrocks: is there a wiki page/documentation on how to get a good traceback my google-fu seems to be off this morning [12:21] "Debugging" on the ubuntu wiki ? [12:21] davmor2: https://wiki.ubuntu.com/DebuggingProgramCrash [12:21] iirc thats the top level page [12:21] yeah [12:21] didrocks: cheers [12:22] davmor2: for using gdb itself, maybe pair with sil2100? [12:22] that will be way faster :) [12:22] sil2100: mind helping davmor2 to retrace a crash? [12:23] What's up? [12:23] * sil2100 reads up [12:23] sil2100: I get this on a fresh flash _usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash [12:25] isnt that just a script ? [12:25] didrocks: looks like the bluetooth issue might be a race issue. I'm assuming to do with what needs to be displayed and removing the indicator from the top bar. [12:25] you should be able to read it with an editor [12:25] ok ;) [12:32] psivaa: do you think ogra should try the unlock screen script? I don't have flo, tried unlocking 10 times the screen for mako without success [12:32] in case: [12:32] http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/files/head:/utils/target/ [12:33] download unlock_* [12:33] chmod +x both [12:33] and run the .sh as root [12:33] didrocks: I think the freq is high in flo. so it would help === alan_g is now known as alan_g|lunch === cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3. Landing frozen for Touch until we get one promotable image | Known Issues: - [13:18] morning [13:18] hey hey [13:19] ogra: so in the end the crash has nothing to do with 4.4.2 [13:19] good and bad news [13:20] well, it seems to expose some races due to 4.4 being more snappy i think [13:20] good is that this is not happening with qt 5.2, bad is that we got another crash there [13:20] ogra: yeah, I believe so === pete-woods is now known as pete-woods-lunch [13:20] * ogra curses his maguro [13:20] it endlessly reboots ... [13:20]