Knapsack Pro / rails-app-with-knapsack_pro / RSpec - Queue Mode - CodeFresh.io Public

Back to CI builds

Build details ID b16061f3-93f3-4828-aa20-be59cd31b9df

You find here details about tests recorded for below git commit hash across 2 parallel CI nodes for master branch.

Commit hash Branch Node total Updated at Created at
35a6ed1813e5f99c3b4e03fec7d9325fa44e126c master 2 2020-03-18 23:08:05 UTC 2020-03-18 23:08:05 UTC

Newest Build Subsets parallel CI nodes

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.111 seconds

Loading...
Node Index Created At Time execution
0 Finished First 2020-03-18 23:08:05 UTC 7.366 seconds
1 Finished Last 2020-03-18 23:08:06 UTC 10.01 seconds

Newest Build Distribution can be used for future CI build split

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
ea2d687d-04a6-4eb3-be94-4d31a2b5ae87 2 17.376 seconds 8.688 seconds 4.605 seconds

The slowest test files for the Build Distribution

The slow test files are highlighted in yellow below.

Test files with higher time execution than 8.688 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/foo_spec.rb 10.01 seconds
spec/slow_shared_examples_spec.rb 3.507 seconds
spec/time_helpers_spec.rb 3.009 seconds
spec/features/calculator_spec.rb 0.317 seconds
spec/controllers/pending_controller_spec.rb 0.1 seconds
spec/controllers/shared_articles_controller_spec.rb 0.1 seconds
spec/pending_spec.rb 0.1 seconds
spec/controllers/dashboard/pending_controller_spec.rb 0.1 seconds
spec/controllers/shared.rb 0.035 seconds
spec/features/homepage_spec.rb 0.03 seconds
spec/controllers/articles_controller_spec.rb 0.019 seconds
spec/rake_tasks/dummy_rake_spec.rb 0.015 seconds
spec/retry_spec.rb 0.013 seconds
spec/collection_spec.rb 0.011 seconds
spec/vcr_spec.rb 0.005 seconds
spec/controllers/welcome_controller_spec.rb 0.004 seconds
spec/services/calculator_spec.rb 0.003 seconds
spec/timecop_spec.rb 0.003 seconds
spec/bar_spec.rb 0.002 seconds
spec/services/meme_spec.rb 0.002 seconds
spec/dir with spaces/foobar_spec.rb 0.001 seconds

Start using Knapsack Pro

Sign up and speed up your tests.