Knapsack Pro / rails-app-with-knapsack_pro / RSpec - Queue Mode - CodeFresh.io PublicBack to CI builds
You find here details about tests recorded for below git commit hash across 2 parallel CI nodes for rspec-split-by-examples-selected-test-files branch.
|Commit hash||Branch||Node total||Updated at||Created at|
|8ea62242c12400859ab3dbb44a862a5f74b02715||rspec-split-by-examples-selected-test-files||2||2020-05-02 15:23:16 UTC||2020-05-02 15:23:16 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 0.523 seconds
|Node Index||Created At||Time execution|
|0 Finished Last||2020-05-02 15:23:16 UTC||10.121 seconds|
|1 Finished First||2020-05-02 15:23:16 UTC||8.377 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|
|d7539b65-6b55-4b0c-b523-7d9900ccea32||2||18.497 seconds||9.249 seconds||4.373 seconds|
The slow test files are highlighted in yellow below.
Test files with higher time execution than 9.249 seconds are bottleneck because they take more time than expected execution time per parallel CI node.
You can enable auto split of slow RSpec test files by test examples on parallel CI nodes to run faster CI builds.
The more parallel CI nodes you use, the more test files will be split by test examples.
We recommend running at least 2 CI builds after you increase the number of parallel CI nodes. This way Knapsack Pro API can learn about your test examples defined in the slow test files to split tests better in future CI builds.
|Test file path (21 files)||Time execution|
|spec/dir with spaces/foobar_spec.rb||0.002 seconds|