I think this should about cover the situation... (š)... HTH... Dave void vl_msg_api_config (vl_msg_api_msg_config_t * c) { api_main_t *am = &api_main;
/* * This happens during the java core tests if the message * dictionary is missing newly added xxx_reply_t messages. * Should never happen, but since I shot myself in the foot once * this way, I thought I'd make it easy to debug if I ever do * it again... (;-)... */ if (c->id == 0) { if (c->name) clib_warning ("Trying to register %s with a NULL msg id!", c->name); else clib_warning ("Trying to register a NULL msg with a NULL msg id!"); clib_warning ("Did you forget to call setup_message_id_table?"); return; } Thanksā¦ Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach) Sent: Friday, October 13, 2017 1:32 PM To: Ole Troan (otroan) <otr...@cisco.com>; Ole Troan <otr...@employees.org> Cc: vpp-dev@lists.fd.io Subject: [vpp-dev] jvpp core future test failure (gerrit 8743) Dear Ole, See https://gerrit.fd.io/r/#/c/8743. It turns out that the java core future āmake testā test fails as shown below. The patch adds three xxx_reply_t binary api messages. See .../src/vnet/dns/dns.api. It sure looks like the Java code knows about them, but isnāt doing a very good job of registering them. Note that I had to modify the binary API client library to keep Java from ASSERTing due to the NULL msg idās squawked below. Whatās going on here? These messages work like a champ in vpp_api_test... INFO: Testing Java future API for core plugin [New Thread 0x7fffd5f9c700 (LWP 4611)] vl_msg_api_config:671: Trying to register dns_enable_disable_reply with a NULL msg id! vl_msg_api_config:671: Trying to register dns_name_server_add_del_reply with a NULL msg id! vl_msg_api_config:671: Trying to register dns_resolve_name_reply with a NULL msg id! [Thread 0x7fffd5f9c700 (LWP 4611) exited] Exception in thread "main" java.lang.IllegalStateException: API mismatch detected: dns_resolve_name_reply_451ab6c0 is missing at io.fd.vpp.jvpp.core.JVppCoreImpl.init0(Native Method) at io.fd.vpp.jvpp.core.JVppCoreImpl.init(JVppCoreImpl.java:75) at io.fd.vpp.jvpp.JVppRegistryImpl.register(JVppRegistryImpl.java:72) at io.fd.vpp.jvpp.core.future.FutureJVppCoreFacade.<init>(FutureJVppCoreFacade.java:25) at io.fd.vpp.jvpp.core.test.FutureApiTest.testFutureApi(FutureApiTest.java:50) at io.fd.vpp.jvpp.core.test.FutureApiTest.main(FutureApiTest.java:44) [New Thread 0x7fffd54af700 (LWP 4612)] Thanksā¦ Dave
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev