My organization (openfoodnetwork.org) / Open Food Network / test_the_rest / Build ID a218e426-80dd-46a0-9cad-6ac53f0accd9
Commit hash | Branch | Nodes | Start | Wall time | Tests execution time |
---|---|---|---|---|---|
87bfe50 | refs/heads/activate_admin_style_v3_for_dev_test_and_new_servers | 5 | 2 months ago | - | N/A |
4 out of 5 parallel CI nodes finished tests.
See your CI server output for CI nodes with index 1 to verify if tests have been finished.
The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 39.04 seconds. The shorter this time is, the better.
The first CI node finished its work at 2024-07-09 16:40:30 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 32.97 seconds.
The time span between the finish times of the CI node that Finished First and the one which Finished Last is 1 minute 39.04 seconds. The shorter this time is, the better.
Node index | Finish time | Tests execution time (10 minutes 11.85 seconds) | Test files |
---|---|---|---|
0 Finished Last | 2024-07-09 16:42:09 UTC | 3 minutes 11.56 seconds | |
2 | 2024-07-09 16:40:55 UTC | 2 minutes 30.97 seconds | |
3 | 2024-07-09 16:41:10 UTC | 2 minutes 30.72 seconds | |
4 Finished First | 2024-07-09 16:40:30 UTC | 1 minute 58.62 seconds | |