Hi Jay, I have created a commit that is awaiting review on Gerrit to clear up these faux errors(https://gerrit.iotivity.org/gerrit/#/c/745/). What is happening is that several unit tests were added which perform actions over the network. In this case, a random networking error occurred in the unit test and caused this faux error for you. You can go to build.iotivity.org<http://build.iotivity.org>, login with your Linux foundation username and password, then select to retrigger your build after logging in. This error is intermittent and depends on the Linux foundation's network to work. My changeset disables these unit tests. There is a general rule of thumb to implement tests which are testing a single unit of code to be best implemented as a system test. System tests will not be performed on the build machine. System tests will need to be run locally or on some development station.
Thanks, Joey On Apr 16, 2015, at 1:59 AM, ??? <junghyun.oh at samsung.com<mailto:junghyun.oh at samsung.com>> wrote: Hi Erich, I'm not sure whether you're the right person to ask about this issue, however, I adding my comments on this Uze's mail. Recently, PPM developer "Yonghyun Joo" commited the code work, (link -> https://gerrit.iotivity.org/gerrit/#/c/733/) however, Jenkins reporeted build test has failed. When I looked at the build result captured from the console, the build error was reported from the "OCHeaderOptionTest" ================================================= .... [ RUN ] OCHeaderOptionTest.ConstructorTooHighOptionIdTest resource/unittests/OCResourceTest.cpp:38: Failure Value of: OC_STACK_OK Actual: 0 Expected: eCode Which is: 29 0: listenCallback(): failed to create resource. clientResponse: 29 resource/unittests/OCResourceTest.cpp:38: Failure Value of: OC_STACK_OK Actual: 0 Expected: eCode Which is: 29 resource/unittests/OCResourceTest.cpp:38: Failure Value of: OC_STACK_OK Actual: 0 Expected: eCode Which is: 29 [ FAILED ] OCHeaderOptionTest.ConstructorTooHighOptionIdTest (73021 ms) [ RUN ] OCHeaderOptionTest.OptionIDTest .... ================================================= Link -> https://build.iotivity.org/ci/job/Verify-IoTivity-Scons/1809/console I do not understand the why this Unit-test fail lead to the PPM build fail. Could you or anyone one this mail thread bring us the light with what is the problem & solution? Thank you. Jay. ------- Original Message ------- Sender : ???<uzchoi at samsung.com<mailto:uzchoi at samsung.com>> S6(??)/??/IoT Solution Lab(S/W??)/???? Date : 2015-04-16 12:20 (GMT+09:00) Title : [dev] Jenkins build error Question during commit. Hi Erich/Bill, We are pushing the code into the gerrit but it generate the Jenkins error as follows. https://gerrit.iotivity.org/gerrit/#/c/733/ Commit ID : 978317257292bf2491d484138b02d90828c21833 Build Error Detail: https://build.iotivity.org/ci/job/Verify-IoTivity-Scons/1809/ However, error report seems not be related with our commit. That is resource/unittests/OCResourceTest.cpp:38 - OCHeaderOptionTest.ConstructorTooHighOptionIdTest. Anyway scons build is successful. BR, Uze Choi Jung-hyun Oh. IoT Solution Lab. | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD Mobile +82-10-9890-6731 | Beyond your imagination, Always <201504161459541_XOK0LK7C.gif> _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: 201504161459541_XOK0LK7C.gif Type: image/gif Size: 13168 bytes Desc: 201504161459541_XOK0LK7C.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150416/ae6b9c97/attachment.gif>
