[00:02] robru: Any idea what landed in krillin rc-proposed 196? I'm getting weird power results ever since then. [00:02] ToyKeeper: dunno, sorry. [00:02] ToyKeeper: sil should have the changelogs somewhere [00:03] ToyKeeper: apparently this http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/196.commitlog [00:05] robru: Thanks. :) [00:05] you're welcome [00:05] Also, ... it worries me that that seems to be the rev which fixed the dbus UI freezes. [00:11] I wonder why it's just krillin. === _salem is now known as salem_ [00:39] hold on, irc bot ping spam incoming... [00:43] robru: I consider myself spammed… :) [00:43] oh this is just the start! [00:43] actually this isn't half as bad as I'd anticipated [00:45] That sinking feeling when you realize the top bugfix for this release is probably what caused the issue you're investigating. [00:47] :-/ [01:09] oh, there it is === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem === _salem is now known as salem_ === chihchun_afk is now known as chihchun [07:49] robru: out of interest, why trusty packages in overlay? [07:49] something train related? [08:11] woot, train is now self hosting. [08:12] Mirv: oh hey. yeah the train is now self-hosting, so when i want to roll out a train update I have to use the train to do it. those trusty packages are just some backports of packages that are necessary for the train to build in a trusty silo. [08:13] robru: wow you're still up? :-) [08:13] Mirv: those packages shouldn't bother anybody as a) they're trusty packages and b) they're not part of any default seed for anything. [08:13] veebers: only midnight ;-) [08:13] robru: thanks, useful to know! and yes they don't bother anybody. [08:13] robru: lol :-P Hey, maybe you can tell me, how do I change the QA signoff status? I would like to publish my silo now that I've fixed and tested it [08:14] veebers: if you click edit on your ticket it's a drop-down you can pick a value from [08:14] ah, right. Had to be an easy one :-) Cheers [08:14] you're welcome [08:15] robru: awesome, have clicked publish now [08:15] veebers: did it work or do you need an ack? [08:15] robru: I don't think it worked /me checks now [08:16] robru: hah "Publish failed: veebers not authorized to upload autopilot", are you able to help me out? :-) [08:16] veebers: no can do unfortunately. sil should be around soon... or maybe Mirv can do it if it's just a universe package [08:16] Mirv: we now have this hilarious changelog: http://bazaar.launchpad.net/+branch/cupstream2distro/view/head:/debian/changelog [08:17] robru: cheers will ask [08:17] Mirv: are you available to help me out publishing autopilot? :-) [08:33] veebers: sure [08:35] Mirv: awesome, thanks :-) [08:35] veebers: publish done [08:35] no problem [08:36] Mirv: sweet thanks for that. Does that manual acking thing need looked at? I got pitti to ack them in the MP [08:36] veebers: yes, I looked through it, not much to look (adding python-tz to deps) [08:36] Mirv: awesome, thanks again [09:29] dbarth, seb128: I briefly looked at the new package in silo 60 (signon-plugin-sasl) and didn't see any obvious issues [09:30] k, I'm going to have a look [09:30] seb128: could you do a preNEW review of that? Since we don't have a NEW queue in the overlay I would like to know the ubuntu archive opinion earlier than in xenial NEW :) [09:30] Thanks! [09:30] yw [09:35] cool, keep us posted [10:06] sil2100: so just FYI a faulty upload from Kubuntu broke all of KDE autopkgtests so the nice was wasted, pitti has now triggered a rerun of all failed tests after the fix was done... so surprise, more waiting [10:06] s/nice/night/ [10:07] sil2100: and because of that we don't have up-to-date status on whether everything on all other fronts is good. it looks good from Qt+autopkgtest side from what can be understood, but the poppler transition and s390x are mixed to the same soup [10:08] hey trainguards, question, since when do we build on s390x architecture? just got this https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-054/+build/8413690 and i think i've never encountered s390x before... [10:08] sil2100: I asked if the Kubuntu guys could hold any big KDE landings for a while if possible. if now a new KDE comes we can say goodbye to this whole week and probably next too. [10:08] pstolowski: since last night as announced on mailing list [10:08] ;/ [10:09] pstolowski: yeah, slangasek sent out an announcment to the phone ml [10:09] Mirv, sil2100 ah, indeed, looking :). thanks [10:10] pstolowski: surely you'll want the Scopes work on your nearest mainframe, don't you? (in reality s390x can be mostly just ignored for now) [10:10] IBM System Z - now with scopes! [10:10] :) [10:11] pstolowski: train should already be smart enough not to block on s390x failures, let me know if anything explodes [10:12] robru, cool, thank you [10:12] Yw [10:15] pstolowski: yeah it reports unity-scopes-shell as successful even with the s390x failure, good [10:15] robru, yep === vrruiz_ is now known as rvr === greyback__ is now known as greyback === salem_ is now known as _salem === marcusto_ is now known as marcustomlinson [12:42] is there a problem with CI? On https://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-vivid-armhf-ci/1321/console I don't see what is going wrong [12:42] I only see this wrong: /tmp/buildd/ubuntu-ui-toolkit-1.3.1705+16.04.20151120.1bzr1753pkg0vivid1321/tests/unit/tst_units/dpr1/dpr1: error while loading shared libraries: libUbuntuComponents.so: cannot open shared object file: No such file or directory [12:42] but I don't know the cause [12:42] cihelp: ^ [12:48] t1mp: let me take a look [12:48] thanks [12:52] t1mp: i think the failure is due to what logged below 'dh_auto_test in virtual frame buffer failed...' [12:53] t1mp: i remember seeing this in one of the i386 builders before, due to some issues on it. let me try to take a look === _salem is now known as salem_ === chihchun is now known as chihchun_afk [13:25] psivaa: ok, thanks for checking it out. Let me know if you find something. [13:32] t1mp: Looks like there were some 'Xvfb' processes left running and they appeared to have the issue on cyclops-node10 [13:32] I'm running the failed job in another node http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-vivid-armhf-ci/1326/console [13:44] Mirv, can we have a silo with the fix for power consumption and without the desktop fix. As I understand it bug 1523975 is desktop only and has no impact at all on the phone, and I don't want to introduce more risk into 8.5 [13:44] bug 1523975 in qtbase-opensource-src (Ubuntu) "[desktop] system-settings crashes on startup with 5.4.1+dfsg-2ubuntu11~vivid1" [High,New] https://launchpad.net/bugs/1523975 [13:44] OTA8.5 [13:45] jibel: ok, creating another silo [13:45] * Mirv starts to hold world record for silos [13:46] jibel: actually, we don't have such a patch directly in existence [13:46] Desktop regression with OTA-8.5 ? [13:46] looking if one could be created by interdiffing [13:49] sil2100, you need package from the vivid overlay installed on a vivid desktop [13:49] sil2100, system-settings + qt packages from the overlay [13:50] jibel: the system-settings crasher fix is just https://launchpadlibrarian.net/229160772/nmbearer-system-settings-fix.diff - do you want that part to be reverted? the whole interdiff between currently landed and the new on - that check, plus removing of code. I think we'd rather need awe's look on the rest of the patch and decide if it's of any use or not (the wifi part is just "potentially fixing") [13:50] jibel: http://paste.ubuntu.com/13858649/ - I was supposed to link that in the middle [13:53] Mirv, okay, lets wait for Tony's feedback. Meanwhile we are testing the silo as it is. === fginther` is now known as fginther === chihchun_afk is now known as chihchun [15:14] psivaa: did the other job finish running? And should it appear on my MR page? https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/pageHead-sectionsIndex/+merge/279834 [15:14] I don't think I'll get approval to merge that until I have good test results [15:22] t1mp: i had only triggered the failed downstream job. For the MP to get updated, the whole set needs to be rebuilt. [15:22] t1mp: i've triggered it here: http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/2597/ === tvoss is now known as tvoss|dinner [16:19] trainguards, could you show some love to the publisher: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-046/+packages [16:19] trainguards, it's taking ages to complete [16:19] trainguards, where ages means: longer than usual ;) [16:20] uh oh ;p [16:20] tvoss|dinner: I think there's not much we can do here, it's supposed to run periodically, but maybe it's busy with publishing a lot of binaries in the archive [16:21] * tvoss|dinner hugs the poor little publisher :) [16:21] okay, some more dinner then [17:03] t1mp: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/pageHead-sectionsIndex/+merge/279834 is looking good on jenkins now [17:50] tvoss|dinner: We applied a Launchpad database schema patch this afternoon, and that requires stopping long-running jobs such as the publisher for a little while. It's been back for a while now. [18:17] trainguards: Are s390x Xenial build failures expected? https://launchpadlibrarian.net/229503357/buildlog_ubuntu-xenial-s390x.libertine_0.99.7%2B16.04.20151209-0ubuntu1_BUILDING.txt.gz [18:22] ChrisTownsend: given https://launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/5.5.1-2ubuntu1/+build/8388169 i'd guess that anything depending on that would also fail to build, yeah :) [18:22] dobey: Ah, ok, that explains it. Thanks [18:28] jibel, dobey has silo 23 ready === salem_ is now known as _salem === tvoss|dinner is now known as tvoss [20:48] psivaa: cool, thanks for checking it.