18:30:13 #startmeeting jenkins.debian.org 18:30:13 Meeting started Wed Aug 23 18:30:13 2017 UTC. The chair is h01ger. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:30:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:30:41 o/ 18:30:57 what's the agenda? Anything peculiar? 18:31:05 * h01ger looks up the agenda 18:31:12 its in j.d.n.git/TODO 18:31:57 status? 18:32:21 #topic 18:32:46 * h01ger is bad at multitasking right now 18:33:11 #topic jenkins.d.n status 18:33:20 munin is too noisy 18:33:30 and the kernel crashes, which I deem more important 18:33:31 anything else is fine afaics / remember 18:33:42 mapreri: often? 18:33:58 just haven't got the time to investigate what part of the kernel crashes.. there are two dmesg saved in /root/ 18:34:11 h01ger: about two times per month, starting in june. 18:34:26 in /root/ there are two crash_$date.dmesg from today and the last time 18:34:34 so with stretch 18:34:37 (haven't got the ssh key handy right now) 18:34:47 yes, that's the timeline 18:35:05 i suppose we should file a bug 18:35:13 when it happens it requires either a sysrq-reboot, or a hard power cycle 18:35:59 before filing a bug it would at the very least require reading the crash backtrace, but things sidetracked me (+ about to be off for a while starting next week, see -private@) :) 18:36:05 ouch 18:37:00 symptoms of that crash are: `df` hangs, systemctl hangs most of the time, very high (> 300, or even > 400 today) load but no processes actually doing anything 18:37:27 that also means, jenkins jobs running on jenkins.d.n itself stalled 18:37:31 i'd file the bug anyway even without reading the crash backtrace 18:37:44 why stalled? crashed i'd understand 18:38:56 no idea, guess the jenkins logs could be looked to see where it blocked (I always "rushed" to recover it rather than look at the jobs themselves), but all the times the executors were filled and most of the jobs had the "red" line indicating a too high running time 18:39:57 incidentally, since today's reboot munin's cronjob has been quited for some reason… (no idea how it relates) 18:43:16 nice 18:43:21 must be lower load 18:43:32 anything else? 18:43:49 nothing comes to my mind 18:44:25 #topic jenkins.d.o migration status 18:44:33 we had a bof at debconf 18:44:38 debconf17 that is 18:44:45 was that recorded? 18:45:06 I've downloaded a few videos, planning to watch them sometime in September 18:45:09 http://meetings-archive.debian.net/pub/debian-meetings/2017/debconf17/let-s-maintain-jenkins-debian-org-as-a-t.vp8.webm 18:45:22 (let-s-maintain-jenkins-debian-org-as-a-team was the full title) 18:45:28 ok, already downloaded that one 18:45:44 #info slides are in jenkins.d.n.git/usercontent/presentation 18:45:51 #info slides are in jenkins.d.n.git/usercontent/presentations 18:46:06 basically the next step is to finally deploy jobs there 18:46:10 so nothing new :/ 18:46:25 jerea.d.o is also already running stretch 18:46:54 I also updated the plugins few days ago, fwiw 18:47:09 (not that it matters, but figured I'd report while we are at it) 18:47:46 nice 18:47:49 guess there are no updates. And I know I can't work on it during the next month. 18:48:18 same here, at least for the next 3 weeks 18:48:48 oh well 18:48:54 #topic anything else? 18:49:04 about the sprint… 18:49:19 do you think it would be possible to chain it to rsw3? 18:49:42 like, do it the weekend before of after (assuming rsw3 will be middle of the week like the other times) 18:50:15 that would make quite easier for me to attend such thing, I expect. 18:52:49 thats a nice idea 18:53:06 +i suppose that would work 18:53:13 probably after though 18:53:54 added to TODO, we mostly need to think about it and make it happen 18:54:29 mapreri: assuming just the two of us would be "good enough" / better than nothing, i'd be very glad if more people joined! 18:54:45 of course :) 18:56:27 h01ger: if there is nothing else, I'd like to move on to other things in RL :) 18:56:47 yeah, me too 18:56:57 thanks for attending or reading logs! 18:57:00 #endmeeting