Tuesday, 2020-03-31

*** pcaruana has quit IRC00:04
*** pcaruana has joined #kata-dev00:16
*** jugs1 has quit IRC03:31
*** jugs1 has joined #kata-dev03:34
*** jugs1 has quit IRC04:29
*** jugs1 has joined #kata-dev04:30
*** sameo has joined #kata-dev05:15
*** dklyle has quit IRC06:41
*** sgarzare has joined #kata-dev07:01
*** jodh has joined #kata-dev07:04
kata-irc-bot<fidencio> I wonder why `jenkins-ci-ubuntu-18-04 Expected — Waiting for status to be reported` takes so long to finish and whether there's a simple way to view where it got stuck (in case it got stuck)07:58
*** davidgiluk has joined #kata-dev08:03
*** gwhaley has joined #kata-dev08:04
kata-irc-bot<graham.whaley> @fidencio hmm, normally afaik the status is updated fairly quickly - you can always go look directly on the jenkins to see if it is in a queue or finished. You can find the link to the jenkins by following the 'status' link of any previously completed job (such as on another PR).08:09
kata-irc-bot<graham.whaley> also..... I think you get the 'waiting for status' before the CI has been triggered - it does not auto-trigger, somebody has to '\test` it etc.08:10
kata-irc-bot<fidencio> I've added a '\test', which theoretically should trigger the CI (considering I've been given reviewer rights)08:15
kata-irc-bot<fidencio> Let's  see how it goes.08:15
kata-irc-bot<graham.whaley> In case you have not seen this @fidencio, here is a list of all the trigger words etc. https://github.com/kata-containers/community/wiki/Controlling-the-CI08:21
kata-irc-bot<graham.whaley> If your `/test` didn't work... (heh, I forget which / or \ it is - too early).... then we can re-check the github settings - it is a little tricky to get them all right ....08:22
kata-irc-bot<fidencio> @graham.whaley, @james.o.hunt pointed that to me. Cool, it seems that now all the tests are running.08:22
kata-irc-bot<graham.whaley> excellent. Sometimes we don't trigger them all - it depends on the PR. Sometimes we'll just trigger the one(s) relevant to the PR or just the ones needed to allow merge (such as /test-ubuntu)08:23
kata-irc-bot<graham.whaley> as CI resource ultimately is not quite free ;)08:23
kata-irc-bot<fidencio> Meanwhile, let me retest the latest version of Dan's patches on my local rawhide box08:23
kata-irc-bot<fidencio> Yeah, I've been reminded about that. :(08:24
kata-irc-bot<graham.whaley> np. it's not obvious or documented ;)08:24
kata-irc-bot<fidencio> Okay, dropped my notes there. Still not sure whether I have the correct permissions to formally approve a PR. But that can be fixed later on, in case something is wrong.08:57
gwhaley@fidenco: it looks like you are now part of the kata org, but your ack did not count on https://github.com/kata-containers/runtime/pull/2503 as you are probably not part of that 'team'. There are teams (sets) of folks who's approvals count for each repo. So, we should decide which repos you have ack power in...09:04
kata-irc-bot<fidencio> I see. :slightly_smiling_face: Yeah, I'm mostly doing work and reviewing stuff on osbuilder / runtime / agent, as those (at least for now) are the parts which have affected Fedora / Fedora CoreOS and needed changes. But, of course, this is up to the team to decide and can be done later on (based on the quantity / quality of the reviews provided).09:08
kata-irc-bot<fidencio> One thing that I usually do on the projects I maintain (as libosinfo), and obviously I'm not going to try to force it here, is if the person providing the patches agrees with really simple changes / nitpicks, I usually do that myself before merging rather than requiring the person to update the PR.09:10
kata-irc-bot<graham.whaley> @fidencio so, you mean the 'maintainer' can apply the small changes and modify the PR before landing it - yeah, that is something we do very very rarely in Kata. I think we'd prefer submitters update their PRs - given we have a lot of submissions and a lot of maintainers, it could get quite confusing otherwise.10:19
kata-irc-bot<fidencio> Yeah, that's usually what I do in the projects I work on, mainly on really small issues ... such as, "there's a typo here"  or things like that10:56
kata-irc-bot<fidencio> Tend to remove a little bit the burden the contributors (mainly if it's their very few first contributions), although adding the burden on the maintainer10:57
*** ailan has joined #kata-dev11:03
*** jugs1 has quit IRC12:44
*** dklyle has joined #kata-dev12:58
*** devimc has joined #kata-dev13:27
*** crobinso has joined #kata-dev13:43
*** jugs has joined #kata-dev14:01
*** crobinso has quit IRC14:15
*** fuentess has joined #kata-dev14:43
kata-irc-bot<fidencio> @gabriela.cervantes.te, so let me just be sure I understand correctly the issue you mentioned me there. • You're using a RHEL-7.6 image • No subscription attached • EPEL is added • `sudo yum update` fails because of `moreutils` Do I understand everything right?15:47
kata-irc-bot<fidencio> So, before start debugging this (which I will), I have to ask ... is there a specific reason to not have a subscription attached? If the reason is "we don't way to pay for one", which is a quite valid one, I'd strongly recommend taking a look at: https://developers.redhat.com/articles/getting-red-hat-developer-subscription-what-rhel-users-need-know/15:49
kata-irc-bot<gabriela.cervantes.te> @fidencio it is failing the yum update, yes we can't pay for one15:49
kata-irc-bot<fidencio> Red Hat Developer Subscription could be used15:49
kata-irc-bot<fidencio> For free :slightly_smiling_face:15:50
kata-irc-bot<fidencio> I can even check internally that there's no problem using it in the CI15:50
kata-irc-bot<fidencio> Anyways, I'll start debugging the issue and will update you about the Red Hat Developer Subscription15:50
kata-irc-bot<gabriela.cervantes.te> however, I am wondering how it will work for the CI, as we are launching new VMs for each repository15:51
kata-irc-bot<fidencio> Do we have control on the create / delete phase? If so, I guess we could easily attach / detach the subscription before each phase15:51
kata-irc-bot<fidencio> I'll bring this up internally and see what can be done, and make sure whether it can be used in this case15:52
kata-irc-bot<gabriela.cervantes.te> ok thanks15:52
kata-irc-bot<fidencio> Okay, about the issue itself, I'll need some time, but I'll get back to you soon. Thanks for pointing that at our direction!15:53
kata-irc-bot<gabriela.cervantes.te> your welcome @fidencio15:53
*** crobinso has joined #kata-dev16:25
*** pcaruana has quit IRC16:56
kata-irc-bot<fidencio> @gabriela.cervantes.te, I wonder how it has ever worked. I don't have access to the Azure images of RHEL, but I'd be interested on what are the repos set up there16:58
*** jodh has quit IRC17:03
*** pcaruana has joined #kata-dev17:10
*** sgarzare has quit IRC17:31
*** kata-irc-bot has quit IRC17:52
*** kata-irc-bot1 has joined #kata-dev17:52
*** fuentess has quit IRC17:54
*** th0din has quit IRC17:54
*** th0din has joined #kata-dev18:31
*** davidgiluk has quit IRC19:19
*** gwhaley has quit IRC19:31
kata-irc-bot1<gabriela.cervantes.te> @fidencio here it is the list https://paste.centos.org/view/7afcb2bc19:44
*** ailan has quit IRC19:58
kata-irc-bot1<fidencio> • @gabriela.cervantes.te, and did it work in the past?19:59
kata-irc-bot1<fidencio> Let me add a comment in the issue, it's better20:01
kata-irc-bot1<gabriela.cervantes.te> yes20:01
kata-irc-bot1<gabriela.cervantes.te> it was working20:01
kata-irc-bot1<fidencio> Okay, added the comment there.20:11
kata-irc-bot1<gabriela.cervantes.te> @fidencio I will disable RHEL CI to avoid the failures20:13
kata-irc-bot1<fidencio> @gabriela.cervantes.te this seems to be the best to do, at least temporarily.20:36
kata-irc-bot1<fidencio> would be good to not have it ditched forever, though.20:36
kata-irc-bot1<fidencio> Okay, let me call it a day! Take care everyone!20:37
kata-irc-bot1<gabriela.cervantes.te> ok thanks20:39
*** sameo has quit IRC21:17
*** sameo has joined #kata-dev21:35
*** crobinso has quit IRC21:58
*** devimc has quit IRC22:08
kata-irc-bot1<gabriela.cervantes.te> @fidencio, I reviewed the azure help and I do not think is going to be easy to solve the RHEL issue as everything is related with problems in stop star create boot vms and so on22:13

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