Knapsack Pro / jest-example-test-suite / Jest - Public

Back to CI builds

Build details ID 4f0c53cd-a6ad-4c23-a9d9-713292ab463c

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
09c495a697627f2a8a757152a35029ebddcb4093 master 2 2020-06-27 21:15:55 UTC 2020-06-27 21:15:55 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.12 seconds

Node Index Created At Time execution
0 Finished First 2020-06-27 21:15:55 UTC 6.312 seconds
1 Finished Last 2020-06-27 21:15:55 UTC 5.027 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
ff821db0-5a0c-4345-8807-4db7b32e2f2e 2 11.339 seconds 5.67 seconds 0.643 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 (3 files) Time execution
__tests__/a.test.js 5.027 seconds
__tests__/b.spec.js 3.163 seconds
__tests__/directory/c.test.js 3.149 seconds

Start using Knapsack Pro

Sign up and speed up your tests.