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

Back to CI builds

Build details ID 0c78d6fc-f2e4-40d6-a014-5091be3e74c6

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
53ae1876df9dff267a042707f017d2abfaf68977 master 2 2019-10-25 10:43:05 UTC 2019-10-25 10:43:05 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.777 seconds

Node Index Created At Time execution
0 Finished First 2019-10-25 10:43:05 UTC 5.608 seconds
1 Finished Last 2019-10-25 10:43:06 UTC 5.038 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
4d5c6c8a-7d14-4da7-89e3-59fc7f92ab82 2 10.646 seconds 5.323 seconds 0.285 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.038 seconds
__tests__/b.spec.js 2.885 seconds
__tests__/directory/c.test.js 2.723 seconds

Start using Knapsack Pro

Sign up and speed up your tests.