Hi All, I've seen that sometimes the tizen build fails during Jenkins verification. (for ex: https://build.iotivity.org/ci/job/Verify-IoTivity-Tizen/1474/console) The build failed log extract is as shown below: --------------------------------------------------------------------------------------------------------------------------------------------------------- 10:12:42 info: Creating (native) source archive com-oic-ca-0.1.tar.gz from '930450585e7835b71fbe552aa26d54fa2761e028' 10:12:42 info: package files have been exported to: 10:12:42 /home/jenkins-ci/GBS-ROOT/local/sources/tizen/com-oic-ca-0.1-1 10:12:42 [32minfo: [0mretrieving repo metadata... 10:13:24 reqesting http://download.tizen.org/releases/2.3/2.3-mobile/tizen-2.3-mobile_20150206.1/repos/target/packages/repodata/repomd.xml failed: 500 read timeout 10:13:24 Couldn't open /home/jenkins-ci/GBS-ROOT/local/cache/9554d913cf4cfeeef258db21f5f6643d/repodata/repomd.xml: 10:13:24 No such file or directory at /usr/lib/build/createrepomddeps line 436 10:13:24 [31merror: [0mrepo cache creation failed... 10:13:24 error: <gbs>some packages failed to be built 10:13:24 Core build failed. Try 'find . -type f -exec dos2unix {} \;' in the 'connectivity/' folder 10:13:24 scons: *** [gbs_build] Error 1 10:13:24 Build step 'Execute shell' marked build as failure ---------------------------------------------------------------------------------------------------------------------------------------------------------
These failures are not due to source code changes, rather they are due to timeout issues while accessing the tizen repos. I feel the best idea is to retrigger such builds (may be for Tizen or specific platforms) automatically. Can anyone please check on this ? Thanks and Best Regards, N Ravi
