With a test investigation of how long each of our current build machines can take to run the sandbox test.py job, we can see that the longest running hosts are any of the arm64 machines. In some cases this may be a matter of overall system load, but in others it's hard to say. The challenge with these tests is that the run itself is single threaded and covers a large number of tests. There may be gains made in looking in to optimizing some individual tests. For now however we will likely gain the most by removing potential bottle necks here and allow any amd64 or arm64 host to run the test instead of trying to ensure they only run on one of the few "fast" machines.
Link: https://source.denx.de/u-boot/u-boot/-/pipelines/26533/test_report Signed-off-by: Tom Rini <tr...@konsulko.com> --- .gitlab-ci.yml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 18afc03b4600..2dfeda9985d7 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -264,8 +264,8 @@ Check packing of Python tools: sandbox test.py: parallel: matrix: - - HOST: "fast arm64" - - HOST: "fast amd64" + - HOST: "arm64" + - HOST: "amd64" tags: - ${HOST} variables: @@ -276,8 +276,8 @@ sandbox test.py: sandbox with clang test.py: parallel: matrix: - - HOST: "fast arm64" - - HOST: "fast amd64" + - HOST: "arm64" + - HOST: "amd64" tags: - ${HOST} variables: @@ -288,8 +288,8 @@ sandbox with clang test.py: sandbox64 test.py: parallel: matrix: - - HOST: "fast arm64" - - HOST: "fast amd64" + - HOST: "arm64" + - HOST: "amd64" tags: - ${HOST} variables: @@ -299,8 +299,8 @@ sandbox64 test.py: sandbox64 with clang test.py: parallel: matrix: - - HOST: "fast arm64" - - HOST: "fast amd64" + - HOST: "arm64" + - HOST: "amd64" tags: - ${HOST} variables: @@ -311,8 +311,8 @@ sandbox64 with clang test.py: sandbox64_lwip test.py: parallel: matrix: - - HOST: "fast arm64" - - HOST: "fast amd64" + - HOST: "arm64" + - HOST: "amd64" tags: - ${HOST} variables: -- 2.43.0
