Wednesday, 2018-07-18

*** zerocoolback has joined #kata-dev00:25
*** bkslsh has joined #kata-dev00:34
*** zerocoolback has quit IRC00:46
*** zerocoolback has joined #kata-dev00:46
*** zerocoolback has quit IRC00:50
*** marst has quit IRC00:51
*** lamego has joined #kata-dev00:56
*** marst has joined #kata-dev01:05
*** lamego has left #kata-dev01:05
*** bkslsh has quit IRC01:14
*** zerocoolback has joined #kata-dev01:59
*** dlw has joined #kata-dev02:30
*** zerocoolback has quit IRC03:06
*** zerocoolback has joined #kata-dev03:40
*** lpetrut has joined #kata-dev03:50
*** sjas has joined #kata-dev04:09
*** sjas_ has quit IRC04:12
*** zerocoolback has quit IRC04:14
*** zerocoolback has joined #kata-dev04:39
*** lpetrut has quit IRC04:39
*** lpetrut has joined #kata-dev04:42
*** zerocoolback has quit IRC04:45
*** zerocoolback has joined #kata-dev04:47
*** lpetrut has quit IRC04:54
*** fdegir has quit IRC05:16
*** din has quit IRC05:16
*** fdegir has joined #kata-dev05:35
*** din has joined #kata-dev05:35
*** core has quit IRC05:37
*** core has joined #kata-dev05:37
*** zerocoolback has quit IRC06:18
*** zerocoolback has joined #kata-dev06:18
*** zerocoolback has quit IRC06:18
*** zerocoolback has joined #kata-dev06:19
*** zerocoolback has joined #kata-dev06:20
*** zerocoolback has quit IRC06:20
*** zerocoolback has joined #kata-dev06:20
*** zerocoolback has quit IRC06:21
*** dlw has quit IRC06:21
*** zerocoolback has joined #kata-dev06:21
*** dlw has joined #kata-dev06:21
*** zerocoolback has quit IRC06:21
*** lpetrut has joined #kata-dev06:22
*** jugs has quit IRC06:41
*** jugs has joined #kata-dev06:42
*** dklyle has quit IRC07:35
*** sameo has quit IRC07:49
*** davidgiluk has joined #kata-dev08:03
*** gwhaley has joined #kata-dev08:06
*** sameo has joined #kata-dev08:22
*** dlw has quit IRC09:10
*** dlw has joined #kata-dev09:10
*** dlw1 has joined #kata-dev10:13
*** dlw has quit IRC10:13
*** dlw1 is now known as dlw10:13
*** gwhaley has quit IRC10:58
*** dlw has quit IRC11:08
*** changcheng has joined #kata-dev11:21
*** JerryLiu has quit IRC11:21
*** sameo has quit IRC11:24
*** changcheng has quit IRC11:43
*** changcheng has joined #kata-dev11:46
*** zerocoolback has joined #kata-dev11:50
*** fuentess has joined #kata-dev11:53
*** zerocoolback has quit IRC11:56
*** zerocool_ has joined #kata-dev11:56
*** devimc has joined #kata-dev11:57
*** fuentess1 has joined #kata-dev12:07
*** fuentess1 has quit IRC12:08
*** gwhaley has joined #kata-dev12:14
* davidgiluk is curious where the connection between DisableModern on virtio devices and nested came from12:15
gwhaleyhi @davidgiluk: iirc, there was a bug/feature that caused 'fast' to not work in the nested situation. iirc, it was reported and fixed upstream (kernel) - but I presume it may have not trickled through all the distros yet.12:21
gwhaleyref: https://github.com/intel/govmm/pull/11 but sadly it does not have much detail :-(12:21
gwhaleyhttps://github.com/containers/virtcontainers/pull/66412:22
davidgilukthanks!12:28
davidgilukhmm that references 663 that mentions azure VMs12:30
gwhaleyI don't remember where we (first?) saw it - mcastelino might, but he is not here right now .... devimc may remember some details?12:35
devimc@davidgiluk, @gwhaley sorry, what was the question?12:36
devimcwhy DisableModern ?12:36
gwhaleyhi devimc - why did we have to ... ^^ yeah, for nested - was an upstream kernel limitation iirc - do you remember any details, and on what nested service etc.?12:37
devimctechnical details? no, but DisableModern=true is to make happy azure VMs12:38
davidgilukok, so it sounds just like an azure special - useful one to know12:41
gwhaleygive me a moment - I might have a link...12:41
gwhaleypossibly fixed with https://patchwork.kernel.org/patch/10330065/12:42
gwhaleygrabbed from https://bugs.launchpad.net/qemu/+bug/163621712:42
openstackLaunchpad bug 1636217 in QEMU "qemu-kvm 2.7 does not boot kvm VMs with virtio on top of VMware ESX" [Undecided,Fix released]12:42
gwhaleythat EPT reference sounds familiar12:43
davidgilukoh ok; that's fun12:44
kata-irc-bot1<bergwolf> Do you have refs for the upstream bug/feature? I can't find it in github log12:55
kata-irc-bot1<bergwolf> oops, just saw the whole conversation. sorry for the noise...12:57
*** mestery has quit IRC13:18
*** mestery has joined #kata-dev13:18
*** dklyle has joined #kata-dev13:50
*** sameo has joined #kata-dev13:51
*** lamego has joined #kata-dev13:57
*** dklyle has quit IRC14:00
*** eernst has joined #kata-dev14:14
*** annabelleB has joined #kata-dev14:35
*** lpetrut has quit IRC14:47
*** sgordon has quit IRC14:51
clarkbsalvador.fuentes: it looked like unittest addition was working but then crio failed. Are you happy enough with that result or should I avoid merging the job update?15:03
kata-irc-bot1<salvador.fuentes> clarkb: I think we can merge, I am seeing issues with the checkcommits tool (it is reporting that there are zero commits to verify).  I think it is mainly because of the way zuul is managing the git branches.15:06
clarkbis it trying to look at diffs if on unmerged code?15:07
*** lpetrut has joined #kata-dev15:16
gwhaleyclarkb: checkcommits tries to locate the patches that are in the PR it is checking so it can do sanity checks on them (formatting, format etc.) - so it tries to identify what is different between HEAD / master and the branch to be checked.15:22
gwhaleywe had to do a little smarts as different CIs set things up differently in the build branches. Maybe we will have to educate it about ZUUL as well15:23
clarkbcouldn't you just do sanity checking on the whole since it includes the PR patches?15:23
gwhaleyTravis was... the 'worst' so far...15:23
gwhaleyclarkb - yes, and no. I don't think we can guarantee that all historical code or commits fits with our current requirements for instance15:23
clarkbwell you wouldn't step through the tree, just that the current commit meets the standards15:24
clarkbso if you got everything up to the standard and enforced thsi check you just check the current checkout each time15:24
gwhaleyright - but it is not just one commit - it is the series of commits that make up the PR - they can be multi-commit15:24
clarkbI understand but it is a DAG and the tip of the PR will include the other commits as well15:25
clarkband if you care about intermediate states the PR model isn't very good :/15:25
gwhaleyAh, right - that is how Zuul works isn't it iirc - it is a pile of all current pending commits? (sorry if pile is not quite the right phrase...)15:26
gwhaleyyeah, we don't enforce that bisects work in our codebase btw - as long as the final commit in a PR series works then we are happy. We do try to have some standards though ;-)15:26
gwhaleyhmm, so, maybe right now we might have to disable checkcommits in Zuul whilst we stare at it and the Zuul workflow to figure out if anything 'clever' can be done15:27
clarkbgwhaley: there are sort of two related things here. THe first is PR workflows (on their own) are really bad for enforcing the type of thing you describe because intermediate states aren't really enforceable. Gerrit's discrete change model is better (imo) as it forces you to consider each commit in series15:27
clarkbthe other is that yes Zuul tries to give you speculative future states to test against because code bases (at least with git) move forward only15:28
clarkbWhat you are really interested in testing is the commit that will be created when you "merge" to master15:28
clarkbnot necesarily the state a commit was pushed in15:28
gwhaleyclarkb - yes, but, checkcommits is really more of a 'style checker' - so it is only really checking your commits are 'well formed' https://github.com/kata-containers/tests/tree/master/cmd/checkcommits#overview15:29
*** annabelleB has quit IRC15:29
gwhaleywe use it in conjunction with (to fill some gaps of) 'pullapprove'.15:29
gwhaleyit checks the commit messages, not the code  :-)15:30
* gwhaley spies stefanha...15:30
clarkbIn this case a PR to kata-containers/proxy proposed to the master branch would look like Master_0 <- PR_A <- PR_B. If while reviewing that PR some other PR merges to master what Zuul will test is Master_1 <- PR_A' <- PR_B' and in the test instance master will be checked out to PR_B'15:30
*** annabelleB has joined #kata-dev15:30
clarkbgwhaley: aha! that is what I was missing you are looking at commits themselves not their contents15:31
gwhaleyHi stefanha - have you seen https://github.com/kata-containers/agent/pull/263 - I wonder if you have any thoughts/insight - as you were <cough> implicated on the original qemu/glib hang up diagnosis, and this feels very similar15:31
gwhaleyclarkb: :-)15:31
clarkbPR_B' on master is not what upstream code repo looks like, but it is what it would look like if that PR merged in the future15:31
clarkband we test that rather than PR_B which is now a state that can never materialize15:31
clarkb(I actually think github does some of this auto rebasing for you too now, but forget the details)15:32
*** lpetrut has quit IRC15:37
clarkbgwhaley: for this commit check to function properly it needs to know what the merge target is and what sha1 is already merged to that target?15:38
gwhaleywe really need @jodh on this, but he is out until next week. What it needs is to be able to figure out which commits come from the PR under test. I think it currently does that by asking git to tell it the difference15:40
gwhaleybetween the current branch and the master - but, we can adapt it if we need for Zuul if we have to I think15:41
clarkbI'm trying to confirm this, but my memory is that while 'master' is the speculative state there is a refs/origin/master (or similar) that has the target branches existing state. I think it may be as simple as git log $BRANCH..refs/origin/$BRANCH (but will figure out those details15:42
*** devimc has quit IRC15:43
*** lpetrut has joined #kata-dev15:55
clarkbhttps://zuul-ci.org/docs/zuul/user/jobs.html#git-repositories seems to confirm it15:59
*** devimc has joined #kata-dev16:01
gwhaleycool - we probably need to open an Issue on the tests repo for https://github.com/kata-containers/tests/tree/master/cmd/checkcommits to gather details - are you up for opening that clarkb with the Zuul details?16:02
clarkbgwhaley: yup I can put that together in a bit.16:02
gwhaleycc @fuentess :-)16:03
*** zerocool_ has quit IRC16:13
*** zerocoolback has joined #kata-dev16:14
*** zerocoolback has quit IRC16:14
*** lpetrut has quit IRC16:17
*** sameo has quit IRC16:35
*** sameo has joined #kata-dev17:12
*** gwhaley has quit IRC17:31
*** annabelleB has quit IRC17:39
clarkbhttps://github.com/kata-containers/tests/issues/511 filed for the above discussion17:46
*** annabelleB has joined #kata-dev17:46
*** dklyle has joined #kata-dev17:55
*** dklyle has quit IRC18:01
*** dklyle has joined #kata-dev18:27
*** lpetrut has joined #kata-dev18:28
*** eernst has quit IRC18:38
*** libregeekingkid has joined #kata-dev18:39
*** annabelleB has quit IRC19:19
*** dklyle has quit IRC19:23
*** annabelleB has joined #kata-dev19:24
*** annabelleB has quit IRC19:34
*** davidgiluk has quit IRC19:37
*** annabelleB has joined #kata-dev19:41
*** annabelleB has quit IRC19:51
*** devimc has quit IRC20:03
*** eernst has joined #kata-dev20:17
*** dklyle has joined #kata-dev20:39
*** lpetrut has quit IRC20:48
*** dklyle has quit IRC21:42
*** dklyle has joined #kata-dev21:45
*** david-lyle has joined #kata-dev21:53
*** dklyle has quit IRC21:54
*** david-lyle has quit IRC22:31
*** libregeekingkid has quit IRC22:32
*** eernst has quit IRC22:49
*** annabelleB has joined #kata-dev22:54
*** annabelleB has quit IRC22:58
*** annabelleB has joined #kata-dev23:05
*** dklyle has joined #kata-dev23:09
*** eernst has joined #kata-dev23:30
*** annabelleB has quit IRC23:33
*** annabelleB has joined #kata-dev23:44

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