Tests are now executing in constrained parallel: https://gerrit.iotivity.org/gerrit/gitweb?p=ci-management.git;a=blobdiff;f=jjb/iotivity/iotivity-jobs.yaml;h=423c0f35655fabe2e2cb18283dae4751d7e916d2;hp=310105bcc44c6ee0e65776a5869e78604d60bcae;hb=c4e459bcccd011eba47659c22095d81e18781777;hpb=5f305ead96d032344ffce9db4eab8cea9f30ac71
On Mon Feb 27 03:05:47 2017, uzchoi at samsung.com wrote: > Hi Phil, LF help or anyone else, > > Currently there are frequent unit test build job failure from Jenkins > verification. > During Unit Test execution, parallel unit test executing cause racing issue. > For example, A test case expect A resource server but at the same time B > test case find A resource first and A resource server close its session. > Then A test case cannot find A resource. > https://build.iotivity.org/ci/job/iotivity-verify-unit_tests/10126/ > Test case should have considered this cases but every test case does not > consider it well. > > As a solution, can we selectively disable this parallel execution for > specific job(unit test job) or check what is the other issue over there? > Is it Jenkins system operation responsibility or build script manager > responsibility or others. > > BR, Uze Choi
