Closed wanghongjuan closed 8 years ago
Update: Dev will not fix this right now, will define the APIs and implement them
Actually, I just realized the root cause. It requires the followings:
In this case, devices and resources will be discovered multiple times, resulting in duplicate events.
Thus, if you leave a total of one interface up on the test device, this error will go away.
Still, I believe this should be fixed in the higher-level API implementation, and it can be fixed, but we must be able to compare discovery handles.
I think I'll change the test to de-dupe the incoming events, unless we decide that we wish to address this corner case in the implementation.
Hi, @gabrielschulhof this issue doesn't reproduced on Joule 570x with image#191, but it is still exists on Galileo with image#508 and Joule with image#190. It is confused me, because the iotivity-node version is 1.1.0-4 on image#190/191, so I compare the difference between image#190 and image#191, there is a new commit d216381
added into image#191, could you help to confirm this issue whether is relevant with the commit? If no, why this issue doesn't reproduced on image#191?
Some asserts of the test
API Presence
are failed on recent GT images(from build#157 to build#164), but they are passed on build#154. We checked the iotivity-node source code version is 1.1.0-4-r0 in image from build#157.The test steps:
git clone https://github.com/otcshare/iotivity-node.git
Gruntfiles.js, .jscsrc, grunt-build and tests
cd /usr/lib/node_modules/iotivity-node; npm install; npm install grunt-cli
./node_modules/grunt-cli/bin/grunt test --suites="API Presence"
Test Environment:
Tuchuck with build#157(using the image named like: ostro-xt-image-noswupd-benchmark-qa-intel-corei7-64-2016-07-25_07-09-15-build-157.dsk.xz ). Failure log: