Hi Uze, I've been looking into this off-and-on the last couple of weeks, and am migrating this to JIRA as I'm pretty certain it's an issue with SCons and not the build servers[1].
Regards, Trevor Bramwell [1] https://jira.iotivity.org/browse/IOT-1526 On Thu Oct 13 21:51:05 2016, bramwelt wrote: > Hi Uze, > > This is very odd. I dug into this a bit, and I'm quite confused. There > does not seem to be a pattern between these failures and which build > servers the tests ran on. > > Here are the dates of failures for master and 1.2-rel merge unit-test > jobs, and the servers they ran on: > > master: > 15 days ago - build-08 [1] > 3 days ago - build-16 [2] > 1 day ago - build-04 [3] > > 1.2-rel: > 8 days ago - build-07 [4] > 6 days ago - build-09 [5] > 3 days ago - build-18 [6] > 3 days ago - build-11 [7] > > I have two ideas as to what might be causing this: > 1) A race condition in the test runner > 2) Execution permission on some files > > Since there does not seem to be a way to consistently reproduce the > error, I'm going to hold off on looking into this more till next week. > > I understand this is an annoyance, and I'm sorry I can't be more help > right now. In the mean time I would suggest just retriggering the > failed > unit_test build from the build description page. > > Regards, > Trevor Bramwell > > [1] https://build.iotivity.org/ci/view/iotivity-merge/job/iotivity- > merge-master-unit_tests/84/ > [2] https://build.iotivity.org/ci/view/iotivity-merge/job/iotivity- > merge-master-unit_tests/170 > [3] https://build.iotivity.org/ci/view/iotivity-merge/job/iotivity- > merge-master-unit_tests/200/ > [4] https://build.iotivity.org/ci/view/iotivity-1.2-rel/job/iotivity- > merge-1.2-rel-unit_tests/14/ > [5] https://build.iotivity.org/ci/view/iotivity-1.2-rel/job/iotivity- > merge-1.2-rel-unit_tests/29/ > [6] https://build.iotivity.org/ci/view/iotivity-1.2-rel/job/iotivity- > merge-1.2-rel-unit_tests/41/ > [7] https://build.iotivity.org/ci/view/iotivity-1.2-rel/job/iotivity- > merge-1.2-rel-unit_tests/43/
