My organization (email@example.com) / 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/heads/master branch.
|Commit hash||Branch||Node total||Updated at||Created at|
|d54c180b0421cf8379e9d4c40654a416f9f397ac||refs/heads/master||2||2020-04-03 04:04:39 UTC||2020-04-03 04:04:39 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 first CI node finished its work at 2020-04-03 04:04:39 UTC. CI nodes that finished at least 60s later are highlighted.
The reason for slow CI nodes might be too large test files (you can see the slowest test files at the bottom of the page when all CI nodes collected time execution data). You may want to try Knapsack Pro Queue Mode (Ruby) to solve a problem with the random performance of test files or your CI nodes. Learn more about dynamic test suite split here.
Note: if you run CI build for the same commit again (for instance when you retry CI build), then you will see build subsets updated below. Until retried CI build finishes work you may see highlighted build subsets.
Average time execution per collected CI node is 8.96 seconds.
The time gap between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 4.198 seconds
|Node Index||Created At||Time execution|
|0 Finished Last||2020-04-03 04:05:44 UTC||12.206 seconds|
|1 Finished First||2020-04-03 04:04:39 UTC||5.714 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|
|c5df3df7-2293-4309-b71f-a1a8e87a597b||2||17.92 seconds||8.96 seconds||4.577 seconds|
The slow test files are highlighted in yellow below.
Test files with higher time execution than 8.96 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 (12 files)||Time execution|