Hi all, After pulling in the latest changes from master (this is Iotivity on Ubuntu 14.04, not Iochibity, although I see the same thing in both places) I'm seeing the following test failures. I'm running tests without valgrind.
$ scons --config=force VERBOSE=TRUE SECURED=1 TEST=1 2>&1 | tee build.log ... ... /resource/csdk/security/provisioning/unittest/unittest ... [----------] 1 test from PerformUnownedDeviceDiscovery [ RUN ] PerformUnownedDeviceDiscovery.NullParam resource/csdk/security/provisioning/unittest/otmunittest.cpp:399: Failure Value of: NumOfUnownDevice Actual: 0 Expected: 2 [ FAILED ] PerformUnownedDeviceDiscovery.NullParam (4000 ms) [----------] 1 test from PerformUnownedDeviceDiscovery (4000 ms total) [----------] 1 test from PerformJustWorksOxM [ RUN ] PerformJustWorksOxM.NullParam resource/csdk/security/provisioning/unittest/otmunittest.cpp:408: Failure Value of: result Actual: 26 Expected: OC_STACK_OK Which is: 0 What's happening with the first fail is that the test suite launches a couple of sampleserver apps in the preceding step and then it runs PMDeviceDiscovery. If I run the tests with LOGGING=TRUE it's clear that the devices (or at least one of them) are responding. The problem seems to be that DeviceDiscoveryHandler (in pmutility.c) then calls GetDoxmDevOwnerId(&myId), which fails, which causes the Doxm data from the payload to be deleted. At least I think that's the problem: 11:47.552 INFO: OIC_RI_PAYLOADPARSE: Finished parse payload, result is 0 11:47.552 DEBUG: PM-UTILITY: Successfully converted doxm cbor to bin. 11:47.552 DEBUG: SRM-DOXM: GetDoxmDevOwnerId(): gDoxm owned = 0. 11:47.552 ERROR: PM-UTILITY: Error while getting my device ID. ... resource/csdk/security/provisioning/unittest/otmunittest.cpp:399: Failure GetDoxmDevOwnerId references gDoxm, which is a global var in doxmresource.c. Any idea what's going on? Is something not getting initialized properly here? Thanks, Gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160801/a0d956e3/attachment.html>
