13:28:17 #startmeeting jquery_xpath_for_md_sal_intern 13:28:17 Meeting started Wed Aug 20 13:28:17 2014 UTC. The chair is devinavery. Information about MeetBot at http://ci.openstack.org/meetbot.html. 13:28:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:28:17 The meeting name has been set to 'jquery_xpath_for_md_sal_intern' 13:28:25 #topic update 13:28:53 #info Neel has updated the code to deal with generating the XML. The test does appear to be generating the correct XML on first glance, but tests are failing 13:29:08 I'm not 100% sure I agree with that 13:29:47 regXboi: the paste bin http://pastebin.com/TpEVZ6RH is from the test output. The restconf output is int he src/test/resources folder under "listtoaster.xml" 13:30:19 what I am concerned about is why childtoasterlist shows up twice 13:30:29 it has to show up 13:30:38 yes - it has to show up once 13:30:41 but twice? 13:30:45 yeah twice 13:30:56 why twice 13:31:02 The childtoasterlist is a list of leaf lists 13:31:09 i made container list whose children is leaflist 13:31:27 * regXboi goes back to yang 13:32:01 I just modified the OpendaylightToaster to change the values to make it clearer 13:32:38 so honestly folks 13:32:58 I would expect a list of leaf-lists to look a little different in the xml 13:33:44 {....}+ 13:34:25 This mirrors what restconf is giving us 13:34:38 but the netconf shows the same one right ? 13:34:39 I will paste the two XML's side by side in a paste bin with my modified values so it is easier to follow 13:35:11 * regXboi doesn't like it, but ok 13:35:45 Check out this paste bin: http://pastebin.com/5A4E1WZZ 13:36:12 Neel_B: not sure if you have something auto correcting, but it is RESTCONF, not NETCONF that is giving us the XML format. :) 13:36:40 when we say the tests are failing - are they throwing excpetions or just not succeeding? 13:36:49 *exceptions 13:37:26 I personally am seeing it fail on the "toasterStatus" xpath - we are expecintg 'up' but it is returning blank 13:37:53 Is that what you are seeing too Neel? 13:39:09 sorry got disconnected 13:39:39 Here is a link to the error I am seeing right now: http://pastebin.com/ZPKBC1yp 13:40:27 yeah the same error 13:41:03 the obvious conclusion is that we are munging the multiple identical childtoasterlist container blocks 13:41:12 identical == same label 13:41:35 I don't know if I believe the obvious conclusion though 13:41:47 so... can we run a test where we have a single childtoasterlist? 13:41:56 that would help us isolate it 13:43:13 how ever the code should pass in this scenario too 13:43:57 yes, but when you have a problem like this, you do fault isolation 13:44:13 so the first question then becomes "does the code work with a single childtoasterlist" 13:44:28 if it does, then we look at how we are handling the second childtoasterlist 13:44:37 if not ... 13:47:05 then we have to look at the base childtoasterlist handling 13:48:34 lost him again... 13:48:48 did i miss anything 13:48:57 maybe yes, maybe no 13:49:01 so I'll back 13:49:07 er I'll go back 13:49:26 the reason I was asking about running a test with a single childtoasterlist is fault isolation 13:49:47 i.e. do we have a problem with a list of leaf lists in general 13:49:57 or do we have a problem with multiple instances in the list of leaf lists 13:50:11 okay 13:50:40 you want to leave one childtaosterlist behind and try the test 13:51:18 yes... what happens if the model is such that the list of leaf lists has a single element 13:51:22 er a single leaf list 13:51:25 that is 13:58:27 brb - bio/caffeine break 14:00:14 regXboi: devinavery same error 14:00:20 the output xml is 14:00:52 http://pastebin.com/FKPuExZ2 14:01:20 Neel - probably worth taking another step back. I would go back to the original XML with just the three attributes and see what you get 14:01:46 Then add back in the child toaster try again, then add back in child lists. This will allow us to isolate when the problem starts as regXboi pointed out 14:04:05 #info regXboi providing tips on how to isolate the problem. Basically start backing out the objects we added in until we get to a point that things start to pass again 14:06:27 yes - that's the way to do this 14:06:40 okay 14:06:52 it's painful, and it's time consuming 14:07:22 but any time I've tried to skip steps, I find that ended up costing me more time 14:07:33 let's end this meeting i have some other work too 14:07:43 i will meetup in the night 14:07:48 late night 14:08:07 can anyone have your afternoon free ? 14:08:18 my schedule has me open right now 14:08:21 but that may change 14:08:29 if not we will have contact through mail 14:08:30 so I'll stay here 14:08:40 here == in this channel 14:08:42 i can continue 2,3 hrs later 14:08:48 yeah i got it 14:08:54 #endmeeting 14:09:07 sorry but i have classes started so 14:09:08 devinavery: I'm not chair, so I can't end this... 14:09:35 Ok. So we are ending the meeting? 14:09:52 #info Neel needs to step away. We will meet up this afternoon and continue debugging 14:09:52 yes, Neel_B has class work to do, so we'll meet up again in 2-3 hours or so 14:09:57 #endmeeting