[00:11] kenvandine: failed again on quiet_logging branch [00:11] damn [00:12] that's the one that has peer_picker_ui in it [00:12] wtf! [00:12] oh [00:12] peer_picker_ui is still in it [00:12] robru, can you remove that from the config? [00:14] cyphermox,thomi,robru: xnox's changes are in https://code.launchpad.net/~xnox/upstart-app-launch/sync-archive/+merge/209908 [00:14] please just land that as well if you're landing another UAL change [00:21] cjwatson, oh, I already pushed the changes direct to trunk. so that MP is stale / conflicting now. wasn't aware of the MP, sorry [00:22] It would have landed weeks ago if the landing process were remotely functional. [00:23] i see [00:24] kenvandine, sorry remove which from the config? I removed one already.. [00:24] ugh [00:24] robru, which did you remove? [00:24] the only one that should get removed is the peer_picker_ui branch [00:24] which was in that second run [00:24] kenvandine, the one that was conflicting from the previous build run... can't remember the name right now [00:25] but not that one you just said [00:25] peer_details? [00:25] peer_picker_ui looked like the one that failed the first time [00:25] kenvandine, fix_pending_check [00:25] that shouldn't have [00:25] it was a tiny change on top of more_handlers [00:25] it got much further than that [00:25] kenvandine, not sure what you mean? "the first time" http://162.213.34.102/job/landing-014-1-build/36/console i saw fix_pending_check giving conflicts [00:26] oh.. i was looking at the criss cross stuff for peer_picker_ui [00:26] let me merge that into quiet_logging too [00:26] kenvandine, ok, so i'm going to add fix_pending_check back, drop peer_picker_ui, then what? [00:26] robru, so drop peer_picker_ui and give me a minute [00:27] kenvandine, wait, do I add fix_pending_check back or not? [00:29] no, it might blow up again [00:29] ok [00:29] i merged it into quiet_logging [00:29] like bfiller said, we'll get a mamoth MP :/ [00:29] but it works :) [00:29] ok, pushed [00:31] robru, remove peer_picker_ui though [00:31] if you didn't already [00:31] so drop fix_pending_check and peer_picker_ui [00:31] and i think it'll be clean [00:31] kenvandine, ok, those are dropped, i'm kicking the build now [00:34] kenvandine, bfiller : ok here is the latest attempt: http://162.213.34.102/job/landing-014-1-build/38/console [00:38] robru, thx [00:38] kenvandine, you're welcome! [00:38] kenvandine, are we rooming in Malta? [00:38] we can [00:38] :) [00:38] put it on the spreadsheet [00:39] yeah, just got my approval today [00:39] cool [00:39] i'm booked already [00:40] kenvandine, heh, neither of us are in the spreadsheet yet ;-) [00:44] ? [00:44] i was the other day [00:44] robru, oh... look at the second worksheet [00:44] there are 2 weeks [00:44] we are on the second [00:44] ooooooooOOOOOOOOOOOOoooooooooooooh [00:44] hey guys, I got a weird build fail (looks like a write fail) on amd64 in my silo, other arches built OK ... is there a way to restart just that one build, to see if it was a transient error in the builder? [00:45] that explains why there were no names I recognized on the whole thing ;-) [00:45] bregma, should be in the PPA a 'retry build' button if you dig. [00:45] bregma, which silo? [00:45] landing-006 [00:46] robru: he won't have access unless he's in ci-train-ppa-service [00:46] ok, i'm on it [00:46] I don't see the failure though [00:46] oh yes I do [00:47] https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+build/5832899 fyi [00:47] looks suspicious to me [00:47] I guess you mean [00:47] make[3]: *** [generated/glib-2.0/schemas/org.compiz.networkarearegion.gschema.xml] Error 9 [00:48] it's pretty scary if our builders are throwing random write errors, but I guess in this case it's OK to give it another try [00:48] bregma, ok, i restarted it, if you keep watching the jenkins log you should see the status revert from "failed" to "building" (eventually) [00:49] yeah, the usual, and hopefully not continue on to "failed to build" [00:49] bregma, if jenkins says "failed to build", just immediately re-run build with WATCH_ONLY and then it'll see the newer status of that rebuild [00:50] well, I just watch the PPA itself, it tells me everything [00:52] bfiller, woot... it's building in the ppa now [00:53] robru, thx for the help [00:53] kenvandine, you're welcome [00:54] i'm going to disconnect now, before i get tempted to work more :) [00:54] good night all! [01:16] ok, i'm off for dinner, but i'll be back in an hour or so in case anybody needs anything [01:40] cyphermox: you around ? [01:41] robru: ...hey when you get back, can you reconfig silo 4 ...one...more...time.... [01:41] it doesn't like me doing reconfig with those "ubuntu-touch-session" MPs [01:41] wondering what trick you are doing to reconfig without it griping [01:46] robru: i gotta boot into my macos for a bit...i'll check back in about an hour or so [01:48] robru: cyphermox: 249 finished, just those two calendar app errors on mako so I'm going to rerun those. hopefully they will not be reproducible [01:50] ok [01:52] robru: reconfiguring silo 4... [01:54] cyphermox, thanks [01:54] just got back [01:54] well, it's failing... [01:54] http://162.213.34.102/job/landing-004-0-reconfigure/14/console [01:56] i... what [01:57] weird huh [01:57] cyphermox, try again? maybe it's a connection issue [01:57] i mean that's a standard MP. it's not like i did anything that would change that. [01:58] some issue with launchpad [01:58] thomi, !!!! omg i'm so sorry that took all day. i just confirmed the trunk resync was successful and now published autopilot! [01:59] robru: that's awesome news! :-) [01:59] veebers, will you be around in an hour? that's usually how long it takes for stuff to get through proposed, then I can merge & clean, then I can assign your next silo... but I might need to be reminded because i seem to be easily distracted and forgetful today [02:00] robru: yep, it's only 3pm for me :-) [02:00] veebers, oh sweet, you australian or something? 7PM here, I'm EOD, but I've got things to do ;-) [02:00] robru: Close, New Zealand :-) [02:00] nice [02:01] robru: I presume you'll be around on my Tuesday morning? (um, probably your Monday afternoon right?) [02:01] veebers, i should be, yeah. [02:01] i'm taking off early friday for a weekend trip but i should be back monday no problems [02:02] robru: coolio, if you're not around in an hour I might hold off and get a silo on my Tues, save holding a silo over the weekend (it's Friday arvo here) [02:02] robru: wooo! thanks man [02:03] thomi, you're welcome! [02:03] veebers, ok no worries [02:04] cyphermox, hmmm what happened in silo 4? [02:05] the what? [02:05] it's the one that is broke for reconfig [02:06] oh right. sorry I was just looking at the most recent *build* log error and got confused [02:08] yeah, it's still failing anyway [02:08] need to ask ops. [03:13] robru: I see the M&C job running - thanks :) [03:13] was just about to kick it off myself :) [03:13] thomi, you're welcome! do you have some MPs to snag a new silo with? [03:14] veebers: ^ ? [03:14] I did this release, it's veebers turn to feel the pain for the next one :) [03:14] haha [03:15] veebers, I'd recommend jumping into a silo now, even if you don't test until next week -- i predict silos will be hard to come by next week... [03:18] robru: I guess he's AFK for a second [03:19] no worries. lunch or dinner perhaps? [03:20] I predict: coffee break [03:20] it's 4:20 PM [03:20] robru: hey, sorry was running tests [03:20] thomi: :-) [03:20] bah.. was close... [03:20] thomi, I've had lunch at 4PM some days ;-) [03:20] robru: one moment I'll update the spreadsheet [03:20] veebers, great [03:24] robru: Thanks for the heads up. I've setup line 49. [03:24] veebers, great, i'll assign it now [03:25] robru: Even if silos are hard to come by, it won't be hard to reconfigure right? i.e. I might need to add a MR for gallery-app [03:25] robru: awesome, thank you [03:25] veebers, nope, reconfigs are trivial [03:26] robru: sweet [03:26] veebers, ok, you got silo... wait for it... 3! ;-) [03:26] veebers, are you able to kick the build yourself? or do you need me to? [03:27] robru: nice :-) thanks again [03:27] robru: I can kick the build [03:27] veebers, you're welcome! [03:29] ahhh, it feels so good to pass the "release autopilot" baton to the next person [05:04] morning [05:16] I'll build the landing-015, since it seems like a good idea to have testable asap [06:14] Mirv, good morning [06:14] Mirv, don't panic, but I published autopilot today. I tested it for at least 5 hours. it looked really good [06:24] robru: PANIC!! [06:24] robru: ok, sounds good :) [06:35] cyphermox, around? [06:35] cyphermox, if so, can I get a silo for line 43? [06:36] tvoss: I'm not good enough for you!? :) [06:37] that said, we're full in silo usage (regarding the limits we've set to ourselves), let's see if something could be freed [06:37] Mirv, oh, you are around :) sorry for that :) [06:38] Mirv, I'm just looking for an available silo-dealer :) but my needs will not be fulfilled I guess [06:41] tvoss: I try to get that one tested line published and I'll let you know when dbus-cpp could have a chance [06:41] Mirv, yup, thank you [06:52] mandel: hi, it was pointed out at #ubuntu-devel that the QML plugin dependency is too strict - or is it on purpose? [06:53] mandel: I mean, are you planning to break ABI on purpose without bumping the library soname? [08:04] Morning [08:11] \ [08:12] I mean, hm, why did robru publish autopilot? Didn't he get the e-mail and didn't read the meeting summary? [08:14] sil2100: he said not to panic in the morning, and that he had tested it for at least 5h before publishing and that it looked really good [08:15] and... morning! [08:16] Mirv: smoketesting looks ok, just it's really unwise to land risky things like autopilot while we're in the state 'do not publish anything besides fixes' [08:16] Mirv: since even if you test everything, you never know if it won't introduce additional flakyness or the likes [08:17] For me stopping the line means stopping the line ;) [08:24] sil2100: yeah, it's not without risks I agree, not sure why he wanted it in (well, of course it's nice to always to get stuff in, just hard to be 100% sure nothing breaks) [08:26] Mirv: this time it's a no-issue, but for the future I would really like to avoid that [08:34] sil2100: autopilot landing worked well? [08:35] hmm. dont see it in 250 [08:37] sil2100: I'm now running the UITK tests for double-testing to spot regressions. it's for the notes-app, I believe that's something that should go in since it's a 5.2 regression? (even though notes-app was workarounded) [08:38] sil2100: meanwhile, I've the updated indicator-datetime installed too. not sure about that one, I didn't have much alarm success but it looks like the branches are supposed to fix real bugs [08:38] Mirv: is it in the blocker list? [08:38] Mirv: for now don't land anything that's not fixing the blockers, so even UITK I would not move [08:39] asac: it was on the blocker list earlier, but then workarounded. so yeah it can be postponed. [08:39] sil2100: true, that [08:39] right [08:39] cool [08:39] sil2100: finally, thomas would like to have a silo for line 43, but we're out of silos [08:39] asac: I don't see the changes file for 250 on ogra's machine, but from my calculations it should be in 250 [08:39] sil2100: do you know where we are on the blockers? [08:40] sil2100: you are right. thta one is missing [08:40] I think we're at the point that Savi_q is sleeping and he filed upstream bug report in the night [08:40] asac: I just read all the e-mails and checked the bugs, and as Mirv mentioned there's an Qt upstream bug filled in and some insight on the LP bug as well [08:40] We would have to wait for upstreams to wake up and comment how they want to proceed [08:40] then the alarms problem alone seems complex, and that's why I'm asking about indicator-datetime - there's the general event issue, and then bugfixes that claim to now have branches [08:41] But it seems that most issues are related ;/ [08:41] sil2100: we cant solve this on our own? [08:41] asac: by upstreams I mean our upstreams [08:41] ah [08:41] Like, Saviq and kgunn ;) [08:41] I built indicator-datetime in the morning with those branches, but since the event issue is also there I'm uncertain how to test the branches properly [08:41] sil2100: ic... those guys are always laggers :P [08:41] hehe [08:42] sil2100: feel free to give the indicator-datetime a whirl [08:42] excuse me! [08:42] Mirv: let me try then, I'll just reflash my device to latest [08:42] Saviq: :O ! Awake already?! [08:42] sil2100, for an hour now :P [08:43] * sil2100 shocked [08:43] ;) [08:43] seems ogra's bot is more unreliable than our AP tests [08:43] guess thats a good thing [08:43] hehe [08:43] heh ;p [08:43] after all we get some maturity into this stuff [08:43] FWIW I'm running full AP suite with both UITK and indicator-datetime updated, so if everything passes that's at least additional data point in addition to actual manual testing [08:43] afaik the trainbot died two days ago already :) [08:43] Saviq: anyway, do you have any ideas on how to proceed with this Qt-event-stopping bug? [08:43] and that doesnt do mcuh :) [08:44] sil2100: well there was the ugly hack to refresh Mir once a second... [08:45] Mirv: sounds like a promotion candidate then! :D [08:45] ;p [08:45] haha === WebbyIT is now known as rpadovani [08:45] seriously, I guess it depends how deep the change of behavior in Qt is, ie. is it really that the events handling can't be just forced somewhere where wanted [08:46] ANyway, seriously, I don't know much about Qt5 insides, but it's strange that this happens for like music and such, but for instance phone calls on a screen turned off still works [08:46] sil2100, yeah, am waiting for QML upstream to show up and comment [08:46] Saviq: are you on #qt-labs? [08:46] Mirv, yes [08:46] Mirv, talked with thiago yesterday, and they did see this behaviour as weird [08:46] but referred me to Alan [08:47] Saviq: if you want to have additional data points, there is ppa:canonical-qt5-edgers/backup-qt511 and I could provide with an apt line to downgrade eg. a chroot:s environment to it [08:47] ie Qt 5.1.1 built against trusty [08:47] I had that done in December [08:47] Nice :) [08:47] Mirv, let me try, I'll be fine with the versions I think [08:48] Convinient! [08:48] ok [08:48] sil2100: /me likes backups, you never know when they might be useful [08:54] Mirv, hmm, libicu48 not there :/ [08:55] Saviq: let me try it and possibly give some ugly hacks [08:56] Mirv, so I'm down to http://pastebin.ubuntu.com/7129585/ [08:57] * Saviq tries to force this in [08:57] Mirv, sil2100 a silo for line 51 would be highly appreciated :) [08:57] Saviq: first one being wget 'https://launchpad.net/ubuntu/+source/icu/4.8.1.1-13+nmu1ubuntu1/+build/5185636/+files/libicu48_4.8.1.1-13%2Bnmu1ubuntu1_amd64.deb' [08:57] Mirv, the latter pulls in -dev packages for some reason [08:58] or maybe my apt-cache foo is wrong [08:59] Mirv, I'm fine it seems [09:00] Mirv, yup, same in 5.1.1 [09:00] Saviq: \o/ dist-upgrade in my chroot still running. I was thinking about apt pinning [09:00] Saviq: aha, so it has changed already there... [09:00] * Saviq marks [09:01] useful data to upstream too [09:01] Mirv, hey, thanks for the silos/starting the build/adding the commit messages [09:02] seb128: you're welcome [09:02] Mirv, I'm doing testing now, giving the silos back then hopefully [09:03] Created: [09:03] Today 12:25 AM [09:03] Updated: [09:03] Today 10:02 AM [09:03] no, that's not confusing _at all_ [09:04] Saviq, you found a way to go back in time to update things before they get created? ;-) [09:04] Saviq: there's only small part of the world you need to convince to leave 12h clock behind :) [09:04] tvoss: bad news! We're in *that* mode again, which means we don't assign any silos for anything that's not a blocker fix [09:04] seb128, Mirv, yeah [09:05] I always need to read the Wikipedia article on the am/pm stuff [09:05] especially the part of what 12:00am meant [09:05] so simple http://en.wikipedia.org/wiki/12-hour_clock#Confusion_at_noon_and_midnight [09:06] Mirv, what do you mean, it's obvious that after 12:59 it's 1:00, isn't it? ;) [09:06] Sooo obvious [09:07] Saviq: yes, it's obvious that after 12:00pm it's 12:01 am and then at some point 01:00, at least according to one interpration :) [09:07] Mirv: sil2100: May I ask for a silo to proceed with the line nro 13? [09:07] bzoltan: TRAINCON-0 announced by asac on the mailing list [09:08] assigning silos would be possible, though, but we're out of them as well [09:08] bzoltan: sadly we are very low on silos right now... [09:08] probably in 1-2h there'll be silos available [09:09] uh, need to reflash my device again [09:09] Mirv: may I put some extra MRs on the silo16 then? [09:10] bzoltan: hehe, actually yes you can, since that's not going in either since it's not anymore a blocker after notes-app was workarounded [09:11] Mirv: ohh... nice :) should we just add the line 13 to that silo and reconfigure? [09:11] bzoltan: yeah I think so [09:11] thostr_: ping [09:11] Mirv: thanks mate :) [09:11] and modify the description [09:11] sil2100: pong [09:11] thostr_: I see charles prepared a merge fixing the #1295237 blocker? [09:11] https://code.launchpad.net/~charlesk/indicator-datetime/lp-1295237/+merge/212021 [09:12] thostr_: do we have a landing for that? Is this a final fix? [09:12] Mirv: ^ [09:12] sil2100: yep [09:12] Mirv: ah, I see now it's part of the datetime landing [09:12] sil2100: that's what I asked you to give a whirl to [09:13] thostr_: ok, so it's in a silo now but with some other fix, nvm then! [09:13] charles told be that cyphermox was already silo'ing it [09:13] sil2100: the other fix is the fix Charles pointed out in the bug report that is on the blocker list [09:13] thostr_: sil2100: yep, cyphermox did the silo and I launched a build in the morning so it's ready to be tested from there [09:14] in total charles has three patches: https://code.launchpad.net/~charlesk/indicator-datetime/lp-1295271/+merge/212028, https://code.launchpad.net/~charlesk/indicator-datetime/lp-1295237/+merge/212021 and https://code.launchpad.net/~charlesk/indicator-datetime/lp-1293646/+merge/212056 [09:15] the first 2 are in silo 15 [09:16] sil2100, Mirv: is that fine if I add the third one and reconfigure/rebuild? or do you want to get the touch fixes through and do another landing for the desktop fix later? [09:17] seb128: let's do another landing later, since this way we won't have to wait for a rebuild now and simply test and publish [09:17] seb128: if that's fine with you [09:17] sil2100, ok, can you help testing it? [09:17] seb128: yes, just finishing re-flashing ;) [09:17] sil2100, sure, if you don't tell me the other landing is going to be blocked because the lockdown :p [09:19] seb128: pfff ;p [09:19] sil2100, can you please kick rebuild in https://launchpad.net/~ci-train-ppa-service/+archive/landing-004/+build/5833499 ? [09:19] or well, "try again" [09:20] Saviq: sure [09:31] ogra_: hello! Are you coming? :) [09:34] mhr3, do you watch your silos? you have one failing to build and one woth "code cleanup" waiting to be tested since yesterday morning at least [09:35] Mirv, I have read your comment in the MR and it makes sense [09:36] mandel: did you read the last one too? :) [09:37] mandel: so it seems it's not something required to be changed. now we just have the TRAINCON-0 so I'm afraid even with it ready for publishing we can't publish it [09:37] Mirv, just did.. ok, so it looks like is not a huge problem then [09:37] Mirv, indeed, I read asacs email and I know the current situation, we will have to wait [09:38] mandel: let's keep in the silo and ready to be published at moment's notice. [09:38] Mirv, is not a blocker for me atm and I have talked with the browser people and they are not yet in the point where they are going to be using it, os we are ok [09:39] Mirv, keeping the silo is awesome :) [09:42] seb128, i do [09:42] mhr3, so fix your build or give the silo back ;-) [09:43] seb128, the testing failed and i already warned Wellark that the indicator stuff needs to move [09:44] the last promoted image still uses 5.0, right? [09:44] Laney, yup [09:44] NEAT [09:44] 237 iirc [09:44] this is handy for testing behaviour differences [09:44] we should keep one around [09:45] we keep the promoted ones [09:45] Laney, what do you test? the tz stuff? [09:45] ya [09:45] cool, I assumed you would [09:45] pretty sure it worked before [09:45] but who knows [09:45] I'm 90% sure it did work correctly [09:46] I was wondering what changed [09:46] qt :P [09:46] but now that you mention it, it's probably qt5.2 :p [09:46] I though we used datetimed there [09:46] although the report doesn't say what version it was [09:46] yes, to change the tz [09:46] well, I get the issue on current trusty desktop [09:46] but then there's a call to tell qml that it has changed [09:46] Date.timeZoneUpdated() [09:46] k [09:47] it's a bit weird [09:47] like I'm utc+1 [09:47] if I pick SF it gaves me california as utc+2 [09:47] if I pick Paris back it gives me france as utc-8 [09:47] e.g it's one step behind [09:47] maybe the order of signals changed or something [09:50] Morning all [09:50] signals done seem to be a strength of Qt 5.2 :P [09:50] *don't [09:53] Laney, btw, you should be able to test click updates now :p [09:54] yeah it works for me on that image [09:54] that's both good and bad at the same time :P [09:57] davmor2: so, ppa:ci-train-ppa-service/landing-015 if anything, and upgrade indicator-datetime from it :) [09:57] sil2100, indicator-datetime seems fine to me, but I'm unsure how to trigger the original bug so I can't really confirm that's fixed [09:58] seb128: I'm trying to do it right now, but I asked davmor2 (who reported it) to give it a spin as well [09:58] good [09:58] As he knows the best how to trigger it [09:58] seb128: thanks for testing! [09:58] yw! [10:00] sil2100, seb128: right my phone is now flashed so let me make sure I can replicate on the new image and then I'll look at installing the ppa and seeing if the fix solves the issue [10:00] davmor2: thanks! [10:13] right reproduced now to install the ppa [10:22] FYI I've not seen regressions from indicator-datetime in full AP suite so far, 3/4 done or so [10:22] one calendar app AP fail but that has happened before too [10:24] Mirv: general dogfooding also didn't reveal any problems here, although I'm having a hard time doing the testing as mentioned on the bug ;) [10:24] Mirv: I guess davmor2 will give us a definite +1 on if the issue is fixed [10:27] ToyKeeper: nice round of bugs you have. I mean, those seem like more cornercase problems but definitely something that people will eventually hit if not kept on radar. [10:30] being a beta tester of jolla these kind of problems seem quite familiar. now they're non-beta, but still some similar bugs there, which is not surprising given the complexity of a phone. [10:35] sil2100, seb128: Okay so I seem to be able to dismiss alarms now \o/ :) [10:36] davmor2, great! [10:39] davmor2: yessss! [10:39] davmor2: actually, on my device every alarm attempt I made was dismissable [10:39] Mirv: you want to do the honor of publishing inidicator-datetime? ;) [10:40] sil2100: so testing has concluded? mine _just_ finished as well, no regressions. [10:40] yeah I got a simple reproducer [10:41] dateTimeUpdated() seems buggy [10:41] I mean timeZoneUpdated [10:41] * Mirv hears if what Laney is saying is somehow related to indicator-datetime landing [10:42] it's a qt problem [10:43] Mirv: it's a different issue, related to TZ's [10:44] sil2100: ok. so changing Tested to be yes as per davmor2 and publishing then. [10:44] Mirv: you can publish indicator-datetime as it is now anyway I guess [10:44] \o/ [10:45] indicator-datetime published [10:46] sil2100, Mirv, davmor2: thanks [10:47] davmor2: adb shell ls /opt/click.ubuntu.com/com.ubuntu.calculator - what do you see? [10:47] http://paste.ubuntu.com/7129959/ [10:48] popey: root@ubuntu-phablet:/# davmor2@stryder:~$ adb shell ls /opt/click.ubuntu.com/com.ubuntu.calculator [10:48] ls: cannot access /opt/click.ubuntu.com/com.ubuntu.calculator: No such file or directory [10:48] wat [10:50] Saviq, hmm, i just worke up my mako and the shell is dead .... indicators work, switching apps work, the launcher shows if i swipe from the left, but the shell itself is stuck on the application lens and i cant move it [10:50] ogra_, right, I think I encountered that once or twice, it felt like mouse input isn't delivered [10:50] (lockscreen works too) [10:50] popey: root@ubuntu-phablet:/opt/click.ubuntu.com# ls -al [10:50] total 8 [10:50] drwxr-xr-x 2 clickpkg clickpkg 4096 Mar 21 03:17 . [10:50] drwxr-xr-x 3 root root 4096 Mar 21 09:26 .. [10:51] ogra_, edges are different 'cause they deal with touch events [10:51] davmor2: is this a clean device you have just flashed? [10:51] ogra_, but everything else deals in mouse events and it looks like that gets b0rked [10:51] popey: yeap and then added a ppa and opened calculator [10:51] hmm, k [10:51] ogra_, I didn't find a way to repro, though :/ [10:51]