Knapsack Pro

DEV Community (dev.to) / dev.to / Forem / Build ID 40df277d-38bc-4968-8bbc-07af3bcbc33b

Build Details

Back to CI builds

Public
Commit hash Branch Nodes Start Wall time Tests execution time
0c1831a refs/pull/21358/merge 8 17 days ago 5 minutes 45.6 seconds 35 minutes 25.29 seconds   24%

Parallel CI nodes

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 15.49 seconds. The shorter this time is, the better.

Parallel CI nodes

The first CI node finished its work at 2024-11-07 18:21:53 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 4 minutes 25.67 seconds.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 15.49 seconds. The shorter this time is, the better.

Node index Finish time Tests execution time (35 minutes 25.29 seconds) Test files
0 Finished First 2024-11-07 18:21:53 UTC 4 minutes 17.33 seconds
1 Finished Last 2024-11-07 18:23:09 UTC 5 minutes 28.53 seconds
2 2024-11-07 18:21:54 UTC 4 minutes 14.79 seconds
3 2024-11-07 18:21:54 UTC 4 minutes 15.19 seconds
4 2024-11-07 18:21:56 UTC 4 minutes 19.76 seconds
5 2024-11-07 18:21:56 UTC 4 minutes 17.89 seconds
6 2024-11-07 18:21:53 UTC 4 minutes 17.43 seconds
7 2024-11-07 18:21:55 UTC 4 minutes 14.4 seconds

Test Files recorded on parallel CI nodes

You can likely decrease your CI build time by around 54 seconds by running more parallel CI nodes.

Running 10 parallel nodes should result in an optimal build time (~3.54 minutes)


Test file path (Displaying entries 901 - 927 of 927 in total files) Execution time
spec/lib/liquid/render_spec.rb
5 miliseconds 66% Trend
spec/workers/podcasts/bust_cache_worker_spec.rb
5 miliseconds 88% Trend
spec/liquid_tags/null_tag_spec.rb
5 miliseconds 72% Trend
spec/services/badges/award_sixteen_week_streak_spec.rb
5 miliseconds Trend
spec/services/edge_cache/bust_page_spec.rb
5 miliseconds 70% Trend
spec/lib/rails_env_constraint_spec.rb
5 miliseconds 70% Trend
spec/lib/liquid/echo_spec.rb
4 miliseconds 93% Trend
spec/liquid_tags/slideshare_tag_spec.rb
4 miliseconds 19% Trend
spec/services/feeds/clean_html_spec.rb
4 miliseconds 19% Trend
spec/services/audit/subscribe_spec.rb
4 miliseconds 91% Trend
spec/services/badges/award_four_week_streak_spec.rb
4 miliseconds 33% Trend
spec/initializers/carrierwave_monkeypatch_spec.rb
4 miliseconds 19% Trend
spec/models/hair_trigger_spec.rb
4 miliseconds 19% Trend
spec/lib/sidekiq/worker_retries_exhausted_reporter_spec.rb
4 miliseconds 92% Trend
spec/lib/data_update_scripts/add_billboard_location_targeting_feature_flag_spec.rb
4 miliseconds 19% Trend
spec/services/images/profile_image_generator_spec.rb
4 miliseconds 92% Trend
spec/lib/reverse_markdown/converters/custom_text_spec.rb
4 miliseconds 19% Trend
spec/liquid_tags/poll_tag_spec.rb
4 miliseconds 19% Trend
spec/refinements/string_to_boolean_spec.rb
4 miliseconds 19% Trend
spec/lib/liquid/variable_spec.rb
4 miliseconds 19% Trend
spec/services/audit/helper_spec.rb
4 miliseconds 75% Trend
spec/models/shared_examples/taggable_spec.rb
0 seconds Trend
spec/system/comments/user_fills_out_comment_spec.rb
0 seconds Trend
spec/generator/services_generator_spec.rb
0 seconds Trend
spec/requests/api/v1/docs/follows_spec.rb
0 seconds Trend
spec/system/dashboards/user_visits_dashboard_spec.rb
0 seconds 100% Trend
spec/system/dashboards/user_followers_display_spec.rb
0 seconds Trend

Start using Knapsack Pro

Sign up and speed up your tests.

Get started free