[00:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1015: SUCCESS in 7 min 18 sec: https://kci.pangea.pub/job/mgmt_merger/1015/ [00:59] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_plasma-workspace-wallpapers build #39: FAILURE in 12 min: https://kci.pangea.pub/job/bionic_stable_plasma-workspace-wallpapers/39/ [00:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:59] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ksmtp build #20: FIXED in 14 min: https://kci.pangea.pub/job/artful_stable_ksmtp/20/ [00:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:59] -kubuntu-ci:#kubuntu-devel- Project artful_stable_picmi build #75: FIXED in 14 min: https://kci.pangea.pub/job/artful_stable_picmi/75/ [01:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [01:16] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ksudoku build #107: FIXED in 29 min: https://kci.pangea.pub/job/artful_stable_ksudoku/107/ [01:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [01:16] -kubuntu-ci:#kubuntu-devel- Project artful_stable_konquest build #24: FIXED in 31 min: https://kci.pangea.pub/job/artful_stable_konquest/24/ [01:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [01:17] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ksnakeduel build #53: FIXED in 31 min: https://kci.pangea.pub/job/artful_stable_ksnakeduel/53/ [01:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [01:17] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kmines build #93: FIXED in 30 min: https://kci.pangea.pub/job/artful_stable_kmines/93/ [01:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #37: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_ark/37/ [01:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kde-dev-scripts build #36: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_kde-dev-scripts/36/ [01:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_palapeli build #39: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_palapeli/39/ [01:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_falkon build #34: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_falkon/34/ [01:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kcachegrind build #37: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_kcachegrind/37/ [01:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [01:36] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktorrent build #132: FIXED in 49 min: https://kci.pangea.pub/job/artful_unstable_ktorrent/132/ [01:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #36: STILL UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/36/ [01:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #192: FAILURE in 20 min: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/192/ [01:40] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_purpose build #32: STILL UNSTABLE in 53 min: https://kci.pangea.pub/job/bionic_unstable_purpose/32/ [01:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #163: STILL FAILING in 7 min 1 sec: https://kci.pangea.pub/job/artful_unstable_babe/163/ [01:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #170: STILL UNSTABLE in 1 hr 5 min: https://kci.pangea.pub/job/artful_unstable_elisa/170/ [01:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #177: NOW UNSTABLE in 1 hr 6 min: https://kci.pangea.pub/job/artful_unstable_k3b/177/ [02:03] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #193: STILL FAILING in 10 min: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/193/ [02:07] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kcachegrind build #21: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_stable_kcachegrind/21/ [02:07] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_palapeli build #18: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_stable_palapeli/18/ [02:09] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #189: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/artful_unstable_ark/189/ [02:10] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #237: STILL UNSTABLE in 1 hr 23 min: https://kci.pangea.pub/job/artful_unstable_kstars/237/ [02:10] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kalzium build #171: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/artful_unstable_kalzium/171/ [02:11] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #164: STILL FAILING in 18 min: https://kci.pangea.pub/job/artful_unstable_babe/164/ [02:21] -kubuntu-ci:#kubuntu-devel- Project artful_stable_cantor build #88: STILL UNSTABLE in 1 hr 34 min: https://kci.pangea.pub/job/artful_stable_cantor/88/ [02:23] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kig build #36: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/bionic_unstable_kig/36/ [02:24] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_purpose build #162: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/artful_unstable_purpose/162/ [02:35] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #40: STILL UNSTABLE in 1 hr 48 min: https://kci.pangea.pub/job/bionic_stable_ark/40/ [02:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [02:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_killbots build #100: FIXED in 1 hr 49 min: https://kci.pangea.pub/job/artful_stable_killbots/100/ [02:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [02:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kgoldrunner build #112: FIXED in 1 hr 49 min: https://kci.pangea.pub/job/artful_stable_kgoldrunner/112/ [02:39] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #36: FAILURE in 56 min: https://kci.pangea.pub/job/bionic_unstable_kwin/36/ [02:46] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #36: STILL UNSTABLE in 1 hr 59 min: https://kci.pangea.pub/job/bionic_stable_kalzium/36/ [02:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #125: STILL UNSTABLE in 1 hr 28 min: https://kci.pangea.pub/job/artful_stable_ark/125/ [02:48] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #36: STILL UNSTABLE in 55 min: https://kci.pangea.pub/job/bionic_unstable_kstars/36/ [03:07] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kig build #40: STILL UNSTABLE in 1 hr 15 min: https://kci.pangea.pub/job/bionic_stable_kig/40/ [03:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [03:07] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_plasma-workspace-wallpapers build #40: FIXED in 1 hr 15 min: https://kci.pangea.pub/job/bionic_stable_plasma-workspace-wallpapers/40/ [03:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [03:08] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktorrent build #127: FIXED in 1 hr 31 min: https://kci.pangea.pub/job/artful_stable_ktorrent/127/ [03:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #73: STILL FAILING in 32 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/73/ [03:11] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwin build #208: FAILURE in 1 hr 7 min: https://kci.pangea.pub/job/artful_unstable_kwin/208/ [03:12] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #37: STILL FAILING in 27 min: https://kci.pangea.pub/job/bionic_unstable_kwin/37/ [03:21] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #40: STILL UNSTABLE in 1 hr 28 min: https://kci.pangea.pub/job/bionic_stable_cantor/40/ [03:28] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #47: FAILURE in 16 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/47/ [03:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmail build #238: STILL FAILING in 5 min 51 sec: https://kci.pangea.pub/job/artful_unstable_kmail/238/ [03:47] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #48: STILL FAILING in 13 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/48/ [03:50] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #74: STILL FAILING in 35 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/74/ [03:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwin build #209: STILL FAILING in 35 min: https://kci.pangea.pub/job/artful_unstable_kwin/209/ [03:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #39: FAILURE in 5 min 26 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/39/ [03:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmail build #239: STILL FAILING in 4 min 42 sec: https://kci.pangea.pub/job/artful_unstable_kmail/239/ [04:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #40: STILL FAILING in 4 min 20 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/40/ [04:06] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #217: FAILURE in 13 min: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/217/ [04:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #218: STILL FAILING in 8 min 44 sec: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/218/ [04:40] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_calligra build #35: STILL FAILING in 1 hr 53 min: https://kci.pangea.pub/job/bionic_unstable_calligra/35/ [04:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-addons build #234: STILL UNSTABLE in 53 min: https://kci.pangea.pub/job/artful_unstable_kdepim-addons/234/ [05:13] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdepim-addons build #55: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/bionic_unstable_kdepim-addons/55/ [05:20] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_calligra build #36: STILL FAILING in 34 min: https://kci.pangea.pub/job/bionic_unstable_calligra/36/ [05:21] uh [05:21] testbed out of date? @tsimonq2 ? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/a/ark/20171212_002708_ec42e@/log.gz [05:25] @wxl, Poke your favorite release team member in #ubuntu-release, it's not the package, it's the thing [05:25] In the meantime if you can give me a URL to retry that would work too, maybe... [05:26] (retry could make it try on a different builder) [05:26] Also a nice exercise in finding the right URL to link me ;) [05:27] @tsimonq2: i seriously need some help with this. there are problems all over the place [05:27] @wxl, Feed me examples [05:28] there's like 20 affected packages all with multiple archs [05:28] you'd be better off just helping me dig through excuses [05:28] @wxl, What's wrong with them? Outdated testbed? [05:29] all over the place [05:29] check this out https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/g/gwenview/20171212_005602_8bb9e@/log.gz [05:30] Welp, that's just the fun that is dealing with autopkgtests :) [05:31] But wxl if you do nothing else tonight, give me links to retry the outdated testbed ones and ping in #ubuntu-release [05:32] yeah well there's no documentation on that as far as i know [05:32] wxl: Bonus points if you can give me a link that makes it seem like I'm sponsoring the retry for you. ;) [05:32] What do you mean? There's plenty of documentation... [05:32] wiki.ubuntu.com/ProposedMigration [05:33] @wxl, https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Test_request_format [05:33] yeah, i'm sorry. not really helping me answer the questions i have [05:33] you'll have to work harder if you want me to get this [05:35] Fwd from tsimonq2: But wxl if you do nothing else tonight, give me links to retry the outdated testbed ones and ping in #ubuntu-release [05:35] This. [05:35] We're just dealing with that right now. [05:35] Go to excuses. [05:35] There's a recycle unicode thing [05:35] That's the retry link [05:35] Give me that link [05:35] Got it? [05:36] https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=ppc64el&package=baloo-widgets5&trigger=baloo-kf5%2F5.41.0-0ubuntu1 [05:36] Specifically for [05:36] Fwd from wxl: testbed out of date? @tsimonq2 ? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/a/ark/20171212_002708_ec42e@/log.gz [05:36] There we go wxl [05:40] K any other ones before I go to bed wxl? [05:40] tons [05:40] potentially [05:41] the only way i'll now is by going through each and every one of them [05:41] unless you know something i don't [05:48] Nope [05:48] That's what it comes down to wxl [05:48] Unless @acheronuk has suggestions [05:48] that's ridiculous [05:49] This is one of those things that I talked about at BBB. I can sit here and hammer these tests, but only I can because I have the archive access. You can't. It's frustrating. [05:50] baloo-kf5 appears to ALWAYS fail on armhf/i386 [05:50] http://autopkgtest.ubuntu.com/packages/baloo-kf5 [05:50] Ignore the ones marked as Always failed. [05:52] i don't even know how to interpret all these failures for plasma-framework http://autopkgtest.ubuntu.com/packages/plasma-framework/bionic/arm64 http://autopkgtest.ubuntu.com/packages/plasma-framework/bionic/s390x [05:53] Just retried a handful of them [05:55] @wxl, @acheronuk or Santa might be able to help but otherwise it's just a matter of retrying and seeing which ones are legit failures and which ones just need retries. [05:56] One other thing to look into wxl is that Santa hasn't finished the dep bump tooling yet for autopkgtests so there might be some failures caused simply by testing against old build deps [05:56] It happens [05:58] @tsimonq2: so you're telling me i should just hit retry on all of them? [05:58] Just get me or Rik a pastebin with retry links (add &requester=wxl as an arg) and if you give us reasonable assurance that they aren't for nothing, we'll be happy to press buttons. [05:58] @wxl, You *can't* because you don't have upload access to the package [05:58] i'm not sure how to define "nothing" [05:59] Then a step in the right direction would probably be retrying with all-proposed [05:59] how about you just go on there and click them all? that seems to require less effort at least [05:59] I did for a handful of them [06:00] well keep going down the list and then i'll see about making sense out of the rest [06:00] and since you know about the stuff Santa's working on, could you check in with him about it? [06:01] But like I said wxl this will become much less of a problem when the tooling is fixed to bump deps for autopkgtests as well as build deps, because the autopkgtesters have -proposed enabled but have apt pinning so that only the strictly necessary packages are pulled in. [06:01] Hi Santa ;) [06:01] @wxl, I need to go to bed for real this time. [06:02] k. what i'm hearing is "please wait" anyways [06:02] I'm trying but I can't do much for ya right now wxl, sorry :/ [06:02] But if you find some legit failures, by all means, fix it [06:02] Hi from the bed [06:03] @Santa, Sorry if I woke you [06:03] "please wait" rather than "try to poke blindly with a stick though there's probably little hope of any immediate solution" is much preferred :) [06:03] @tsimonq2, That may solve it or not, we will see [06:03] @Santa, Even if it doesn't solve all of it it should pick up some weird failures. [06:04] @tsimonq2, I was already awake, but still in bed haha [06:04] @Santa, Heh ok [06:04] o/ [06:05] nite [06:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ki18n build #33: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/bionic_unstable_ki18n/33/ [09:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1957: SUCCESS in 58 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1957/ [09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1957: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1957/ [09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1957: SUCCESS in 3 min 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1957/ === himcesjf_ is now known as him-cesjf [10:34] tsimonq2 wxl: https://bugs.kde.org/show_bug.cgi?id=387824 [10:34] KDE bug 387824 in general "gwenview fails PlaceTreeModelTest autotest with frameworks 5.4.1" [Normal,Unconfirmed] [11:25] Howdy all [12:24] I'll be around for a limited amount of time until this afternoon. Ping if you need me. [12:33] Ok [14:20] @tsimonq2 so looks like that one needs upstream help, eh ? [14:26] @wxl[m], Yep iirc [14:58] So wxl did you get the nagging emails this morning? :P [14:58] (for frameworks) [15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1958: SUCCESS in 55 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1958/ [15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1958: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1958/ [15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1958: SUCCESS in 3 min 43 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1958/ [16:04] @tsimonq2: i think i got the nagging emails last night [16:07] @wxl, Heh good :P [16:15] @tsimonq2: maaaybe? [16:15] @wxl, It helps you keep on top of it. ;P [16:16] @tsimonq2: i thought the emails that i saw were related to the tests failing, though? [16:17] @wxl, Nope. They now have emails for when things are stuck in proposed. :P [16:17] wxl: ktexteditor may have commits upstream that looks like fixes to it's fail [16:18] @tsimonq2: yeah, and that's what it seemed to be related to, i thought [16:19] @wxl, Right [16:21] @tsimonq2: so what's that have to do with symbols? [16:22] @wxl, ? [16:22] who mentioned symbols? [16:22] i thought someone did, but lastlog is behaving very weird for me and filling my screen with useless garb so perhaps that's old. sorry. i need caffiene [16:23] mmmmm..... coffee [16:23] so anyways i'm back on to "wait and see" XD [16:24] I'll be gone from ~ $hour:30 to $hour+1:00 so don't be mad if you don't see me for a bit. 😉 [16:24] $hour? [16:24] Gone for 30 minutes from half past [16:25] @acheronuk, $hour for me is 10, UTC-6 [16:25] * acheronuk shrugs [16:28] still a lot of running and queued tests, especially BIG ones, so this may take a few days [16:29] frameworks is particularly bad, as most of our stuff depends on so much of it! [16:30] right, so wait, got it XD [16:31] ktexteditor is one that can be looked at now though [16:32] i'll have a looksie [17:50] here's the fail in ktexteditor: https://share.riseup.net/#m8tf_En9gxY2GdZIoog-kg [17:50] tl;dr it's the katesyntax test only [17:51] looks like 14/15 fails [17:52] ah the 15th one is just an init i think [17:52] they are all, not surprisingly, syntax highlighting tests [17:52] so one test (and it's 14 functional subtests, fail)? [17:52] it seems to me they changed the color [17:53] correct [17:53] ues [17:53] example fail: [17:53] *yes [17:53] -
[17:53]  +
[17:53]  that's ---reference +++current
[17:53]  so, a fix?
[17:54]  well i wonder if it's simply intentional. if it is, it's just a matter of updating the tests, from what i can tell
[17:55]  have they updated it upstream since the 5.41 tars were made/tagged?
[18:00]  acheronuk: i got to this but i'm not sure where to find the actual test itself https://cgit.kde.org/ktexteditor.git/tree/autotests/src/katesyntaxtest.cpp
[18:01]  ah i think i found it
[18:02]  there it is https://cgit.kde.org/ktexteditor.git/tree/autotests/input/syntax/rmarkdown/results/example.rmd.reference.html#n11
[18:02]  that's actually for the very last one on the previous paste
[18:03]  how does one blame with cgit?
[18:03]  yes, the reference data paths are shown in that test fail
[18:03]  wxl: maybe have a look at the git log?
[18:03]  https://cgit.kde.org/ktexteditor.git/log/
[18:04]  hahahah
[18:04]  yeah i don't usually do that because it's often searching for a needle in the haystack
[18:04]  BT
[18:04]  BUT i mean
[18:04]  https://cgit.kde.org/ktexteditor.git/commit/autotests/input/syntax/rmarkdown/results?id=210eb236660afe3e13e195faf0a8f719b63c0f53
[18:04]  right at the top
[18:04]  oh
[18:04]  that's the fix
[18:04]  yes, that show the change for just that file
[18:05]  but... that commit changes more
[18:05]  https://cgit.kde.org/ktexteditor.git/commit/?id=210eb236660afe3e13e195faf0a8f719b63c0f53
[18:06]  right
[18:06]  that's the fix
[18:06]  seems so
[18:07]  so i should pull down this one patch then?
[18:08]  to test, yes
[18:08]  there is a link in the commit for a patch
[18:08]  commit	210eb236660afe3e13e195faf0a8f719b63c0f53 (patch)
[18:08]  http://websvn.kde.org/trunk/?rev=210&view=rev | svn://anonsvn.kde.org/home/kde/trunk -r 210
[18:09]  fine, bot
[18:09]  (patch) is a link
[18:09]  https://cgit.kde.org/ktexteditor.git/patch/?id=210eb236660afe3e13e195faf0a8f719b63c0f53
[18:15]  wxl: BTW, I have upgraded this artful box to 5.41 from staging, and so far so good :)
[18:18]  acheronuk: so i need to recreate an autopkgtest environment?
[18:18]  if you want to run the test realistically, yes
[18:19]  too bad we don't have an OpenStack cloud as that seems even easier :)
[18:19]  hehe
[18:22]  ideally you'd run the test yourself anyway
=== claydoh is now known as Guest85401
[18:24]  comparing the test results on build.kde.org for that commit to the previous, it can be seen it fixed the equivalent fail there
[18:24]  so it's a good bet, even if you were not able to test locally
[18:34]  are you advising that i just go ahead and apply the patch?
[18:35]  can you test it?
[18:35]  i can but i'd want to do that at home. this machine is a little crippled from a virtualization perspective
[18:35]  i got a new one on the way but it's not ready yet
[18:36]  there's no way i could run it on the kontainer and connect to it remotely is there?
[18:36]  I'm asking, as I tested it earlier :P
[18:36]  yeah i hear what you're saying. i'd like to test it :)
[18:36]  wxl: probably would work on the container with LXD
[18:37]  i'll try playing around with that. it would be a lot easier for all of us if we could use that as an option
[18:37]  just trying now.....
[18:38]  I usually run locally, as this machine slightly out performs linode for stuff like this
[18:39]  i like the idea of taking my work with me as i go, thus the benefit of the kontainer
[18:39]  indeed
[18:39]  so like i said, i'll give that some effort
[18:40]  seems to be working.....
[18:41]  oh you just got it going eh?
[18:42]  did you have to do anything other than autopkgtest-buildvm-ubuntu-cloud -v?
[18:42]  yeah, well I was playing around with it earlier when I was having local issues with lxd. so giot most of the way to setting it up
[18:43]  s/vm-ubuntu-cloud/-lxd/
[18:44]  autopkgtest-buildvm-ubuntu-cloud would not work for me. (1) from ages ago, the virtualisation on the linode CPUs (or something) doesn't like that and (2) those cloud images are a bit broken at the moment
[18:44]  so I was using lxd
[18:44]  what did you specify for the images?
[18:45]  autopkgtest-build-lxd images:ubuntu/bionic/amd64
[18:45]  k cool :)
[18:45]  then run
[18:45]  autopkgtest ktexteditor --apt-pocket=proposed -U --shell-fail --build-parallel=4 -- lxd autopkgtest/ubuntu/bionic/amd64
[18:46]  that would do the reference run, with the archive package
[18:46]  to see the fail
[18:46]  then do 
[18:46]  ah foo i haven't run lxd yet
[18:46]  init gave me a bad file descriptior issue
[18:46]  i took all the defaults. problem with btrfs maybe?
[18:47]  think mine used zfs
[18:47]  hm
[18:48]  zfs isn't listed as an option i'll figure it out
[18:49]  I probably need to check what I have. Mine was init ages ago, but not set up more than that until today
[18:53]  i wonder if running on bionic is a problem
[18:58]  hmmm. my lxd on linode is using 'dir' for the storage pool!
[18:58]  locally here it's zfs
[18:59]  lxd is confusing
[18:59]  ah
[19:00]  that worked :)
[19:00]  which is why I used to just use thsoe cloud images, locally, with qemu
[19:00]  until that broke today
[19:00]  aha. good :)
[19:01]  building
[19:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #393: STILL FAILING in 3 min 55 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-workspace/393/
[19:28] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-workspace build #158: STILL FAILING in 4 min 57 sec: https://kci.pangea.pub/job/xenial_stable_plasma-workspace/158/
[19:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #394: STILL FAILING in 4 min 47 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-workspace/394/
[19:38] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-workspace build #159: STILL FAILING in 4 min 50 sec: https://kci.pangea.pub/job/xenial_stable_plasma-workspace/159/
[19:56] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #219: STILL FAILING in 32 min: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/219/
[19:56] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #49: STILL FAILING in 33 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/49/
[20:13]  wxl: any luck?
[20:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #355: NOW UNSTABLE in 36 min: https://kci.pangea.pub/job/xenial_unstable_kwin/355/
[20:25] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #50: ABORTED in 23 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/50/
[20:29] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #220: STILL FAILING in 27 min: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/220/
[20:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #38: ABORTED in 4 min 31 sec: https://kci.pangea.pub/job/bionic_unstable_kwin/38/
=== ghostcube_ is now known as ghostcube
[20:55]  acheronuk: unfortunately no https://share.riseup.net/#VcCjjUmOSMG5TNsgeMFgWw
[20:56]  i had the "wicked resolution" when building but everything ended up resolving itself
[21:00] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:00] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #51: FIXED in 30 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/51/
[21:01]  update didn't help
[21:01]  what's your resolve.conf like acheronuk ?
[21:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #356: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/xenial_unstable_kwin/356/
[21:03]  or maybe you have some sort of proxy set up?
[21:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #395: STILL FAILING in 2 min 48 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-workspace/395/
[21:09]  wxl: tried to run it gain, and now not working!
[21:09]  grrrr
[21:09]  same error???
[21:12]  no, mine jut hung at testbed setup
[21:12]  *just
[21:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #396: STILL FAILING in 2 min 48 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-workspace/396/
[21:27] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwin build #210: NOW UNSTABLE in 57 min: https://kci.pangea.pub/job/artful_unstable_kwin/210/
[21:35]  wxl: Upload it to a PPA, I can queue an autopkgtest against that
[21:35]  just hold on
[21:35]  i have a theory
[21:35]  Go ahead wxl but if you run out of ideas, that's a solution ;)
[21:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:50] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #221: FIXED in 23 min: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/221/
[21:51]  grr
[21:51]  i'd really like it to work :(
[21:52]  and now in runs again. lol
[21:52]  are you getting the something wicked garbage?
[21:53]  nope
[21:56]  deleted images and storage and started again
[21:56]  I am not 100% sure what sorted it
[21:59]  ooh
[22:00]  that 10.39.153.1:3142 is an apt proxy
[22:01]  wxl: apt-cacher-ng
[22:10]  cloud images should be fixed on next build run hopefully. so that gives another option, albeit again one that won't work on linode
[22:21]  well commenting out the apt-cacher definition in /etc/apt/conf.d worked just fine
[22:22]  now let's see what happens with the test
[22:26]  it's possible the defaults aren't sufficient
[22:26]  it does seem to think there's a proxy but *shrugs*
[22:36]  this fixes it so it work swith the proxy https://askubuntu.com/questions/895197/how-do-i-cache-packages-for-a-snapcraft-cleanbuild
[22:36]  tl;dr export LXD_ADDRESS=$(ip -4 -o address show dev lxdbr0 | awk -F'[ /]*' '{print $4}') && lxc profile set default environment.http_proxy "http://$LXD_ADDRESS:3128"
[22:36]  of course that only does ipv4 but oh well
[22:37]  so now how do i apply the patch to the test?
[22:39]  wxl: You patch the source using quilt.
[22:39]  and throw it in a ppa?
[22:39]  i.e. extract the tar and use https://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
[22:39]  Well, that too
[22:39]  (enable all possible arches)
[22:40]  how would i do that with autopkgtest's lxd backend, tho?
[22:40]  git-clone-all -s ktexteditor
[22:40]  cd ktexteditor/git/
[22:40]  wxl: I can retry the tests using the package from your PPA
[22:41]  quilt import path_to_your_patch
[22:41]  gbp-ppa
[22:42]  then run the autotest with the .dsc and the package argument
[22:42]  *as the
[22:42]  AH
[22:42]  you're awesome
[22:42]  or if not using git, you can 'pull-lp-source ktextedit'
[22:43]  do the same import in that
[22:43]  and then do 'debuild -S -sa -us -uc' to make a quick source build to test
[22:44]   Wow, good evening, it's been developed factory in here today, good skills 😁
[22:44]  :)
[22:44]  :)
[22:44]  :)
[22:44]  lol
[22:44]  we need to document this lxd autopkgtesting. this is good stuff.
[22:44]   good Stuff!!!
[22:45]  santa has a page mentioning lcx on the wiki. so we can add the better new lxd way, if it's not there now
[22:45]  point me at that and i'll edit away
[22:46]  https://phabricator.kde.org/w/kubuntu/autopkgtests/staging_howto/
[22:46]  danke
[22:46]  it's actually meant to be for testing against a ppa, but includes that lxc bit
[22:46]  so maybe that could be separated out
[22:46]  if i put the docs in there, at least we have it to refer to and someone else can separate it out if they want
[22:47]  ok
[22:51]   (Document) https://irc-attachments.kde.org/T9vZSH7X/file_3802.pdf
[22:51]   @tsimonq2, This might help wxl
[22:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #41: FIXED in 40 min: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/41/
[22:54]  omgerd
[22:54]  This is why we need it on a central server, so when Santa needs to do server maintenance we can still have that
[22:54]  not as bad as it looks
[22:54]  Right
[22:55]  A major part of this is the fact that the queues are huge...
[22:55]  We'll have a better look once all the tests are ran
[22:55]  yeah, I can prod to fix some now, but more of the same may fail later
[22:57]  how did you say to get the patch from cgit? or should i just copy the diffstat?
[22:59]   (Photo, 665x436) https://irc-attachments.kde.org/rRLJ3lmw/file_3804.jpg
[23:01]  whatever works though
[23:03]  tsimonq2: I'm half asleep, so can you make sure this gets done if time?
[23:03]  acheronuk: sure
[23:06]  https://share.riseup.net/#hGdzCoQZsDmW6vqJgDaFKg
[23:06]  that's.... weird.....
[23:07]  also weird that lp:ka says i registered it XD
[23:09]  that happens even when called gbp-ppa with -d bionic 
[23:09]  oh wait
[23:09]  wrong location
[23:10]  nooo...
[23:11]  and yes i did git-clone-all -s ktexteditor -b kubuntu_bionic_archive
[23:40]  i just don't understand how this worked for all of frameworks but not for a single package.. i.. don't even
[23:50]  are you in the git folder>
[23:50]  yeah
[23:50]  aren't you supposed to be in bed tho? XD
[23:51]  I am
[23:51]  awww how cute :)
[23:51]  laptops are evil
[23:53]  i'm exclusively phone in bed
[23:55]  has bionic?
[23:55]   /usr/lib/python3/dist-packages/lib/ubuntu_info.py
[23:56]  it's bionic if that's what you mean
[23:56]  and that file exists
[23:57]  https://git.launchpad.net/ka/tree/libka/ubuntu_info.py#n20
[23:57]      "bionic": "18.04",
[23:57]  has that?