[00:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #185: UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/185/
[00:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #199: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/199/
[00:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #223: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/223/
[00:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #399: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_kstars/399/
[00:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #266: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/266/
[00:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #204: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/204/
[00:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #416: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/416/
[00:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-dev-utils build #93: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kde-dev-utils/93/
[00:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #77: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/77/
[00:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #68: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kdb/68/
[00:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #262: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/262/
[00:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #133: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kstars/133/
[00:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #98: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/98/
[00:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #228: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/228/
[00:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #129: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/129/
[00:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #101: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/101/
[00:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #300: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/300/
[00:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #175: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/175/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #123: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/123/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #118: UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/118/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #134: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/zesty_unstable_marble/134/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #42: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_k3b/42/
[01:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #110: STILL UNSTABLE in 1 hr 20 min: http://kci.pangea.pub/job/zesty_unstable_krita/110/
[01:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kunitconversion build #115: STILL FAILING in 4 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_kunitconversion/115/
[01:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #100: STILL UNSTABLE in 9 min 49 sec: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/100/
[01:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kunitconversion build #116: STILL FAILING in 3 min 38 sec: http://kci.pangea.pub/job/zesty_unstable_kunitconversion/116/
[01:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktexteditor build #105: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_ktexteditor/105/
[02:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #173: FAILURE in 5 min 0 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/173/
[02:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #115: FAILURE in 5 min 46 sec: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/115/
[02:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #174: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/174/
[02:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #116: STILL FAILING in 4 min 35 sec: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/116/
[02:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #165: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_messagelib/165/
[03:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #87: STILL UNSTABLE in 1 hr 12 min: http://kci.pangea.pub/job/zesty_unstable_calligra/87/
[03:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcompletion build #80: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kcompletion/80/
[03:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #120: STILL UNSTABLE in 8 min 17 sec: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/120/
[03:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kguiaddons build #96: STILL UNSTABLE in 6 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_kguiaddons/96/
[03:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kauth build #59: STILL UNSTABLE in 7 min 3 sec: http://kci.pangea.pub/job/zesty_unstable_kauth/59/
[03:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfig build #85: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_kconfig/85/
[03:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcodecs build #91: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kcodecs/91/
[03:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #123: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/123/
[04:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ki18n build #96: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_ki18n/96/
[04:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #94: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_kcoreaddons/94/
[10:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #117: NOW UNSTABLE in 1 hr 59 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/117/
[10:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #175: FIXED in 1 hr 59 min: http://kci.pangea.pub/job/zesty_unstable_kmail/175/
[10:39] <BluesKaj> Hiyas all
[11:29] <yofel> hm...
[11:29] <yofel> why are the image jobs messed up again
[11:37] <yofel> clivejo, acheronuk: did one of you intentionally re-enable post-build workspace cleanup for the image builds?
[11:39] <clivejo> yofel: That would have been me, for zesty build.  I was trying to find a way to copy the created iso somewhere useful
[11:40] <yofel> ah ok
[11:40] <acheronuk> yofel: not intentionally here. I did look last week or something, as I was wondering why a build I triggered did not leave the iso in place
[11:40] <acheronuk> clivejo: aha
[11:40] <clivejo> I couldnt see a way of doing it unless the job was on master
[11:40] <clivejo> but master has no containers
[11:41] <yofel> master also doesn't have the disk space configured for that right now
[11:41]  * acheronuk wants it somewhere he can zysnc
[11:41] <clivejo> have I caused problems?
[11:41]  * clivejo wants that too
[11:42] <yofel> it can't zsync from teh workspace?
[11:42] <yofel> oh, no
[11:42] <yofel> timestamp
[11:42] <acheronuk> no authentication either?
[11:42] <clivejo> well the workspace is hidden behind the OpenID auth
[11:42] <yofel> well, the workspace is public
[11:43] <clivejo> is it?
[11:43] <acheronuk> I didn't think so
[11:43] <clivejo> I didnt think so either
[11:43] <yofel> oh, it indeed isn't
[11:43] <yofel> meh
[11:43] <clivejo> which is why I been trying to copy the iso somewhere public for people to grab easy
[11:44] <yofel> hm.....
[11:44]  * acheronuk smells gammon cooking
[11:44] <yofel> let me split that weird volume group on pond, then lets see if we can work that out
[11:46] <clivejo> river seems to run the job on master, and just copies it into www folder 
[11:46] <yofel> right. I'm not against your copy-on-master-then-somewhere-else idea per se
[11:47] <yofel> you'll just make master run out of space with that right now
[11:47] <yofel> well, eventually
[11:47] <clivejo> does kubuntu-ci user have a FTP space?
[11:47] <clivejo> like we do?
[11:48] <yofel> probably, but we can use master just fine
[11:48] <yofel> if we use more than 50G of the 1.2TiB that we have ^^
[11:49] <acheronuk> yofel: is there any reason we have not updated sddm to v14?
[11:49] <yofel> I just don't want to have that on / which has 19G left
[11:50] <yofel> acheronuk: not that I know of
[11:50] <clivejo> acheronuk: simon proposed a merge that that somewhere
[11:50] <clivejo> of that
[11:50]  * yofel wonders why that mkdir in the job failed though
[11:51] <acheronuk> yofel clivejo:hmmm. maybe a bit late in the release cycle now to mess with sddm?
[11:51] <clivejo> I dont know enough about sddm to mess with it
[11:51] <yofel> depends on the feature set, is it worth it?
[11:52] <acheronuk> nicer default user icons on the login screen. lol.
[11:52] <acheronuk> apart from that I'm not 100% sure
[11:53] <yofel> ok, vgs split. now we have 930G HDD and 172G SSD space that's unused
[11:53] <acheronuk> https://github.com/sddm/sddm/releases
[11:54] <clivejo> who else uses sddm?
[11:55] <clivejo> lubuntu?
[11:55] <yofel> the PAM and HiDPI stuff might be worth it
[11:57] <acheronuk> build in a ppa somewhere this week and test I guess
[11:57] <acheronuk> then maybe ffe
[12:00] <acheronuk> well, seems Neon have been basically running the debian 14.0 sddm with one extra patch
[12:00] <acheronuk> https://packaging.neon.kde.org/kde-std/sddm.git/log/?h=Neon/release
[12:00] <acheronuk> ^^^^ something to look into this week.
[12:01] <acheronuk> gotta go for Sunday lunch now :)
[12:01] <clivejo> enjoy!
[12:01] <yofel> do you guys know why we have 2 workspace folders in jenkins? (mgmt_ and merger_ use ~/workspace/, the build jobs ~/workspaces/)
[12:01] <clivejo> no idea
[12:02]  * acheronuk shrugs on way out the door
[12:02] <clivejo> but its been the case for a while
[12:02] <yofel> I guess he wanted to have the namespaces separate
[12:02] <yofel> i guess I could bind mount stuff...
[12:03] <yofel> or go with btrfs if it's just storage
[12:05] <clivejo> !info sddm
[12:42] <yofel> ok, master now has 200G for workspace storage. And I installed and configured docker while at it
[12:49] <yofel> clivejo: do you know where the implicit job plugin triggers come from?
[12:50] <yofel> copy-to-slave isn't actually part of the job, but runs anyway
[12:51] <yofel> otoh, we'll have to override it anyway so it doesn't copy the lb workspace
[13:07]  * yofel gives up and gives fixing the tooling deployment another go
[13:17] <ahoneybun> ohhhh kube was added to the KCI
[13:19] <clivejo> yofel: havent a clue
[13:20] <clivejo> ahoneybun: yes, but it won't build
[13:20] <clivejo> it requires sink
[13:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #47: STILL FAILING in 1.9 sec: http://kci.pangea.pub/job/mgmt_tooling/47/
[13:29] <ahoneybun> still cool
[13:32] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #48: STILL FAILING in 2.3 sec: http://kci.pangea.pub/job/mgmt_tooling/48/
[13:35] <yofel> huh
[13:35] <yofel> clivejo: am I seeing this right that jenkins is missing the rvm plugin?
[13:37]  * yofel wonders why the mergers are actually working o.O
[13:41] <clivejo> did you install it?
[13:42] <clivejo> says 0.6 is installed
[13:42] <yofel> I did, lets hope I didn't just break everything
[13:43]  * clivejo crosses fingers
[13:44] <clivejo> ahoneybun: is this now resolved - https://phabricator.kde.org/T5247 ?
[13:46] <yofel> duh
[13:47] <yofel> I didn't because rvm is used nowhere as it wasn't installed
[13:47] <clivejo> should it be used?
[13:49] <yofel> well, for mgmt_tooling to work, it has to be able to somewhat control and manipulate the ruby environment it runs it. Which it can't with the system ruby as that requires root permissions. So you need some kind of environment wrapper. Harald went with rvm
[13:50] <clivejo> can you get that working again then?
[13:50] <yofel> yes, well, eventually
[14:03] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #49: STILL FAILING in 3 min 26 sec: http://kci.pangea.pub/job/mgmt_tooling/49/
[14:03] <yofel> well, progress
[14:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #50: STILL FAILING in 1 min 28 sec: http://kci.pangea.pub/job/mgmt_tooling/50/
[14:08] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #51: STILL FAILING in 31 sec: http://kci.pangea.pub/job/mgmt_tooling/51/
[14:08] -kubuntu-ci:#kubuntu-devel- Philip Muškovac: Don't require nokogiri twice
[14:17] <yofel> grrr, running the wrong ruby
[14:31] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #54: STILL FAILING in 19 sec: http://kci.pangea.pub/job/mgmt_tooling/54/
[14:32] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #55: STILL FAILING in 32 sec: http://kci.pangea.pub/job/mgmt_tooling/55/
[14:32] -kubuntu-ci:#kubuntu-devel- Failed tests:
[14:32] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/55/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[14:32] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/55/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[14:32] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/55/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[14:32] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/55/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[14:32] -kubuntu-ci:#kubuntu-devel- DeployTest.test_upgrade: http://kci.pangea.pub/job/mgmt_tooling/55/testReport/junit/junit/(root)/DeployTest/test_upgrade
[14:32] -kubuntu-ci:#kubuntu-devel- (3 more)
[14:46] <yofel> ok, that works again. Now I'll need to fix the env on the slaves
[14:46] <yofel> later
[18:02] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #56: STILL FAILING in 34 sec: http://kci.pangea.pub/job/mgmt_tooling/56/
[18:02] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Remove misnamed management job
[18:02] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Document the rvm setup
[18:02] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Add another job for the tooling deployment and adjust the jobs
[18:03] -kubuntu-ci:#kubuntu-devel- Failed tests:
[18:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/56/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[18:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/56/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[18:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/56/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[18:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/56/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[18:03] -kubuntu-ci:#kubuntu-devel- DeployTest.test_upgrade: http://kci.pangea.pub/job/mgmt_tooling/56/testReport/junit/junit/(root)/DeployTest/test_upgrade
[18:03] -kubuntu-ci:#kubuntu-devel- (3 more)
[18:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #1: SUCCESS in 23 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/1/
[18:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #1: SUCCESS in 3 min 44 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/1/
[18:55] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #57: STILL FAILING in 49 sec: http://kci.pangea.pub/job/mgmt_tooling/57/
[18:55] -kubuntu-ci:#kubuntu-devel- Philip Muškovac: Fix the broken job syntax and use the current rvm env config
[18:55] -kubuntu-ci:#kubuntu-devel- Failed tests:
[18:55] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/57/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[18:55] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/57/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[18:55] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/57/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[18:55] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/57/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[18:55] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: http://kci.pangea.pub/job/mgmt_tooling/57/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[18:55] -kubuntu-ci:#kubuntu-devel- (2 more)
[18:56] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #1: SUCCESS in 6 min 47 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/1/
[18:56] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #1: SUCCESS in 7 min 6 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/1/
[18:56] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1337: FAILURE in 0.19 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1337/
[18:57] <yofel> o.O
[18:59] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1337: SUCCESS in 2 min 44 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1337/
[19:00] <yofel> oh
[19:04] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1337: SUCCESS in 7 min 34 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1337/
[19:04] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1337: SUCCESS in 8 min 13 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1337/
[19:04] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1338: STILL FAILING in 1.3 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1338/
[19:05] <yofel> okay, I could've known that...
[19:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1338: SUCCESS in 1 min 6 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1338/
[19:08] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1338: SUCCESS in 3 min 35 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1338/
[19:08] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1338: SUCCESS in 3 min 49 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1338/
[19:12] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1339: STILL FAILING in 1.2 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1339/
[19:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1339: SUCCESS in 1 min 10 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1339/
[19:15] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1339: SUCCESS in 3 min 40 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1339/
[19:15] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1339: SUCCESS in 3 min 50 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1339/
[19:18] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1340: STILL FAILING in 0.76 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1340/
[19:19] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1340: SUCCESS in 1 min 1 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1340/
[19:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1340: SUCCESS in 3 min 35 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1340/
[19:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1340: SUCCESS in 3 min 51 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1340/
 Huh?
[19:35] <yofel> ruby gem management is annoying
[19:42] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1341: STILL FAILING in 0.75 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1341/
[19:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1342: STILL FAILING in 0.75 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1342/
[19:51] <yofel> where the hell is it pulling those gems from o.O
[19:51] <yofel> this works fine in a shell...
[19:54] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1343: STILL FAILING in 0.85 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1343/
[19:58] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1344: STILL FAILING in 0.83 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1344/
[19:59] <yofel> Using /var/lib/jenkins/.rvm/gems/ruby-2.3.3
[19:59] <yofel> GEM_HOME='/var/lib/jenkins/.rvm/gems/ruby-2.4.0'
[19:59] <yofel> wtf?!?
[20:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:04] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1345: FIXED in 4 min 11 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1345/
[20:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1346: SUCCESS in 58 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1346/
[20:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1346: SUCCESS in 1 min 9 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1346/
[20:09] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1346: SUCCESS in 3 min 41 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1346/
[20:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1346: SUCCESS in 3 min 50 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1346/
[20:12] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1347: SUCCESS in 57 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1347/
[20:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1348: SUCCESS in 57 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1348/
[20:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #58: STILL FAILING in 2 min 50 sec: http://kci.pangea.pub/job/mgmt_tooling/58/
[20:22] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Use rvm for the docker update
[20:22] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: ... and cleanup
[20:22] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Read the rvm env again before the docker update
[20:22] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Only use local gems again
[20:22] -kubuntu-ci:#kubuntu-devel- Failed tests:
[20:22] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/58/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[20:22] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/58/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[20:22] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/58/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[20:22] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/58/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[20:22] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: http://kci.pangea.pub/job/mgmt_tooling/58/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[20:22] -kubuntu-ci:#kubuntu-devel- (2 more)
[20:23] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #2: FAILURE in 22 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/2/
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix the broken job syntax and use the current rvm env config
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Use rvm for the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: ... and cleanup
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Read the rvm env again before the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Only use local gems again
[20:23] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #2: SUCCESS in 32 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/2/
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix the broken job syntax and use the current rvm env config
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Use rvm for the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: ... and cleanup
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Read the rvm env again before the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Only use local gems again
[20:23] <yofel> urgh
[20:23] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #2: SUCCESS in 1 min 3 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/2/
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix the broken job syntax and use the current rvm env config
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Use rvm for the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: ... and cleanup
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Read the rvm env again before the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Only use local gems again
[20:23] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #2: SUCCESS in 1 min 5 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/2/
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix the broken job syntax and use the current rvm env config
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Use rvm for the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: ... and cleanup
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Read the rvm env again before the docker update
[20:23] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Only use local gems again
[20:24] -kubuntu-ci:#kubuntu-devel- Starting build #28 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[20:32] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #28: ABORTED in 7 min 26 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/28/
[20:35] <yofel> acheronuk, clivejo: FYI: I had to change the jenkins UID for the deployment to work right - just in case permission errors pop up somewhere
[20:36] <clivejo> where would they pop up?
[20:36] <yofel> somewhere I can't think of. I fixed everything else ;)
[20:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:37] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #3: FIXED in 24 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/3/
[20:37] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #3: SUCCESS in 33 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/3/
[20:38] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #3: SUCCESS in 1 min 2 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/3/
[20:38] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #3: SUCCESS in 1 min 5 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/3/
[20:39] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1349: SUCCESS in 58 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1349/
[20:39] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1349: SUCCESS in 1 min 2 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1349/
[20:41] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1349: SUCCESS in 3 min 38 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1349/
[20:42] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1349: SUCCESS in 3 min 51 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1349/
[20:43] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #59: STILL FAILING in 45 sec: http://kci.pangea.pub/job/mgmt_tooling/59/
[20:43] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Build images on master again
[20:43] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Don't print commits for the deploy status
[20:43] -kubuntu-ci:#kubuntu-devel- Failed tests:
[20:43] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/59/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[20:43] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/59/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[20:43] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/59/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[20:43] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/59/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[20:43] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: http://kci.pangea.pub/job/mgmt_tooling/59/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[20:43] -kubuntu-ci:#kubuntu-devel- (2 more)
[20:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #4: SUCCESS in 22 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/4/
[20:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #4: SUCCESS in 27 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/4/
[20:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #4: SUCCESS in 53 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/4/
[20:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #4: SUCCESS in 59 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/4/
[20:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1350: SUCCESS in 56 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1350/
[20:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1350: SUCCESS in 1 min 3 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1350/
[20:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1350: SUCCESS in 3 min 35 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1350/
[20:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1350: SUCCESS in 3 min 50 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1350/
[20:50] <clivejo> yofel: what you doing?
[20:50] <yofel> clivejo: I just finished fixing the auto-deployment
[20:51] <yofel> although it won't auto-trigger as long as the tests fail
[20:51] <clivejo> so a push to pangea tooling on LP will auto deploy?
[20:52] <yofel> it will trigger mgmt_tooling, which if >= UNSTABLE will trigger mgmt_tooling_deploy which on SUCCESS will trigger mgmt_docker
[20:53] <clivejo> any insight on getting stable running again?
[20:53] <yofel> so for the time being you'll have to trigger mgmt_tooling_deploy by hand
[20:53] <yofel> some more ideas, but I wanted to get this out of the way first
[20:54] -kubuntu-ci:#kubuntu-devel- Starting build #29 for job iso_zesty_unstable_amd64 (previous build: ABORTED -- last SUCCESS #27 16 days ago)
[21:00] <yofel> grrr. I knew I forgot something
[21:06] <clivejo> are the iso's public now?
[21:06] <yofel> not yet
[21:06] <yofel> I'm trying to build them on master, but I forgot to set up apt-cacher-ng
[21:07] <yofel> better
[21:07] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #29: FAILURE in 13 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/29/
[21:08] <yofel> o.O
[21:09] -kubuntu-ci:#kubuntu-devel- Starting build #30 for job iso_zesty_unstable_amd64 (previous build: FAILURE -- last SUCCESS #27 16 days ago)
[21:10] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #30: STILL FAILING in 1 min 21 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/30/
[21:10] <clivejo> :O
[21:11] -kubuntu-ci:#kubuntu-devel- Starting build #31 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #27 16 days ago)
[21:13] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #31: STILL FAILING in 1 min 20 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/31/
[21:16] <yofel> hm, that's exactly why I'm passing CAP_SYS_ADMIN. Why is it ignoring that..
[21:23] <yofel> duh, apparmor
 (Photo, 1280x360) https://irc-attachments.kde.org/GouBxg8U/file_2191.jpg
 \o/
[21:38] <clivejo> ??
[21:39] <clivejo> dual monitors?
[21:39] <ahoneybun> ywp
[21:39] <ahoneybun> *yep
[21:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #60: STILL FAILING in 34 sec: http://kci.pangea.pub/job/mgmt_tooling/60/
[21:49] -kubuntu-ci:#kubuntu-devel- Philip Muškovac: Disable apparmor
[21:49] -kubuntu-ci:#kubuntu-devel- Failed tests:
[21:49] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/60/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[21:49] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/60/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[21:49] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/60/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[21:49] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/60/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[21:49] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: http://kci.pangea.pub/job/mgmt_tooling/60/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[21:49] -kubuntu-ci:#kubuntu-devel- (2 more)
[21:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #5: SUCCESS in 23 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/5/
[21:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #5: SUCCESS in 29 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/5/
[21:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #5: SUCCESS in 58 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/5/
[21:51] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #5: SUCCESS in 1 min 0 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/5/
 (Photo, 1280x360) https://irc-attachments.kde.org/wG06cFxu/file_2193.jpg
 better clivejo?
[21:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1351: SUCCESS in 58 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1351/
[21:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1351: SUCCESS in 1 min 2 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1351/
[21:54] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1351: SUCCESS in 3 min 41 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1351/
[21:55] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1351: SUCCESS in 3 min 51 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1351/
[21:55] -kubuntu-ci:#kubuntu-devel- Starting build #32 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #27 16 days ago)
[22:03] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #61: STILL FAILING in 40 sec: http://kci.pangea.pub/job/mgmt_tooling/61/
[22:03] -kubuntu-ci:#kubuntu-devel- Philip Muškovac: Only disable apparmor for image builds
[22:03] -kubuntu-ci:#kubuntu-devel- Failed tests:
[22:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: http://kci.pangea.pub/job/mgmt_tooling/61/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[22:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: http://kci.pangea.pub/job/mgmt_tooling/61/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[22:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: http://kci.pangea.pub/job/mgmt_tooling/61/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[22:03] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: http://kci.pangea.pub/job/mgmt_tooling/61/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[22:03] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: http://kci.pangea.pub/job/mgmt_tooling/61/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[22:03] -kubuntu-ci:#kubuntu-devel- (2 more)
[22:11] <clivejo> yofel: where will it put them when it does start to build them?
[22:12] <yofel> not quite sure yet, I'll probably just add a vhost with a public dir
[22:13] <yofel> although, looking at that thing building I might look into copying from linode after all. This is too slow -.-
[22:16] <yofel> I wonder how that worked before. The builder code seems to imply that the storage folder got bind-mounted into the container?
[22:19] <clivejo> looks like it, the master filesystem looks visable from inside the container
[22:19] <clivejo> its slow on pond?
[22:20] <clivejo> I thought that thing was really hardware?
[22:20] <yofel> well, the workspaces are on the HDDs, and that's where the images build as that's chrooted
[22:20] <yofel> so everything but the image builds is fast ^^
[22:23] <yofel> I could put the workspaces into the same thin-lv that docker uses I guess. That thing has 150G
[23:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:03] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #32: FIXED in 1 hr 7 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/32/
[23:03] <yofel> dat runtime
[23:16] <clivejo> KCI : The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
[23:17] <yofel> that was me
[23:17] <clivejo> oh right
[23:18] <yofel> sadly my idea of using the docker volume doesn't work because devicemapper messes up the lv metadata *-.-
[23:18] <yofel> so I'm setting things up again differently
[23:21] <clivejo> if we got sftp space on LP, could the file be sftp from within the container?
[23:22] <yofel> probably, but I don't think we have enough space there
[23:22] <yofel> FWIW, we could sftp to master in exactly the same way
[23:22] <clivejo> from within container on Linode?
[23:24] <yofel> right
[23:25] <yofel> lets see if that's any faster
[23:26] -kubuntu-ci:#kubuntu-devel- Starting build #33 for job iso_zesty_unstable_amd64 (previous build: FIXED)
[23:26] <yofel> sadly eatmydata doesn't really work well with live build :/
[23:27] <clivejo> can it be sftp back to pond:/var/www/ ?
[23:28] <clivejo> what seed does the job use to create the iso?
[23:29] <yofel> kubuntu-desktop right now
[23:30] <yofel> ok, this is considerably better
[23:30] <clivejo> I guess thats why its smaller than the daily ISO
[23:31] <yofel> the daily has some extra stuff just for the live session
[23:31] <yofel> the ci image mostly not
[23:32] <clivejo> did you fix the clock?
[23:32] <yofel> not intentionally. Might've been a ntp hickup
 all sounds good. :) will have to catch up on what you have both been up to tommorow
[23:35]  * clivejo points at yofel
[23:35]  * clivejo did nothing
[23:35] <yofel> you kept asking questions :D
[23:36] <clivejo> Im good at that :P
[23:37] <clivejo> seeing as we not getting that other machine, could we setup an autotests thingie-ma-bob on a Linode container?
[23:39] <yofel> I guess so. There's some spare space left as long as it's not excessive
[23:39] <clivejo> or will Aaron have pink kittens ?
[23:40] <clivejo> the packages have to be rebuilt locally?
[23:40] <yofel> dunno. You could also run that on the CI server. That has plenty of resources left if you don't mind using it for multiple things
[23:41] <clivejo> or can the built packages be installed from the PPA and just built the tests?
[23:41] <yofel> no, you need the compile cache to actually build stuff
[23:42] <yofel> but I'm not too familiar with the necessary setup
[23:42] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #33: SUCCESS in 16 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/33/
[23:43] <clivejo> eakk
[23:43] <yofel> lol, that took a quater of the time XD
[23:43] <ahoneybun> pink kittens?
[23:43] <clivejo> ahoneybun: seeing Linode maxing out all the time
[23:43] <yofel> throwing out some fs integrity helped >.>
[23:44] <ahoneybun> I did get an email yesterday about it
[23:45] <yofel> can't you deactivate those?
[23:46] <ahoneybun> maybe just easier to delete the email
[23:53] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #6: SUCCESS in 25 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/6/
[23:53] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #6: SUCCESS in 31 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/6/
[23:54] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #6: SUCCESS in 1 min 5 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/6/
[23:54] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #6: SUCCESS in 1 min 8 sec: http://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/6/
[23:55] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1352: SUCCESS in 57 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1352/
[23:55] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1352: SUCCESS in 59 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1352/
[23:58] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1352: SUCCESS in 3 min 42 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1352/
[23:58] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1352: SUCCESS in 3 min 57 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1352/