Hi Trevor,
https://build.iotivity.org/ci/job/Verify-IoTivity-Tizen/2842/ https://build.iotivity.org/ci/job/Verify-IoTivity-Tizen/2845/ It seems Tizen builds are failing on the build server for some reason. The only error I could see in the logs are: 16:24:24 Calling core gbs build command 16:24:24 gbs build -A armv7l -B ~/GBS-ROOT --include-all --repository ./ 16:24:24 info: generate repositories ... 16:24:25 info: build conf has been downloaded at: 16:24:25 /var/tmp/jenkins-ci-gbs/tizen.conf 16:24:25 [32minfo: [0mstart building packages from: /home/jenkins-ci/workspace/Verify-IoTivity-Tizen/tmp (git) 16:24:25 2015-10-08 16:24 +0000 16:24:25 gbs 0.23.2 16:24:25 [32minfo: [0mprepare sources... 16:24:25 Argument "" isn't numeric in numeric eq (==) at /usr/bin/depanneur line 642. 16:24:25 [32minfo: [0mstart export source from: /home/jenkins-ci/workspace/Verify-IoTivity-Tizen/tmp ... 16:24:29 warning: Deprecated option '--git-export-only', please use '--no-build' instead! 16:24:29 info: Creating (native) source archive iotivity-0.9.2.tar.bz2 from '0043b6ce1d6cefa209d79f2ce48f787da1280f19' 16:24:29 info: package files have been exported to: 16:24:29 /home/jenkins-ci/GBS-ROOT/local/sources/tizen/iotivity-0.9.2-0 16:24:29 [32minfo: [0mretrieving repo metadata... 16:24:30 [32minfo: [0mparsing package data... 16:24:30 [32minfo: [0mbuilding repo metadata ... 16:24:30 [32minfo: [0mresolving skipped packages ... 16:24:30 [32minfo: [0mpackage dependency resolving ... 16:24:30 [31merror: [0mthere're mounted directories to build root. Please unmount them manually to avoid being deleted unexpectly: 16:24:30 / ==> /home/jenkins-ci/GBS-ROOT/local/BUILD-ROOTS/scratch.armv7l.0/proc 16:24:30 / ==> /home/jenkins-ci/GBS-ROOT/local/BUILD-ROOTS/scratch.armv7l.0/dev/pts 16:24:30 / ==> /home/jenkins-ci/GBS-ROOT/local/BUILD-ROOTS/scratch.armv7l.0/dev/shm 16:24:30 error: <gbs>some packages failed to be built 16:24:30 Build failed! 16:24:30 Build step 'Execute shell' marked build as failure 16:24:30 Archiving artifacts I could not see any recent changes which could have triggered these failures. Were there any updates in the build server? Thanks Sachin 503-264-8071 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151008/f21dfafd/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7768 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151008/f21dfafd/attachment.p7s>
