My organization (firstname.lastname@example.org) / office_stuff / Minitest PublicBack to CI builds
You find here details about tests recorded for below git commit hash across 2 parallel CI nodes for refs/pull/15/merge branch.
|Commit hash||Branch||Node total||Updated at||Created at|
|c6e17e0e8ace7db1942aa57b04ee1fff16f699f7||refs/pull/15/merge||2||2020-04-02 17:24:13 UTC||2020-04-02 17:24:12 UTC|
Here you can check if all parallel CI nodes recorded tests timing data.
When you re-run CI build or run a new CI build for the same commit & branch & node total number, then the data below will be updated.
Collected Build Subsets 2 out of 2.
All CI nodes sent time execution data to Knapsack Pro API. Everything works!
The time gap between the finish times of the CI node that Finished First and the one which Finished Last is 9.476 seconds
|Node Index||Created At||Time execution|
|0 Finished First||2020-04-02 17:24:12 UTC||5.403 seconds|
|1 Finished Last||2020-04-02 17:24:22 UTC||8.049 seconds|
Build Distribution ID is the ID for the test suite split. You can see this ID in knapsack_pro logs as a test suite split seed.
Total time execution is sum of tests' execution times recorded across all parallel CI nodes.
Node max time execution is an estimated average time of running tests per CI node.
Distance is a time gap between average CI node time execution and the slowest CI node. The lower the better.
|Build Distribution ID||Node total||Total time execution||Node max time execution||Distance|
|8e4888ec-0ba7-4903-8d42-a057ee02e645||2||13.452 seconds||6.726 seconds||2.486 seconds|
The slow test files are highlighted in yellow below.
Test files with higher time execution than 6.726 seconds are bottleneck because they take more time than expected execution time per parallel CI node.
Please check how to improve test suite split for the slowest test files.
|Test file path (10 files)||Time execution|