My organization ( / office_stuff / Minitest Public

Back to CI builds

Build details ID eaa6aa3c-5744-4592-93d6-c1ea5abff800

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

Commit hash Branch Node total Updated at Created at
5d45953fdbb5ad1a20640daecb627509d8e1b3bc refs/heads/master 2 2020-04-03 02:42:47 UTC 2020-04-03 02:42:47 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 first CI node finished its work at 2020-04-03 02:42:47 UTC. CI nodes that finished at least 60s later are highlighted.

The reason for slow CI nodes might be too large test files (you can see the slowest test files at the bottom of the page when all CI nodes collected time execution data). You may want to try Knapsack Pro Queue Mode (Ruby) to solve a problem with the random performance of test files or your CI nodes. Learn more about dynamic test suite split here.

Note: if you run CI build for the same commit again (for instance when you retry CI build), then you will see build subsets updated below. Until retried CI build finishes work you may see highlighted build subsets.

Average time execution per collected CI node is 8.818 seconds.

The time gap between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 3.349 seconds

Node Index Created At Time execution
0 Finished Last 2020-04-03 02:43:50 UTC 9.3 seconds
1 Finished First 2020-04-03 02:42:47 UTC 8.336 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
28eaa5e1-923f-48e7-b8cb-4a3a80cf4d5d 2 17.636 seconds 8.818 seconds 0.806 seconds

The slowest test files for the Build Distribution

All test files have time execution below node max time execution so they can be well split across CI nodes.
Test file path (12 files) Time execution
test/controllers/users_controller_test.rb 7.751 seconds
test/controllers/comments_controller_test.rb 7.447 seconds
test/jobs/stuffs_job_test.rb 1.654 seconds
test/controllers/stuffs_controller_test.rb 0.348 seconds
test/mailers/comment_mailer_test.rb 0.114 seconds
test/mailers/stuff_mailer_test.rb 0.088 seconds
test/controllers/sessions_controller_test.rb 0.072 seconds
test/models/user_test.rb 0.047 seconds
test/models/stuff_test.rb 0.044 seconds
test/models/comments_test.rb 0.033 seconds
test/jobs/comments_job_test.rb 0.033 seconds
test/models/category_test.rb 0.01 seconds

Start using Knapsack Pro

Sign up and speed up your tests.