I think the large sequence of *contiguous* ERRORs below makes these log entries look scarier than they probably are. If these ERRORs are actually spread across multiple tests, many of them don't look surprising to me.
Probably windows x86 is the only Jenkins build job that runs with LOGGING=1, which explains why the output looks so different than the other build jobs. I agree that the IoTivity logs should be reviewed and improved. For example, please log a JIRA ticket for these suspect log entries, or let me know if you prefer me to log that ticket: 12:53:16 53:13.122 WARNING: OIC_PLATFORM: Unsupported platform. 12:53:16 53:13.122 ERROR: OIC_PLATFORM: Failed to GetSysLocalAppDataPath, ret: 3 Thanks, Dan -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Wednesday, May 24, 2017 3:00 PM To: IoTivity Developer List <iotivity-dev at lists.iotivity.org> Subject: [dev] odd msgs in windows x86 build logs from jira, a failed build: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild.iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-x86-vs2013%2F1978%2Fconsole&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C1c5c4a9c000b45b0981208d4a2f039cc%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636312600048564193&sdata=3X%2Bjp%2BBiA60SG4U0jcOnQtsqHCwhra0tJIlEFaGhRHk%3D&reserved=0: 12:53:16 53:13.122 WARNING: OIC_PLATFORM: Unsupported platform. 12:53:16 53:13.122 ERROR: OIC_PLATFORM: Failed to GetSysLocalAppDataPath, ret: 3 is this something expected? A succeeded build here also has a lot of unexpected stuff in it: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild.iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-x86-vs2015%2F1973%2Fconsole&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C1c5c4a9c000b45b0981208d4a2f039cc%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636312600048564193&sdata=uDsiefIdonlBHVZjnRbT9eGQDUL4bvG8WQMgwE8Nhwg%3D&reserved=0 there are 4228 lines in the full log that contain the tag ERROR:, the unique list of those messages follows. Since I don't see any of those in an x64 windows build, it seems kind of surprising all those would happen and the build would still be marked a succeed... are these some kind of debug output that are triggering on ERROR: OI45:10.705 DEBUG: OIC_CA_CONN_MGR: CAInitialize type : 1 ERROR: OIC_45:10.692 DEBUG: OIC_CA_CONN_MGR: CAInitialize type : 1 ERROR: OIC_CA_ADAP_UTILS: Failed at parse ipv6 address using inet_pton ERROR: OIC_CA_BWT: no logic [0] ERROR: OIC_CA_IP_SERVER: WSAEventSelect failed 10038 ERROR: OIC_CA_MSG_HANDLE: Failed to generate unicast PDU ERROR: OIC_CA_MSG_HANDLE: Invalid input: sendMsg ERROR: OIC_CA_MSG_HANDLE: send failed:7 ERROR: OIC_CA_PRTCL_MSG: Invalid input: token ERROR: OIC_CA_PRTCL_MSG: reset is not empty message ERROR: OIC_CA_QING: thread instance is empty.. ERROR: OIC_CA_TCP_SERVER: WSAEventSelect failed 10093 ERROR: OIC_PLATFORM: Failed to GetSysLocalAppDataPath, ret: 3 ERROR: OIC_RI_PAYLOADPARSE: Array details weren't clear with cbor error: 'unknown error'. ERROR: OIC_RI_PAYLOADPARSE: Array parse failed, mixed arrays not allowed ERROR: OIC_RI_RESOURCE: No value specified. ERROR: OIC_RI_RESOURCE: Null or empty device name. ERROR: OIC_RI_RESOURCE: Platform ID is not a UUID. ERROR: OIC_RI_RESOURCE: Platform Resource does not exist. ERROR: OIC_RI_RESOURCE: R[==========] 5 tests from 2 test cases ran. (2 ms total) ERROR: OIC_RI_RESOURCE: ReadDatabaseFromPS failed ERROR: OIC_RI_RESOURCE: ReadDevicePropertiesFromDatabase failed ERROR: OIC_RI_RESOURCE: The passed value cannot be empty ERROR: OIC_RI_RESOURCE: The passed value is bigger than permitted. ERROR: OIC_RI_STACK: Added handle equals collection handle ERROR: OIC_RI_STACK: collectionHandle is NULL ERROR: OIC_RI_STACK: handle is NULL ERROR: OIC_RI_STACK: Input parameter is NULL ERROR: OIC_RI_STACK: Invalid callback ERROR: OIC_RI_STACK: Invalid handle for deletion ERROR: OIC_RI_STACK: Invalid mode ERROR: OIC_RI_STACK: Invalid parameters ERROR: OIC_RI_STACK: Invalid property ERROR: OIC_RI_STACK: Invalid TPS Types OC_ALL ERROR: OIC_RI_STACK: OCEncodeAddressForRFC6874 failed: encoded output will not fit! ERROR: OIC_RI_STACK: OCEncodeAddressForRFC6874 failed: Input string is already encoded ERROR: OIC_RI_STACK: OCProcess has failed. ocstack is not initialized ERROR: OIC_RI_STACK: Resource /a/led already exists ERROR: OIC_RI_STACK: resourceInterfaceName is NULL ERROR: OIC_RI_STACK: Resource not found ERROR: OIC_RI_STACK: resource type illegal (see RFC 6690) ERROR: OIC_RI_STACK: resourceTypeName is NULL ERROR: OIC_RI_STACK: URI is empty or too long ERROR: OIC_SRM_PSI: (OC_STACK_OK == ret) failed!! ERROR: OIC_SRM_PSI: ps is NULL ERROR: OIC_ULINKLIST: Invalid input: linklist is null ERROR: OIC_UMUTEX: oc_mutex_lock Invalid mutex ! ERROR: OIC_UMUTEX: oc_mutex_unlock: Invalid mutex ! _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C1c5c4a9c000b45b0981208d4a2f039cc%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636312600048564193&sdata=XnJdzbykbql8amczq62dEEptRJw0jK%2BsLYK6QDIM0iI%3D&reserved=0
