There are a few patches pending against 1.3-rel - I know one is some
maintenance on the demo, which is written to run against 1.3.

CI builds don't pass on these patches, with two specific builds always
failing - the 64-bit/vs2015 build, and the 32-bit/vs2013 build (the
other two Windows builds don't seem to run these tests). The error
message is not the same, though the test is, and we don't see this in
master or 1.4-rel.  Does anyone know what could have rotted? I'm unable
to provide the developers with any useful help.


iotivity-verify-windows-amd64-vs2015

15:21:03 [ RUN      ] AMACLResourceTest.CBORAMACLConversion
15:21:03 resource\csdk\security\unittest\amaclresourcetest.cpp(86):
error: Value of: AmaclToCBORPayload(secAmacl, &psStorage, &size)
15:21:03   Actual: 255
15:21:03 Expected: OC_STACK_OK
15:21:03 Which is: 0
15:21:03 resource\csdk\security\unittest\amaclresourcetest.cpp(91):
error: Value of: NULL != psStorage
15:21:03   Actual: false
15:21:03 Expected: true
15:21:03 [  FAILED  ] AMACLResourceTest.CBORAMACLConversion (1 ms)

iotivity-verify-windows-x86-vs2013

15:23:50 [ RUN      ] AMACLResourceTest.CBORAMACLConversion
15:23:50 23:50.464 ERROR: OIC_SRM_AMACL: Failed Closing Amacl Map. with
cbor error: 'too few items added to encoder'.
15:23:50 resource\csdk\security\unittest\amaclresourcetest.cpp(86):
error: Value of: AmaclToCBORPayload(secAmacl, &psStorage, &size)
15:23:50   Actual: 255
15:23:50 Expected: OC_STACK_OK
15:23:50 Which is: 0
15:23:50 resource\csdk\security\unittest\amaclresourcetest.cpp(91):
error: Value of: NULL != psStorage
15:23:50   Actual: false
15:23:50 Expected: true
15:23:50 [  FAILED  ] AMACLResourceTest.CBORAMACLConversion (1 ms)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9898): 
https://lists.iotivity.org/g/iotivity-dev/message/9898
Mute This Topic: https://lists.iotivity.org/mt/24932503/21656
Group Owner: [email protected]
Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to