Comment 4 for bug 1902727

When we prune by age, we do avoid pruning any actions that have not completed.
However, when we prune by size, we do prune actions regardless of completed status, the oldest first, to get the collection size back under the limit.

The size limit defaults to 5G and is set by the model config max-action-results-size.
It is surprising that the 5G limit would be exceeded, unless there are some actions which have run and which have generated a lot of output.

But I do agree that when pruning by size, we should not start with only completed actions.