Hi Gabriel, Thank you. Will take a look at this patch.
-Hongjun From: Gabriel Ganne [mailto:gabriel.ga...@enea.com] Sent: Wednesday, December 20, 2017 5:12 PM To: Ni, Hongjun <hongjun...@intel.com>; vpp-dev@lists.fd.io Subject: Re: kube-proxy test fail Oh, I understand. Sorry. Well, since I had a look, I came up with a few small modifications to make the tests pass but fail instead of getting stuck in the lock. It's all here: https://gerrit.fd.io/r/c/9880/ if you don't mind having a look. It also seems to make the NAT66 tests fall into place somehow. Best regards, -- Gabriel Ganne ________________________________ From: Ni, Hongjun <hongjun...@intel.com<mailto:hongjun...@intel.com>> Sent: Wednesday, December 20, 2017 9:49:15 AM To: Gabriel Ganne; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: RE: kube-proxy test fail Hi Gabriel, Currently, kube-proxy plugin only supports NAT44, so skip other test cases. NAT66, NAT46 and NAT64 will be added later. Thanks, Hongjun From: Gabriel Ganne [mailto:gabriel.ga...@enea.com] Sent: Wednesday, December 20, 2017 4:03 PM To: Ni, Hongjun <hongjun...@intel.com<mailto:hongjun...@intel.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: Re: kube-proxy test fail I believe this does not run the extended tests, and therefore not the kubeproxy tests. I mean, this runs NAT44, but skips NAT46, NAT64, and NAT66. You need to add EXTENDED_TESTS=yes, or use the test-all target to run the other three : make test TEST=test_kubeproxy EXTENDED_TESTS=yes make test-all TEST=test_kubeproxy Best regards, -- Gabriel Ganne ________________________________ From: Ni, Hongjun <hongjun...@intel.com<mailto:hongjun...@intel.com>> Sent: Wednesday, December 20, 2017 4:52:39 AM To: Gabriel Ganne; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: RE: kube-proxy test fail Hi Gabriel, I used below command and it works well: make test TEST=test_kubeproxy Could you give it a try? Thanks, Hongjun From: Gabriel Ganne [mailto:gabriel.ga...@enea.com] Sent: Tuesday, December 19, 2017 8:54 PM To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; Ni, Hongjun <hongjun...@intel.com<mailto:hongjun...@intel.com>> Subject: kube-proxy test fail Hi Hongjun, I just ran the kube-proxy tests and I end up stuck in kp_vip_find_index() while processing a cli command. Below is the command I used and the backtrace I get. make test-all V=2 TEST=*.TestKP.* ... 0x0000ffff7eaa9c04 in kp_vip_find_index (prefix=prefix@entry=0xffff7ec3dbe8, plen=104 'h', vip_index=vip_index@entry=0xffff7ec3dbbc) at /home/gannega/vpp/build-data/../src/plugins/kubeproxy/kp.c:457 457 kp_get_writer_lock(); (gdb) bt #0 0x0000ffff7eaa9c04 in kp_vip_find_index (prefix=prefix@entry=0xffff7ec3dbe8, plen=104 'h', vip_index=vip_index@entry=0xffff7ec3dbbc) at /home/gannega/vpp/build-data/../src/plugins/kubeproxy/kp.c:457 #1 0x0000ffff7eaaeacc in kp_pod_command_fn (vm=<optimized out>, input=<optimized out>, cmd=<optimized out>) at /home/gannega/vpp/build-data/../src/plugins/kubeproxy/kp_cli.c:132 #2 0x0000ffffbf62cfd0 in vlib_cli_dispatch_sub_commands ( vm=vm@entry=0xffffbf68cfd0 <vlib_global_main>, cm=cm@entry=0xffffbf68d220 <vlib_global_main+592>, input=input@entry=0xffff7ec3ddf8, parent_command_index=<optimized out>) at /home/gannega/vpp/build-data/../src/vlib/cli.c:588 #3 0x0000ffffbf62d618 in vlib_cli_dispatch_sub_commands ( vm=vm@entry=0xffffbf68cfd0 <vlib_global_main>, cm=cm@entry=0xffffbf68d220 <vlib_global_main+592>, input=input@entry=0xffff7ec3ddf8, parent_command_index=parent_command_index@entry=0) at /home/gannega/vpp/build-data/../src/vlib/cli.c:566 #4 0x0000ffffbf62d764 in vlib_cli_input (vm=vm@entry=0xffffbf68cfd0 <vlib_global_main>, input=input@entry=0xffff7ec3ddf8, function=function@entry=0x411b78 <inband_cli_output>, function_arg=function_arg@entry=281472808508960) at /home/gannega/vpp/build-data/../src/vlib/cli.c:662 #5 0x0000000000411e78 in vl_api_cli_inband_t_handler (mp=0x3ffff809c4ec) at /home/gannega/vpp/build-data/../src/vpp/api/api.c:219 #6 0x0000ffffbf6941ec in vl_msg_api_handler_with_vm_node (am=0xffffbf6be430 <api_main>, the_msg=0x3ffff809c4ec, vm=0xffffbf68cfd0 <vlib_global_main>, node=0xffff7ec35000) at /home/gannega/vpp/build-data/../src/vlibapi/api_shared.c:508 #7 0x0000ffffbf69d544 in memclnt_process (vm=<optimized out>, node=0x1390000013a, f=<optimized out>) at /home/gannega/vpp/build-data/../src/vlibmemory/memory_vlib.c:970 #8 0x0000ffffbf635410 in vlib_process_bootstrap (_a=<optimized out>) at /home/gannega/vpp/build-data/../src/vlib/main.c:1231 #9 0x0000ffffbef127a8 in clib_calljmp () at /home/gannega/vpp/build-data/../src/vppinfra/longjmp.S:676 Best regards, -- Gabriel Ganne
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
