DEV Community ( / / Cypress tests Public

Back to CI builds

Build details ID 169d8743-8eb3-4a88-bdfa-07e02c6c6b25

You find here details about tests recorded for below git commit hash across 3 parallel CI nodes for master branch.

Commit hash Branch Node total Updated at Created at
e3c6c71f9747d54224d0e260f7694222542c5ca5 master 3 2021-01-11 13:57:36 UTC 2021-01-11 13:57:21 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 3 out of 3.

All CI nodes sent time execution data to Knapsack Pro API. Everything works!

When one of your CI nodes has a time execution of 0, it means that other CI nodes had already executed all tests so that CI node had no work to do. It could happen when you use the Queue Mode and one of the CI nodes started later - at a time when other CI nodes had already completed all of the work.

The first CI node finished its work at 2021-01-11 13:57:21 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 4.32 seconds.

The time gap between the finish times of the CI node that Finished First and the one which Finished Last is 30 minutes 10.011 seconds

Node Index Created At Time execution
0 Finished Last 2021-01-11 14:27:31 UTC 0 seconds
1 2021-01-11 13:57:36 UTC 0 seconds
2 Finished First 2021-01-11 13:57:21 UTC 12.958 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
ccb3429d-ddbd-4e15-89a7-15c116af6ea0 3 12.958 seconds 4.32 seconds 8.639 seconds

The slowest test files for the Build Distribution

The slow test files are highlighted in yellow below.

Test files with higher time execution than 4.32 seconds are bottleneck because they take more time than expected execution time per parallel CI node.

Please check how to improve test suite split for the slowest test files.

Test file path (1 files) Time execution
cypress/integration/loginFlows/initialAdminLogin.spec.js 12.958 seconds

Start using Knapsack Pro

Sign up and speed up your tests.