Knapsack Pro
DEV Community (dev.to) / dev.to / Forem / Build ID 232dd253-f799-44e6-a352-c57e594b26b8
| Commit hash | Branch | Nodes | Tests execution time | Created at |
|---|---|---|---|---|
| dd0facb | refs/pull/20834/merge | 8 | 24 minutes 48.6 seconds 5% | 2024-04-03 15:35:05 UTC |
All parallel CI nodes finished their work.
The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 17.14 seconds. The shorter this time is, the better.
The first CI node finished its work at 2024-04-03 16:56:31 UTC. CI nodes that finished at least 60s later are highlighted.
The reason for slow CI nodes might be too large test files (see the Test Files tab). You may want to try the Knapsack Pro Queue Mode (Ruby) to improve the distribution of your tests. Learn more about dynamic test suite split here.
Note: if you run a CI build for the same commit again (for instance when you retry a CI build), then you will see the data updated below. Some of the nodes might be highlighted until the whole CI build is complete.
The average test execution time per CI node is 3 minutes 6.08 seconds.
The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 17.14 seconds. The shorter this time is, the better.
| Node index | Finish time | Tests execution time (24 minutes 48.6 seconds) |
|---|---|---|
| 0 | 2024-04-03 16:57:27 UTC | 3 minutes 23.96 seconds |
| 1 | 2024-04-03 16:56:51 UTC | 3 minutes 4.41 seconds |
| 2 | 2024-04-03 16:57:31 UTC | 3 minutes 31.68 seconds |
| 3 | 2024-04-03 16:56:46 UTC | 2 minutes 54.11 seconds |
| 4 Finished First | 2024-04-03 16:56:31 UTC | 2 minutes 47.57 seconds |
| 5 | 2024-04-03 16:56:33 UTC | 2 minutes 31.7 seconds |
| 6 Finished Last | 2024-04-03 16:57:48 UTC | 3 minutes 45.57 seconds |
| 7 | 2024-04-03 16:56:40 UTC | 2 minutes 49.64 seconds |
The slow test files are highlighted in yellow.
Test files with higher execution time than 3 minutes 6.08 seconds are a bottleneck because they take more time than the 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 your CI builds faster.
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 (Displaying entries 901 - 916 of 916 in total files) | Execution time | ||
|---|---|---|---|
| spec/lib/liquid/render_spec.rb | 4 miliseconds | 76% | Trend |
| spec/lib/liquid/variable_spec.rb | 4 miliseconds | 19% | Trend |
| spec/services/edge_cache/bust_podcast_spec.rb | 4 miliseconds | 76% | Trend |
| spec/lib/sidekiq/worker_retries_exhausted_reporter_spec.rb | 4 miliseconds | 77% | Trend |
| spec/initializers/carrierwave_monkeypatch_spec.rb | 4 miliseconds | 71% | Trend |
| spec/lib/data_update_scripts/add_multiple_reactions_feature_flag_spec.rb | 4 miliseconds | 78% | Trend |
| spec/lib/rails_env_constraint_spec.rb | 3 miliseconds | 89% | Trend |
| spec/services/badges/award_sixteen_week_streak_spec.rb | 3 miliseconds | 93% | Trend |
| spec/models/hair_trigger_spec.rb | 3 miliseconds | 40% | Trend |
| spec/services/images/profile_image_generator_spec.rb | 3 miliseconds | 25% | Trend |
| spec/services/audit/helper_spec.rb | 3 miliseconds | 25% | Trend |
| spec/requests/api/v1/docs/follows_spec.rb | 0 seconds | Trend | |
| spec/system/dashboards/user_followers_display_spec.rb | 0 seconds | Trend | |
| spec/system/comments/user_fills_out_comment_spec.rb | 0 seconds | Trend | |
| spec/models/shared_examples/taggable_spec.rb | 0 seconds | Trend | |
| spec/generator/services_generator_spec.rb | 0 seconds | Trend |