summaryrefslogtreecommitdiffstats
path: root/docs/submodules/escalator
diff options
context:
space:
mode:
authorJose Lausuch <jalausuch@suse.com>2017-09-20 12:47:54 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-09-20 12:47:54 +0000
commitb8c533f6ecb88579abbefc84d7f593c40ffa9c33 (patch)
tree8837b75fe11336ebf5747abda0487d5bc98e3394 /docs/submodules/escalator
parent812d0146ed781fb6dcdf7fd0d856bbfcf800f307 (diff)
Update git submodules
* Update docs/submodules/releng from branch 'master' - Merge "Add functest return status in Alpines" - Add functest return status in Alpines So far we had 2 approaches: * return Functest CI status: can be OK even if tests are FAIL * return Functest Test status: can be FAIL even if all Functest tests are OK (Fail in onboaraded tests) A 3rd way is possible thanks to [1]. We consider only Functest status and Functest tests for the return statement the return will be FAIL only if * error in the framework * error in Functest Tests So concretely, if promise, Doctor can be FAIL, if Functest tests are OK, the return will be PASS [1]: https://gerrit.opnfv.org/gerrit/#/c/42245/ Change-Id: I6c7fbe99d888e43700ddb2dfc9bfd6cc9bfbaed6 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
Diffstat (limited to 'docs/submodules/escalator')
0 files changed, 0 insertions, 0 deletions