Knapsack Pro

DEV Community (dev.to) / dev.to / Forem / Build ID d6902b21-d00e-403f-b004-712b92b9620d

Build Details

Back to CI builds

Public
Commit hash Branch Nodes Tests execution time Created at
05b37f8 refs/heads/gh-readonly-queue/main/pr-20803-0cc9cc0250bdfd1bb2a2de440ef1f4013b7ebcb2 8 27 minutes 41.29 seconds   5% 2024-04-04 12:12:18 UTC

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

Loading...

Parallel CI nodes

The first CI node finished its work at 2024-04-04 12:16:09 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 27.67 seconds.

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

Node index Finish time Tests execution time (27 minutes 41.29 seconds)
0 Finished First 2024-04-04 12:16:09 UTC 3 minutes 40.9 seconds
1 2024-04-04 12:16:10 UTC 3 minutes 37.99 seconds
2 2024-04-04 12:16:11 UTC 3 minutes 35.36 seconds
3 2024-04-04 12:16:09 UTC 3 minutes 36.11 seconds
4 2024-04-04 12:16:09 UTC 3 minutes 34.49 seconds
5 2024-04-04 12:16:10 UTC 3 minutes 36.09 seconds
6 Finished Last 2024-04-04 12:44:02 UTC 3 minutes 1.97 seconds
7 2024-04-04 12:16:10 UTC 2 minutes 58.42 seconds

Test Files recorded on parallel CI nodes

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

Running 9 parallel nodes should result in an optimal build time (~3.08 minutes)


Test file path (Displaying entries 901 - 916 of 916 in total files) Execution time
spec/lib/rails_env_constraint_spec.rb 4 miliseconds 85% Trend
spec/lib/data_update_scripts/add_billboard_location_targeting_feature_flag_spec.rb 4 miliseconds Trend
spec/lib/sidekiq/worker_retries_exhausted_reporter_spec.rb 4 miliseconds 77% Trend
spec/lib/data_update_scripts/add_multiple_reactions_feature_flag_spec.rb 4 miliseconds 78% Trend
spec/models/hair_trigger_spec.rb 4 miliseconds 19% Trend
spec/services/badges/award_eight_week_streak_spec.rb 4 miliseconds 71% Trend
spec/services/badges/award_sixteen_week_streak_spec.rb 4 miliseconds 93% Trend
spec/services/audit/helper_spec.rb 4 miliseconds Trend
spec/liquid_tags/poll_tag_spec.rb 4 miliseconds 19% Trend
spec/lib/liquid/variable_spec.rb 4 miliseconds 19% Trend
spec/services/images/profile_image_generator_spec.rb 4 miliseconds Trend
spec/system/dashboards/user_followers_display_spec.rb 0 seconds Trend
spec/models/shared_examples/taggable_spec.rb 0 seconds Trend
spec/generator/services_generator_spec.rb 0 seconds Trend
spec/system/comments/user_fills_out_comment_spec.rb 0 seconds Trend
spec/requests/api/v1/docs/follows_spec.rb 0 seconds Trend

Start using Knapsack Pro

Sign up and speed up your tests.