[00:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #38: STILL UNSTABLE in 1 hr 4 min: https://kci.pangea.pub/job/bionic_unstable_cantor/38/
[00:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #59: STILL UNSTABLE in 1 hr 6 min: https://kci.pangea.pub/job/bionic_unstable_ark/59/
[00:11] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #60: FAILURE in 1 hr 16 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/60/
[00:17] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #59: STILL UNSTABLE in 1 hr 21 min: https://kci.pangea.pub/job/bionic_stable_cantor/59/
[00:31] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_purpose build #52: STILL FAILING in 47 min: https://kci.pangea.pub/job/bionic_unstable_purpose/52/
[00:32] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #43: STILL UNSTABLE in 1 hr 36 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/43/
[00:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #61: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/61/
[00:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_baloo-widgets build #41: STILL FAILING in 1 hr 19 min: https://kci.pangea.pub/job/bionic_unstable_baloo-widgets/41/
[00:54] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #54: STILL UNSTABLE in 1 hr 59 min: https://kci.pangea.pub/job/bionic_unstable_kstars/54/
[01:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #62: FIXED in 25 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/62/
[01:09] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kwin build #65: STILL UNSTABLE in 1 hr 56 min: https://kci.pangea.pub/job/bionic_stable_kwin/65/
[01:09] <mparillo> Following https://kubuntu.org/news/plasma-5-12-lts-beta-available-ppa-for-testing-on-artful-bionic/ in an AA VM. I got 262 packages to update. Clean update, re-booted the VM. No dead kittens. 
[01:11] <mparillo> krunner launches kinfocenter, reporting Plasma 5.11.95 (FW 5.42). The kicker application launcher launches discover, System Settings, Dolphin, Kate, konsole, and they come up cleanly.
[01:13] <mparillo> It did not switch AA to Breeze Dark.
[01:17] <acheronuk> mparillo: thanks. the breeze dark was set in a config file provided by kubuntu-settings in bionic, so AA would not have switched
[01:44] <mparillo> And unlike XX, I did not manage to crash discover.
[01:50] <mparillo> https://blog.martin-graesslin.com/blog/2018/01/kwinx11-is-feature-frozen/
[02:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #61: STILL UNSTABLE in 2 hr 40 min: https://kci.pangea.pub/job/bionic_unstable_kwin/61/
[02:03] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi build #67: FAILURE in 44 min: https://kci.pangea.pub/job/bionic_unstable_akonadi/67/
[02:13] <IrcsomeBot> <ahoneybun> Finally leaving for home from the office lol
[02:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdevelop build #72: UNSTABLE in 54 min: https://kci.pangea.pub/job/bionic_unstable_kdevelop/72/
[02:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi build #68: STILL FAILING in 21 min: https://kci.pangea.pub/job/bionic_unstable_akonadi/68/
[02:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:53] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_purpose build #53: FIXED in 22 min: https://kci.pangea.pub/job/bionic_unstable_purpose/53/
=== ronnoc_ is now known as ronnoc
[05:34] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdeclarative build #37: UNSTABLE in 2 hr 12 min: https://kci.pangea.pub/job/bionic_unstable_kdeclarative/37/
[08:00] <jimtendo> Hi all,
[08:00] <jimtendo> Not sure if this is a Kubuntu issue or I'm doing something wrong (copying from other CMakeLists that I've seen). When trying to build a KDE plugin, I'm using ${PLUGIN_INSTALL_DIR} as the location to install the library to. On Kubuntu, this maps to: /usr/lib/x86_64-linux-gnu/plugins/ where as I think it should be /usr/lib/x86_64-linux-gnu/qt5/plugins/, lest it won't be found otherwise. Anyone know anything about this or has noticed similar behaviour?
[08:00] <jimtendo> ^ Does that sound like a bug? The way I'm referencing the install dir in my CMake (copied from some other projects I've seen): install(TARGETS mylib DESTINATION ${PLUGIN_INSTALL_DIR})
[08:23] <blaze> jimtendo: cmake is not that smart as you may think, you have to define it manually
[08:27] <acheronuk> jimtendo: maybe pass -DKDE_INSTALL_USE_QT_SYS_PATHS=ON to cmake?
[08:29] <blaze> in case of kde app there's ${KDE_INSTALL_PLUGINDIR} variable
[08:32] <acheronuk> jimtendo: our build tools for packages pass that cmake option by default
[08:32] <blaze> you have to use include(KDEInstallDirs) from ECM
[08:32] <acheronuk> yes, you do
[08:33]  * acheronuk hates cmake
[08:34] <acheronuk> well, it can be annoying, anyway
[08:35] <blaze> i love cmake, because I had to use autotools earlier :D
[08:36] <acheronuk> urgh. point taken
[08:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdevelop build #73: FIXED in 37 min: https://kci.pangea.pub/job/bionic_unstable_kdevelop/73/
[08:55] <jimtendo> Thanks acheronuk and blaze... looks like the "-DKDE_INSTALL_USE_QT_SYS_PATHS=ON" was what I needed :)
[08:56] <acheronuk> :)
[08:59] <jimtendo> Quick followup sorry - is there a command I can use to restart KRunner? Working on a onetimepass (TOTP) krunner atm.
[10:52] <BluesKaj> Howdy folks
[10:54] <jimtendo> Howdy BluesKaj.
[10:55] <BluesKaj> Hi jimtendo
[11:14] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2009: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2009/
[11:16] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2009: SUCCESS in 3 min 38 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2009/
=== JoseeAntonioR is now known as jose
[16:51] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2009: SUCCESS in 5 hr 38 min: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2009/
[16:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2010: SUCCESS in 40 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2010/
[16:53] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2010: FAILURE in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2010/
[17:01] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2011: SUCCESS in 43 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2011/
[17:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:02] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2011: FIXED in 1 min 23 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2011/
[17:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2011: FIXED in 4 min 25 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2011/
[17:05] <yofel> FYI: CI is operational again after the meltdown maintenance on linode earlier today
[17:13] <IrcsomeBot> <tsimonq2> Kool
[18:36] <acheronuk> yofel: thanks. I was going to try to look at it, but sort put it off
[18:36] <acheronuk> sort off
[18:40] <acheronuk> yofel: docker-monitor.service does not seem to start automatically on any nodes. is that normal? I need to go in and manually start it when they are rebooted
[18:42] <yofel> that is supposed to auto-start, maybe I forgot to actually enable it again..
[18:43] <yofel> hm no...
[18:45] <yofel> Jan 17 16:56:40 kubuntu.dh.bytemark.co.uk docker-monitor[1834]: /usr/lib/ruby/2.3.0/drb/drb.rb:883:in `initialize': Cannot assign requested address - bind(2) for "10.0.3.1" port 9991 (Errno::EADDRNOTAVAIL)
[18:45] <yofel> looks like I forgot to make it depend on the network target?
[18:45] <acheronuk> I didn't poke at it, on the principle that if I change nothing I break nothing
[18:45] <acheronuk> right
[18:46] <yofel> okay, I'll fix that once I find out what the correct dep is
[18:49] <acheronuk> cool. not been a huge bother, but it did perplex me until I discovered what it was and why stuff was failing
[18:50] <acheronuk> still not sure why mgmt_tooling is broken. if you have a clue on that, would be appreciated
[18:51] <yofel> that really isn't telling much.. noted
[18:53] <acheronuk> 20:59:39 Tests have failed for a parallel_test group. Use the following command to run the group again:
[18:53] <acheronuk> 20:59:39 
[18:53] <acheronuk> 20:59:39 nice ruby -r/var/lib/jenkins/workspace/mgmt_tooling/test/helper.rb -Itest -e '%w[ci-tooling/test/test_adt_junit_summary.rb ci-tooling/test/test_ci_source.rb ci-tooling/test/test_ci_tarball.rb ci-tooling/test/test_mutable-uri_generic.rb ci-tooling/test/test_projects_factory.rb ci-tooling/test/test_thread_pool.rb ci-tooling/test/test_upstream_scm.rb].each { |f| require %{./#{f}} }' --  2>&1
[18:54] <acheronuk> but nothing that really tell me why
[18:54] <acheronuk> so, I've not got much to 'tell'!
[18:55] <acheronuk> well, not really being familiar with the test side, it doesn't tell *me* much, anyway
[18:56]  * acheronuk runs it
[18:57] <acheronuk> knowing my luck, it will pass
[19:01] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #180: STILL FAILING in 4 min 59 sec: https://kci.pangea.pub/job/mgmt_tooling/180/
[19:01] <acheronuk> nope. same fail :/
=== claydoh is now known as Guest18477