-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
v4.2, v4.0
-
DAG 2019-11-04
-
28
-
2
In BF-11716, the second task in the stitch_support_lib_build_and_test task group (stitch_support_run_tests) is failing because it gets run on a different build variant (and at the same time as, rather than after) it's dependency task (stitch_support_install_tests). We should set max_hosts to 1 on the stitch_support_lib_build_and_test task group so these tasks get run in consecutive order on the same host.
Similarly, in BF-14342, embedded_sdk_install_dev is getting run before it's dependency task (embedded_sdk_build_cdriver). These tasks are run as part of the embedded_sdk_build_and_test task group.
User story:
As a server engineer,
When I run the stitch_support_lib_build_and_test and embedded_sdk_build_and_test task groups, I should know that each task group's tasks will get run in consecutive order on the same host, so that I do not have failures in my build.
AC:
- Tasks within the stitch_support_lib_build_and_test task and the embedded_sdk_build_and_test task groups should run in consecutive order