My organization (pirasanthan@intros.at) / Test / Cypress-Test Public

Back to CI builds

Build details ID e4cf3660-96ed-4ea3-9fab-51906f988909

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
0ee3b46ad52429f4499ed2f43e30fb571a78c596 refs/heads/master 2 2021-02-15 13:53:18 UTC 2021-02-15 13:53:15 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!

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 time gap between the finish times of the CI node that Finished First and the one which Finished Last is 2.735 seconds

Loading...
Node Index Created At Time execution
0 Finished First 2021-02-15 13:53:15 UTC 0 seconds
1 Finished Last 2021-02-15 13:53:18 UTC 0 seconds

Start using Knapsack Pro

Sign up and speed up your tests.