[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #739: FIXED in 7 min 27 sec: http://kci.pangea.pub/job/mgmt_merger/739/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #724: FIXED in 7 min 31 sec: http://kci.pangea.pub/job/mgmt_progenitor/724/
[00:20] <acheronuk> santa_: problems?
[00:21] <santa_> acheronuk: nope. dry-run sucessful, I'm about to start the real run(TM)
[00:22] <acheronuk> you doing all 3 dists? 
[00:23] <santa_> acheronuk: no, my idea is staging for zesty and taking care of backports tomorrow or so
[00:23] <santa_> once the thing is built for zesty
[00:23] <acheronuk> good point
[00:24] <santa_> the reason is that we might need to make some adjustments, so this way we won't have to backport each time we cahnge something
[00:24] <santa_> * change
[00:25] <santa_> acheronuk: ok, about to start the real thing, I already pushed the package metadata to KA so you should be able to do your thing in parallel
[00:25] <acheronuk> right
[00:27] <santa_> acheronuk: btw if you are going to merge the frameworks and qt dev maps into plasma, you should delete the overrides file
[00:27] <santa_> acheronuk: i.e. dev-package-name-lists/plasma-zesty-overrides.json
[00:29] <acheronuk> oh. didn't know that was a thing
[00:30] <acheronuk> santa_: so 'dev-package-name-list -d zesty -r plasma -m qt frameworks' ?
[00:31] <acheronuk> i.e. can the -m take both arguments?
[00:31] <santa_> acheronuk: yes, I think that should get you the correct thing
[00:31] <santa_> yes, I think so
[00:32] <santa_> acheronuk: oh, one thing more
[00:32] <santa_> I have a newer pkg-kde-tools
[00:32] <santa_> with a couple of bugfixes from debian
[00:33] <acheronuk> where?
[00:33] <santa_> maybe I could upload it to the frameworks staging ppa so we will get the thing rebuilt against that?
[00:33] <santa_> let me check what I have
[00:35] <santa_> acheronuk: it's in our git repo for pkg-kde-tools, also I made a complete test rebuild of frameworks 5.27 plasma 5.8.3 and apps 16.04.3 against it
[00:38] <santa_> acheronuk: so if you don't mind I'm going to upload this to frameworks staging, and once it's built we can upload frameworks and plasma
[00:38] <santa_> we have time while we do the do-all gbp-nr
[00:38] <acheronuk> ok
[00:40] <santa_> ok, uploaded
[00:40] <santa_> hopefully it will be built before the do-all gbp-nr is completed
[00:42] <santa_> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages?field.name_filter=pkg-kde-tools&field.status_filter=published&field.series_filter=
[00:44] <acheronuk> santa_: readme.ng doesn't mention do-all bump-build-dep-versions ?
[00:45] <acheronuk> is something else doing that now?
[00:45] <santa_> acheronuk: gbp-nr does that automatically (it uses the same code)
[00:46] <acheronuk> santa_: cool. I was hoping it was something like that.
[00:46] <santa_> the reason to have the option of running it separately is to repair things which went wrong
[00:46] <santa_> for instance an incorrect maps update or so
[00:46] <acheronuk> got it
[00:47] <santa_> if fact we used it for that purpose with apps 16.04.3, d you remember?
[00:47] <santa_> s/d /do /
[00:48] <acheronuk> vaguely 
[00:49] <santa_> we did :)
[00:49] <santa_> there was a wrong buld dependency map, we corrected it and we rebuilt all the apps with the correct bumping
[00:50] <santa_> ok, do-all gbp-nr ended sucessfully here, uploading to staging...
[00:59] <acheronuk> ok. ready to upload here
[00:59] <DarinMiller> finally home from work....
[00:59] <santa_> pushing to git as we speak...
[01:00] <santa_> acheronuk: done, now wrt fw 5.28 it's all waiting and running kubuntu-retry-builds
[01:01] <DarinMiller> Excellent.  I try to take the afternoon off for the next one.   I wanted to see the full process...
[01:01] <wxl> DarinMiller: i got screwed cuz we don't have outbound access here over 2203 :(
[01:02] -kubuntu-ci:#kubuntu-devel- Project merger_kactivitymanagerd build #285: FAILURE in 21 sec: http://kci.pangea.pub/job/merger_kactivitymanagerd/285/
[01:02] <DarinMiller> Same issue at Micron (where I work).
[01:02] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-sdk build #676: FAILURE in 16 sec: http://kci.pangea.pub/job/merger_plasma-sdk/676/
[01:02] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-nm build #849: FAILURE in 15 sec: http://kci.pangea.pub/job/merger_plasma-nm/849/
[01:02] -kubuntu-ci:#kubuntu-devel- Project merger_discover build #206: FAILURE in 20 sec: http://kci.pangea.pub/job/merger_discover/206/
[01:03] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-workspace build #1002: FAILURE in 20 sec: http://kci.pangea.pub/job/merger_plasma-workspace/1002/
[01:03] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-pa build #543: FAILURE in 15 sec: http://kci.pangea.pub/job/merger_plasma-pa/543/
[01:03] -kubuntu-ci:#kubuntu-devel- Project merger_libkscreen build #868: FAILURE in 12 sec: http://kci.pangea.pub/job/merger_libkscreen/868/
[01:04] -kubuntu-ci:#kubuntu-devel- Project merger_kdeplasma-addons build #897: FAILURE in 13 sec: http://kci.pangea.pub/job/merger_kdeplasma-addons/897/
[01:04] -kubuntu-ci:#kubuntu-devel- Project merger_kwin build #1027: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_kwin/1027/
[01:06] <wxl> DarinMiller: also, cool. what do you do for micron?
[01:06] <DarinMiller> wxl: I can't even use konversation at work as the IRC ports are blocked.  But I can use webirc....
[01:08] <wxl> DarinMiller: get yourself a cloud host and do ssh forwarding :) i assume you can go out on 22?
[01:08] <DarinMiller> wxl: I wor in photo handling automation and number crunching projects.
[01:08] <wxl> DarinMiller: oooo!
[01:08] <DarinMiller> ^work
[01:10] <DarinMiller> wxl: basically I am a photo engineer who loves computers and the automation of tedious tasks, aka: hacker
[01:11] <wxl> niiice
[01:11] <wxl> how does one apply engineering to photos exactly?
[01:11] <acheronuk> santa_: forgot how slow my upload was! should have done it on linode
[01:11] <DarinMiller> sounds like santa_ has some cool new scripts!
[01:12] <wxl> git checkout cool-new-scripts
[01:12] <wxl> nope
[01:12] <santa_> nah, they are the same we used in the latests stagings, they just have some improvements and we fixed a few bugs on them
[01:12] <DarinMiller> wxl: In semiconductor terms, photo the is one of several areas of process to create a semicon. chip.  We uses expensive cameras to print the small circuits.
[01:13] <wxl> DarinMiller: oh wow, that's super cool!
[01:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_pause_integration build #7: ABORTED in 1 hr 35 min: http://kci.pangea.pub/job/mgmt_pause_integration/7/
[01:32] <DarinMiller> wxl: I imagine bike manufacturing is also a blast!
[01:32] <acheronuk> santa_: all uploaded
[01:32] <wxl> sure is DarinMiller :)
[01:37] <DarinMiller> OK. So I am lost.  I thought plasma 5.8.4 was just uploaded.... but I don't see it here... http://qa.kubuntu.co.uk/ppa-status/plasma/
[01:37] <DarinMiller> Maybe needs time to refresh?
[01:37] <santa_> we didn't update the status pages yet
[01:38] <DarinMiller> Oh, that's a manual update?
[01:39] <santa_> nope, we just need to set that in a configuration file for the new versions
[01:42] <DarinMiller> Are the corresponding .json files maintained by hand?  Those look a bit daunting... (http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.8.3_zesty.json)
[01:43] <santa_> no, all of that is generated automatically with 'ppa-build-status' from Kubuntu Automation
[01:43] <wxl> well, automatically, once you run the script manually XD
[01:44] <DarinMiller> :)
[01:44] <santa_> well. that script is being run by cron
[01:44] <wxl> oh nevermind
[01:45] <acheronuk> it just grabs part of it's config from out git
[01:45] <santa_> so to update the status pages we just need to do this https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=78a180a9fdeecf94f64d58bb5dd3696f1c627c08
[01:45] <wxl> being the lowly packager here, i'll ask by what mechanism the upload actually happens
[01:46] <santa_> a different thing is preparing the changes for a new upstream release, pushing them to git and uploading the built packages to the ppa's
[01:46] <IrcsomeBot1> <tsimonq2> *YAWN*
[01:46] <IrcsomeBot1> <tsimonq2> Hai guys :)
[01:47] <DarinMiller> g'morning tsimonq2! :)
[01:47] <IrcsomeBot1> <tsimonq2> Evening
[01:47] <wxl> tsimonq2: what is the primary channel you go to for lxcontainer support?
[01:47] <acheronuk> night
[01:48] <IrcsomeBot1> <tsimonq2> wxl: stgraber :P
[01:48] <wxl> bah
[01:48] <IrcsomeBot1> <tsimonq2> What do you tell me, wxl?
[01:48] <IrcsomeBot1> <tsimonq2> R
[01:48] <IrcsomeBot1> <tsimonq2> T
[01:48] <IrcsomeBot1> <tsimonq2> F
[01:48] <IrcsomeBot1> <tsimonq2> M
[01:48] <IrcsomeBot1> <tsimonq2> :P
[01:49] <wxl> yeah when there is a manual with relevenat information
[01:49] <wxl> otherwise, no!
[01:49] <mparillo> !paste
[01:49] <ubottu> For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic.
[01:49] <IrcsomeBot1> <tsimonq2> Bah
[01:50] <IrcsomeBot1> <tsimonq2> wxl: Don't you use that awesome DDG thing? Besides, I have never needed help with it.
[01:50] <wxl> if it was resolved that easily i wouldn't be asking
[01:51] <IrcsomeBot1> <tsimonq2> Can't you find an IRC channel over DDG?
[01:51] <IrcsomeBot1> <tsimonq2> #lxc? ##lxc?
[01:51] <wxl> i find about a billion
[01:51] <IrcsomeBot1> <tsimonq2> Try one dude!
[01:51]  * wxl facepalms
[01:51] <wxl> next time, try this: "i don't know"
[01:51] <IrcsomeBot1> <tsimonq2> Fine :P
[01:52] <wxl> btw nevermind ddg when there's /msg alis list *lxc*
[01:52] <IrcsomeBot1> <tsimonq2> Lol
[01:52] <IrcsomeBot1> <tsimonq2> K
[01:52] <wxl> do you know about alis?
[01:53] <IrcsomeBot1> <tsimonq2> Yeah
[01:54] <DarinMiller> acheronuk: how did you generate the package name list (https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=52874430f4420bc119f38464c27dada4d91a0651)
[01:56] <acheronuk> ran the script 'dev-package-name-list -d zesty -r plasma -m qt frameworks'
[01:57] <wxl> DarinMiller: https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/README.ng#n54
[01:59]  * wxl is stepping out musically
[01:59]  * wxl is listening to Try My Robe by Goat ♫ https://www.last.fm/music/Goat/_/Try+My+Robe
[02:03] <DarinMiller> acheronuk:  ahhh, I see, all the magic starts with:  kubuntu-automation/conf/versions.json
[02:05] <ahoneybun> acheronuk: for Gwenview we have the new Importer now in KF5
[02:05] <ahoneybun> but that will be the next release after 16.12
[02:07] <DarinMiller> ahoneybun: all we need to do is fix the 4th line in kubuntu-automation/conf/versions.json and bob's our uncle.
[02:07] <DarinMiller> applications":"16.04.3"  -> applications":"16.12.1"   :)
[02:08] <ahoneybun> maybe lol
[02:08] <ahoneybun> that's a huge jump
[02:08] <DarinMiller> But packages are not ready yet... http://download.kde.org/stable/applications/
[02:09] <ahoneybun> I'm wondering if we can move to 16.08.3 for now then
[02:10] <IrcsomeBot1> <tsimonq2> We don't
[02:10] <IrcsomeBot1> <tsimonq2> We cant
[02:10] <IrcsomeBot1> <tsimonq2> *can't
[02:10] <acheronuk> not for PIM, anyway
[02:11] <DarinMiller> PIM the monster.  Good theme for a horror movie?
[02:13] <acheronuk> DarinMiller: PIM dependency map http://weegie.edinburghlinux.co.uk/~jr/tmp/PIM.png
[02:13] <IrcsomeBot1> <tsimonq2> That's outdated tho. :P
[02:13] <acheronuk> and that is an old version. it's more complicated now!
[02:14] <acheronuk> tsimonq2: yep
[02:14] <acheronuk> 'monster' is about right
[02:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #75: STILL FAILING in 1 hr 1 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/75/
[02:16] <DarinMiller> acheronuk: Yep, that's why I called it the monster.  If I remember correctly, it just about killed Scarlet on the 16.04 release....
[02:26] <wxl> omg look what's on this album!
[02:26]  * wxl is listening to Ubuntu by Goat ♫ https://www.last.fm/music/Goat/_/Ubuntu
[02:26] <IrcsomeBot1> <tsimonq2> What? Lol
[02:26] <IrcsomeBot1> <tsimonq2> What's it about? The OS or philosophy?
[02:27]  * wxl facepalms
[02:27] <IrcsomeBot1> <tsimonq2> ?
[02:27] <wxl> o'
[02:28] <wxl> i'll give you one guess 
[02:28] <acheronuk> night all
[02:28]  * acheronuk goes ZZZZzzzzz....
[02:28] <IrcsomeBot1> <tsimonq2> Philosophy
[02:28] <IrcsomeBot1> <tsimonq2> o/ acheronuk
[02:28] <wxl> OMG YOU GOT IT RIGHT
[02:28] <wxl> I"M TOTALLY AMAZORD
[02:28] <DarinMiller> nite acheronuk
[02:29] <IrcsomeBot1> <tsimonq2> (Document) https://irc-attachments.kde.org/A409cFvV/file_1255.mp4
[02:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #37: STILL UNSTABLE in 1 hr 14 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/37/
[02:46]  * ahoneybun thinks his harddrive is going to fail soon
[02:47] <IrcsomeBot1> <tsimonq2> Ooooooooooooooooooooh
[02:47] <ahoneybun> it's making some noise
[02:47] <ahoneybun> has been for a few days
[02:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #298: STILL FAILING in 1 hr 40 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/298/
[02:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #23: STILL UNSTABLE in 1 hr 40 min: http://kci.pangea.pub/job/zesty_unstable_kopete/23/
[02:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #291: STILL FAILING in 1 hr 39 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/291/
[02:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #98: STILL UNSTABLE in 1 hr 39 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/98/
[02:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #122: STILL UNSTABLE in 1 hr 39 min: http://kci.pangea.pub/job/xenial_unstable_kopete/122/
[03:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #76: STILL FAILING in 1 hr 7 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/76/
[03:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #292: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/292/
[03:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #299: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/299/
[03:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #333: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/333/
[05:11] <ahoneybun> since when did our version of Akregator remove Ubuntu related news?
[05:11] <ahoneybun> well Kubuntu mostlu
[05:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kapidox build #23: FAILURE in 4 hr 1 min: http://kci.pangea.pub/job/zesty_unstable_kapidox/23/
[05:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #42: FAILURE in 4 hr 1 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/42/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kapidox build #164: FAILURE in 4 hr 1 min: http://kci.pangea.pub/job/yakkety_unstable_kapidox/164/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_extra-cmake-modules build #169: FAILURE in 4 hr 1 min: http://kci.pangea.pub/job/yakkety_unstable_extra-cmake-modules/169/
[05:52] <tsimonq2> santa_: https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=252512bcb881fe1727cfd9b9b381bdb6adfb5c0f
[05:54] <santa_> tsimonq2: ok, looks good to me
[05:54] <santa_> tsimonq2: related to that, are you running kubuntu-retry-builds right now?
[05:55] <santa_> are you?
[05:59] <IrcsomeBot1> <tsimonq2> Was
[05:59] <IrcsomeBot1> <tsimonq2> Now I sleep
[05:59] <santa_> against plasma
[05:59] <IrcsomeBot1> <tsimonq2> Problem?
[05:59] <IrcsomeBot1> <tsimonq2> Yep
[05:59] <santa_> well, you are perfoming unintentionally a DoS
[06:00] <IrcsomeBot1> <tsimonq2> Oh shoot :(
[06:00] <IrcsomeBot1> <tsimonq2> Was
[06:00] <IrcsomeBot1> <tsimonq2> Done now
[06:00] <IrcsomeBot1> <tsimonq2> Really sorry
[06:00] <santa_> no prob man :)
[06:00] <santa_> look https://launchpad.net/%7Ekubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages?field.name_filter=&field.status_filter=published&field.series_filter=zesty
[06:01] <santa_> extra-cmake-modules isn't built yet
[06:01] <santa_> it's waiting in the queue
[06:01] <santa_> e-c-m is used by everything in frameworks and plasma
[06:01] <IrcsomeBot1> <tsimonq2> Fair enough
[06:02] <IrcsomeBot1> <tsimonq2> Please rerun kubuntu-retry-builds when that's done. :)
[06:02] <santa_> therefore we have to wait a bit until everything gets in dep-wait
[06:02] <IrcsomeBot1> <tsimonq2> Ok
[06:02] <santa_> because if you run it continuosly you are going to hinder the e-c-m build like forever
[06:02] <IrcsomeBot1> <tsimonq2> Night
[06:02] <IrcsomeBot1> <tsimonq2> I see
[06:03] <santa_> good night, sleep well
[06:03] <IrcsomeBot1> <tsimonq2> o/
[06:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreen build #252: FAILURE in 27 min: http://kci.pangea.pub/job/xenial_unstable_kscreen/252/
[07:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreen build #253: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kscreen/253/
[08:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #331: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/331/
[08:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:47] -kubuntu-ci:#kubuntu-devel- Project merger_kwin build #1028: FIXED in 21 sec: http://kci.pangea.pub/job/merger_kwin/1028/
[08:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:51] -kubuntu-ci:#kubuntu-devel- Project merger_kactivitymanagerd build #286: FIXED in 19 sec: http://kci.pangea.pub/job/merger_kactivitymanagerd/286/
[08:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:54] -kubuntu-ci:#kubuntu-devel- Project merger_libkscreen build #869: FIXED in 20 sec: http://kci.pangea.pub/job/merger_libkscreen/869/
[08:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #138: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/138/
[08:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:58] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-workspace build #1003: FIXED in 21 sec: http://kci.pangea.pub/job/merger_plasma-workspace/1003/
[09:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:05] -kubuntu-ci:#kubuntu-devel- Project merger_kdeplasma-addons build #898: FIXED in 25 sec: http://kci.pangea.pub/job/merger_kdeplasma-addons/898/
[09:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:10] -kubuntu-ci:#kubuntu-devel- Project merger_discover build #207: FIXED in 24 sec: http://kci.pangea.pub/job/merger_discover/207/
[09:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #305: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_kstars/305/
[09:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:13] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-nm build #850: FIXED in 20 sec: http://kci.pangea.pub/job/merger_plasma-nm/850/
[09:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kapidox build #24: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_kapidox/24/
[09:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kapidox build #165: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_kapidox/165/
[09:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #43: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/43/
[09:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_extra-cmake-modules build #170: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_extra-cmake-modules/170/
[09:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:16] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-pa build #544: FIXED in 21 sec: http://kci.pangea.pub/job/merger_plasma-pa/544/
[09:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #231: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/231/
[09:21] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:21] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-sdk build #677: FIXED in 18 sec: http://kci.pangea.pub/job/merger_plasma-sdk/677/
[09:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #67: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/67/
[09:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #243: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/243/
[09:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #231: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_cantor/231/
[09:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #20: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/20/
[09:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #219: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/219/
[10:26] <acheronuk> morning :)
[11:27] <mamarley> No wonder this is taking so long, half the builders are disabled: https://launchpad.net/builders
[11:31] <yofel> the queues are practically empty though
[11:34] <mamarley> The amd64 and i386 queues both have over 200 jobs in them.
[11:48] <acheronuk> yep. LP is struggling on the amd64/i386 queue. was last night even before we staged or let KCI run again I think 
[11:55] <yofel> well, we could increase the timeout to 6 or so
[11:56] <yofel> 30min is not that much of a wait, even if it feels long today.
[12:06] <BluesKaj> Hi folks
[12:33] <acheronuk> tsimonq2: is that you doing the retry script?
[12:34] <tsimonq2> acheronuk: Yep...
[12:34] <tsimonq2> :|
[12:34] <acheronuk> please don't for now
[12:34] <tsimonq2> santa_: Before the Launchpad team tells us that our accidental DoSing is bad, please put some sort of delay in that script.
[12:35] <tsimonq2> acheronuk: Already done... :|
[12:36] <acheronuk> some of the tier1 frameworks on things like arm64 etc, are held up as -dev packages they need also depend on -data packages that the backlogged amd64 builds haven't mage yet
[12:36] <acheronuk> *made yet
[12:38] <acheronuk> so until certain parts or most of that amd64 backlog builds it's missing tier 1 stuff, retying is a bit pointless
[12:44] <IrcsomeBot1> <tsimonq2> Oh jeez
[12:49] <IrcsomeBot1> <tsimonq2> Sorry everyone, didn't realize Launchpad was THAT backed up...
[13:01] <acheronuk> gonna be a long day waiting for that to clear I think
[13:02] <acheronuk> hi blaze 
[13:02] <blaze> hi acheronuk 
[13:18] <mamarley> Until those builders get back on-line, it probably isn't going to clear at all.  The queue is longer this morning than it was last night.
[13:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kapidox build #25: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_kapidox/25/
[13:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kapidox build #166: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_kapidox/166/
[13:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #44: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/44/
[13:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_extra-cmake-modules build #171: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_extra-cmake-modules/171/
[14:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #333: UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/333/
[14:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #334: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/334/
=== palasso_ is now known as palasso
[16:27] <santa_> tsimonq2: well, you can't use that script happily, without thinking, pretending it doesn't schedule a few hundred re-builds
[16:27] <santa_> you just can't abuse the script running it continuously like that
[16:28] <santa_> https://launchpad.net/builders
[16:28] <santa_> 171 available build machines, 49 disabled and 66 building of a total of 220 registered.
[16:29] <santa_> there was a peak of 95 buildds disabled
[16:29] <santa_> before you started to run the script abusively there was *4* disabled buildds
=== greyback is now known as greyback|afk
[16:30] <santa_> and I bet the buildds disabled are disabled because they got too many failed builds
[16:49] <IrcsomeBot1> <tsimonq2> :(
[16:52] <santa_> the good news is that this unintentional DoS like usage can be reduced
[16:52] <santa_> not introducing a delay, but doing something better
[16:53] <santa_> I'm going start to work on that in ~ 1 hour
[16:53] <santa_> but I need your cooperation
[16:54] <santa_> tsimonq2, acheronuk: I need you to NOT run kubuntu-retry-builds until further notice. ok?
[16:56] <IrcsomeBot1> <tsimonq2> OK fair enough
[16:56] <IrcsomeBot1> <tsimonq2> I didn't mean to cause harm :(
[16:58] <santa_> I know, they are various overlapping problems here, and you are not the only one XD
[16:58] <santa_> we will figure it out, don't worry
[17:01] <IrcsomeBot1> <tsimonq2> Yay, builders being disabled are not my fault. :)
[17:02] <santa_> are you sure?
[17:02] <acheronuk> [16:59] <cjwatson> tsimonq2: not your fault
[17:03] <acheronuk> [17:00] <cjwatson> tsimonq2: lcy01's openstack infrastructure has been having some difficulty and is down for the time being; the rest is certainly worse than usual, but I don't have time to look today, I can just re-enable and hope
[17:03] <acheronuk> the retries can't have helped, but not root cause it seems
[17:03] <santa_> well the lcy01 seemed to have problems before we started
[17:04] <santa_> "the rest is certainly worse than usual, but I don't have time to look today"
[17:04] <IrcsomeBot1> <tsimonq2> Exactly so not my fauk5
[17:04] <IrcsomeBot1> <tsimonq2> *fault
[17:04] <IrcsomeBot1> <tsimonq2> I just made it a PITA for anyone else to build things...
[17:04] <IrcsomeBot1> <tsimonq2> :/
[17:05] <santa_> that's not conclusive - my bet is that they are disabled automatically when they get so many build failures in a row
[17:05] <santa_> anyway, we have to improve this, as I said do NOT run the retry builds
[17:06] <santa_> there's one thing true and it's that the retry script is pretty dumb
[17:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #171: ABORTED in 3 hr 21 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/171/
[17:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #31: ABORTED in 3 hr 21 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/31/
[17:07] <IrcsomeBot1> <tsimonq2> OK, please someone disable KCI's nightly until the other builders are back!
[17:07] <IrcsomeBot1> <tsimonq2> Let's only sparingly upload things
[17:08] <IrcsomeBot1> <tsimonq2> Good deal santa_ and acheronuk?
[17:08] <santa_> we can pause the KCI I guess
[17:08] <shadeslayer> Launchpad doesn't disable builders if you spam it  too much
[17:09] <shadeslayer> or if there are too many failiures
[17:09] <santa_> ok
[17:09] <acheronuk> santa_: we can see about KCI later. if needed
[17:10] <IrcsomeBot1> <tsimonq2> See, proves it even more. Less blame for me! :)
[17:10] <IrcsomeBot1> <tsimonq2> I really hope the release team doesn't do a mass archive test rebuild... :P
[17:11]  * acheronuk kicks tsimonq2 for tempting fate
[17:12] <mamarley> Hopefully they would see that the build system is already struggling and hold off.
[17:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #116: FAILURE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/116/
[17:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeconnect-kde build #100: FAILURE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-kde/100/
[17:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #27: FAILURE in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/27/
[17:18] <IrcsomeBot1> <tsimonq2> Lol acheronuk
[17:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #117: FIXED in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/117/
[17:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeconnect-kde build #101: FIXED in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-kde/101/
[18:08] <acheronuk> Architecture 	Builders 	Queue
[18:08] <acheronuk> amd64 	59 	318 jobs (1 hour 10 minutes) 
[18:08]  * acheronuk gives up
[18:10] <mamarley> At this rate, by the time FW 5.28 gets built, 5.29 will be out!
[18:12] <IrcsomeBot1> <tsimonq2> Well I don't know about THAT
[18:14]  * mamarley slaps lcy01 around a bit with a large trout.
[18:31] <acheronuk> santa_: looks like those builders are not coming back in a hurry, so I've set KCI not to trigger tonight. should not need to pause it as the timer is set to exclude tonight
[18:38] <santa_> acheronuk: ack
[19:09] <IrcsomeBot1> <ahoneybun> I've done it @Sick_Rimmit
[19:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #45: ABORTED in 2 hr 9 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/45/
[19:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #28: ABORTED in 20 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/28/
[20:18] <mamarley> Launchpad seems thoroughly hosed.  In addition to lcy01 being down, it now seems to be ignoring uploads both of source packages and of binary packages from the remaining PPA builders…
[20:27] <valorie> yikes
[20:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #29: STILL FAILING in 45 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/29/
[20:38] <santa_> hi valorie
[20:38] <valorie> hi santa
[20:38] <santa_> well, I need a break. but I alredy did some progress on the kubuntu-retry-builds improvement
[20:40] <valorie> cool, it sounds like the day was a bit frustrating
[20:40] <valorie> good ole lunchpad
[20:40] <santa_> a bit stressing, but not frustrating
[20:40] <mamarley> Did somebody say lunch?
[20:40] <wxl> santa_: did you add any rate limiting or additional error checking with the kubuntu-retry-builds script to keep this from happening?
[20:41] <santa_> acheronuk, tsimonq2: when thins thing is done we will have a small change in the KA user interface: dev-package-names-list and package-name-list won't exist anymore; instead we will have a ka-update-metadata which will update any package metadata (including the dev and source package names list)
[20:42] <santa_> wxl: what I'm going to do is just scheduling for rebuild only the releavant packages
[20:42] <wxl> santa_: great idea
[20:42] <santa_> for instance if we upload a new frameworks version everything will be waiting for extra-cmake-modules
[20:43] <santa_> the way it's done now it schedules rebuldings of all the dep-wait packages
[20:44] <santa_> this is pretty dumb because it triggers an unintentional DoS against the launchpad build farm
[20:45] <santa_> so the idea is rebuilding only the packages which doesn't have anything else blocking them, and therefore are prone to build succesfully
[20:45] <mamarley> Right now the build farm seems to be doing a pretty effective job of denying access to itself.
[20:46] <santa_> anyway this problem shouldn't exist in the first place, because imho launchpad should put the dep-wait packages on hold
[20:46] <santa_> like wannabuild from debian does
[20:47] <santa_> I mean right now I can beat the launchpad buid farm @ building frameworks with a core i3 and 4 gb of ram
[20:47] <santa_> go figure
[20:50] <wxl> ko
[20:50] <wxl> maybe it's too far for anyone to reach it
[20:50] <wxl> you should let them borrow your cane
[21:18] <acheronuk> oooh. lcy01 builders now say 'cleaning' instead of 'disabled'
[21:18]  * acheronuk crosses fingers and toes
[21:20] <valorie> that sounds good
[21:21] <acheronuk> it has the potential for goodness.....
[21:22] <acheronuk> and the potential to crash and burn....
[22:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #30: FIXED in 1 hr 19 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/30/
=== greyback|afk is now known as greyback
[22:23] <santa_> acheronuk, tsimonq2: ok I have just pushed now the kubuntu-retry-builds improvement to kubuntu-automation/master
[22:23] <santa_> piece of cake XD
[22:23] <santa_> let me know if you have any doubts about the stuff I have done
[22:24] <santa_> oh, IMPORTANT (yes, in caps lock)
[22:24] <wxl> don't ever use it and then go to sleep? :)
[22:25] <valorie> lol
[22:25] <santa_> even with the improvement please refrain to execute it against plasma right now because it's still waiting for frameworks
[22:25] <santa_> but it's safe to use it against frameworks (apparently)
[22:25] <wxl> we should document that general dependency
[22:26] <wxl> i assume applications also needs frameworks, too?
[22:26] <santa_> well, I'm not going to document it because this is just a temporary situation
[22:27] <santa_> in a normal situation we won't have this problem
[22:27] <wxl> seems reasonable
[22:27] <santa_> and yes, apps also needs frameworks, but we are not dealing with applications right now
[23:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #320: FAILURE in 27 min: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/320/
[23:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #321: STILL FAILING in 6 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/321/
[23:56] <valorie> bug  #1643715 
[23:56] <ubottu> bug 1530523 in libqapt (Ubuntu Xenial) "duplicate for #1643715 kcm_driver_manager: Infinitely shows Collecting information" [High,Triaged] https://launchpad.net/bugs/1530523
[23:57] <valorie> hmmm, really?