My organization (noah@comakery.com) / https://github.com/CoMakery/comakery-server / RSpec / Build ID 0570dcf2-8a83-4abf-a085-03f74b999a25
Public Back to CI builds
| Commit hash | Branch | Parallel nodes | Created at | Updated at |
|---|---|---|---|---|
| 29ca2c2a75dc5072592e8c0b99b8b74a718d35bb | refs/heads/feature/prd-538 | 10 | 2023-02-16 16:21:22 UTC | 2023-02-16 16:21:22 UTC |
6 out of 10 parallel CI nodes completed tests.
See your CI server output for CI nodes with index 0, 1, 2, 3 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 8 minutes 25.071 seconds. The shorter this time is, the better.
The first CI node finished its work at 2023-02-16 16:21:22 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 21 minutes 7.907 seconds.
The time span between the finish times of the CI node that Finished First and the one which Finished Last is 8 minutes 25.071 seconds. The shorter this time is, the better.
| Node index | Finish time | Execution time |
|---|---|---|
| 4 | 2023-02-16 16:21:28 UTC | 18 minutes 3.0 seconds |
| 5 Finished First | 2023-02-16 16:21:22 UTC | 20 minutes 13.354 seconds |
| 6 | 2023-02-16 16:21:23 UTC | 20 minutes 5.427 seconds |
| 7 Finished Last | 2023-02-16 16:29:47 UTC | 28 minutes 18.926 seconds |
| 8 | 2023-02-16 16:21:24 UTC | 19 minutes 49.407 seconds |
| 9 | 2023-02-16 16:21:35 UTC | 20 minutes 17.329 seconds |