Monday, 2019-03-25

*** changcheng has quit IRC07:16
*** changcheng has joined #kata-dev07:18
*** zhenyuw has quit IRC07:25
*** zhenyuw has joined #kata-dev07:25
*** jodh has joined #kata-dev07:36
*** sgarzare has joined #kata-dev08:06
*** sameo has joined #kata-dev08:32
*** tmhoang has joined #kata-dev08:38
*** davidgiluk has joined #kata-dev09:02
*** gwhaley has joined #kata-dev10:54
*** sgarzare has quit IRC11:26
*** sgarzare has joined #kata-dev11:31
*** gwhaley has quit IRC12:18
*** lpetrut has joined #kata-dev12:26
*** dklyle has joined #kata-dev13:04
*** gwhaley has joined #kata-dev13:14
*** devimc has joined #kata-dev13:14
*** irclogbot_0 has joined #kata-dev13:27
*** fuentess has joined #kata-dev13:30
*** altlogbot_1 has quit IRC13:31
*** altlogbot_2 has joined #kata-dev13:31
*** dklyle has quit IRC13:37
*** irclogbot_0 has quit IRC13:38
*** irclogbot_0 has joined #kata-dev13:38
kata-irc-bot<graham.whaley> Hi @xu @eric.ernst (and all) - ooi, can somebody tell me the difference between these two kata containerd howto docs we have in our repo: https://github.com/kata-containers/documentation/blob/master/how-to/containerd-kata.md and https://github.com/kata-containers/documentation/blob/master/how-to/how-to-use-k8s-with-cri-containerd-and-kata.md13:55
kata-irc-bot<graham.whaley> I'm thinking one is for containerdv2, and the other <v2...13:56
kata-irc-bot<graham.whaley> in which case, probably need to make that clearer in the doc titles13:56
kata-irc-bot<graham.whaley> and add whichever one is missing to the document repo top level index/toc (or mark it as deprecated).13:56
kata-irc-bot<graham.whaley> Just trying to clarify where I would send somebody if they wanted to run up k8s containerd kata instead of cri-o :slightly_smiling_face:13:56
kata-irc-bot<eric.ernst> I think the should probably be combined, and perhaps introduce a second document describing runtimeClass14:52
*** waz0wski has quit IRC15:17
*** dklyle has joined #kata-dev15:20
*** lpetrut has quit IRC15:32
*** waz0wski has joined #kata-dev15:33
*** tmhoang has quit IRC15:46
*** sameo has quit IRC15:51
*** igordc has joined #kata-dev16:32
*** igordc has quit IRC16:32
*** igordc has joined #kata-dev16:58
*** sgarzare has quit IRC17:43
kata-irc-bot<graham.whaley> And then I came across another k8s section - in the dev guide - which may or may not be amalgamated with the above two as well: https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#run-kata-containers-with-kubernetes17:44
*** jodh has quit IRC18:06
*** sameo has joined #kata-dev18:39
*** gwhaley has quit IRC18:40
kata-irc-bot<gmmaharaj> @salvador.fuentes i always check the output of travis before i kick the the CI to test patches. for some reason the issues that was mentioned by @teawater was not visible there. talking in reference to https://github.com/kata-containers/runtime/pull/137219:00
kata-irc-bot<gmmaharaj> is there somewhere else i should be looking? or am i missing something extremely obvious?19:00
kata-irc-bot<salvador.fuentes> @gmmaharaj you should see the failed status of travis directly in the PR, there are different jobs inside the travis build, so one of them was the one failing, now I see both jobs passed19:51
*** davidgiluk has quit IRC19:55
kata-irc-bot<gmmaharaj> @salvador.fuentes yeah.. wasn't sure where the ppc64 failure came from.20:13
kata-irc-bot<gmmaharaj> aah well.. seems it is not there now.20:14
kata-irc-bot<salvador.fuentes> @gmmaharaj it is actually there, but not very visible20:14
kata-irc-bot<salvador.fuentes> https://travis-ci.org/kata-containers/runtime/builds/51103649220:14
kata-irc-bot<salvador.fuentes> you will see 2 jobs there20:14
kata-irc-bot<salvador.fuentes> one of them is x86 and the other is ppc20:14
kata-irc-bot<gmmaharaj> right.20:15
kata-irc-bot<salvador.fuentes> you can move your mouse to the tux image and a label will appear20:15
kata-irc-bot<gmmaharaj> the ppc if i remember right was always failing cause of yq.20:15
kata-irc-bot<gmmaharaj> guess that is fixed now.20:15
kata-irc-bot<salvador.fuentes> yeah, fixed over the weekend I think20:15
kata-irc-bot<gmmaharaj> which explains the linter actually running and finding issues.20:15
kata-irc-bot<salvador.fuentes> right :slightly_smiling_face:20:15
kata-irc-bot<gmmaharaj> bah!! CI failed again20:16
kata-irc-bot<salvador.fuentes> and thanks for fixing those, now k8s installation is broken20:16
kata-irc-botAction: gmmaharaj goes to check why his patch is failing.20:16
kata-irc-bot<gmmaharaj> ROFL20:16
kata-irc-bot<salvador.fuentes> https://github.com/kubernetes/kubernetes/issues/7568320:16
kata-irc-bot<salvador.fuentes> will add a workaround for the CI until it is fixed...20:16
kata-irc-bot<gmmaharaj> @salvador.fuentes http://jenkins.katacontainers.io/job/kata-containers-runtime-fedora-PR/1737/consoleText20:16
kata-irc-bot<gmmaharaj> are you able to see what caused that job to fail?20:17
kata-irc-bot<gmmaharaj> aha!!20:17
kata-irc-bot<gmmaharaj> that's k8s failing isn';t it?20:17
kata-irc-bot<salvador.fuentes> yeahh, k8s installation20:17
kata-irc-bot<gmmaharaj>20:17
kata-irc-bot<gmmaharaj> sooo.. should i re-kick CI now or should i wait for the workaround to land?20:17
kata-irc-bot<salvador.fuentes> no, please wait for my workaround20:18
kata-irc-bot<gmmaharaj> cool.. will do!20:19
kata-irc-bot<gmmaharaj> cause without the lint patch landing in  runtime, that repo is hosed ! :(20:19
*** devimc has quit IRC22:52

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!