My organization (openfoodnetwork.org) / Open Food Network / knapsack_rspec_test_the_rest / Build ID 5d5e8881-7194-40bb-933b-ec8f9d01e392

Public     Back to CI builds

Build Details

Commit hash Branch Parallel nodes Created at Updated at
727f7d086d9c17274d569e5dbb52d6044c33f595 refs/pull/10258/merge 5 2023-01-11 10:11:14 UTC 2023-01-11 10:11:14 UTC

Parallel CI Nodes

4 out of 5 parallel CI nodes completed tests.

See your CI server output for CI nodes with index 1 to verify if tests have been completed.

Refresh this page to see up-to-date results.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 18.439 seconds. The shorter this time is, the better.

Loading...

Parallel CI nodes

The first CI node finished its work at 2023-01-11 10:11:14 UTC. CI nodes that finished at least 60s later are highlighted.

The reason for slow CI nodes might be too large test files (see the Test Files tab). You may want to try the Knapsack Pro Queue Mode (Ruby) to improve the distribution of your tests. Learn more about dynamic test suite split here.

Note: if you run a CI build for the same commit again (for instance when you retry a CI build), then you will see the data updated below. Some of the nodes might be highlighted until the whole CI build is complete.

The average test execution time per CI node is 2 minutes 3.242 seconds.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 18.439 seconds. The shorter this time is, the better.

Node index Finish time Execution time
0 Finished First 2023-01-11 10:11:14 UTC 2 minutes 6.934 seconds
2 Finished Last 2023-01-11 10:12:32 UTC 2 minutes 48.64 seconds
3 2023-01-11 10:11:43 UTC 1 minute 39.703 seconds
4 2023-01-11 10:11:32 UTC 1 minute 37.691 seconds
All parallel CI nodes must complete their work before you can see recorded test files.

Start using Knapsack Pro

Sign up and speed up your tests.