Dear Maintainers.
Currently all unit tests cannot be executed due to time limit. It will be better to increase the unit test limit time to secure the quality. For this one, I suggest to separate the unit test job into resource one and service one according to the current directory structure, and to Add the new Jenkins task for service unit test. BR, Uze Choi From: Othman, Ossama [mailto:[email protected]] Sent: Tuesday, September 29, 2015 12:38 AM To: minjii.park at samsung.com Cc: iotivity-dev at lists.iotivity.org; ???; Patrick Lankswert Subject: Re: [dev] Jenkins for iotivity unit tests build timeout Hi Minji, On Mon, Sep 28, 2015 at 2:28 AM, minji park <minjii.park at samsung.com> wrote: I tried to make IoTivity Jenkins verify unit tests for both resource and service, but Jenkins build for unit tests is aborted due to the timeout (after 7 or 8 mins). To execute all unit tests, it takes more than 8 minutes. To verify both resource and service unit tests at Jenkins build time, It seems that discussion regarding time limit for unit tests is needed. Part of the long test run times for the Linux builds is due to timed condition variable waits in the Linux BLE Transport that block waiting for a Bluetooth adapter to be found/enabled. The timed waits are being triggered in the Jenkins build since no usable Bluetooth adapter is available. I have a patch pending that should alleviate the test timeout problem. Thanks, -Ossama -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150930/8939d6dd/attachment.html>
