The es archiver load action is being updated to increase speed.

The usual culprit is the concurrency, which places data out of expected sort order.
We expect placing a sort order in the queries themselves is one solution.
Another could be asserting in such a fashion that does not require a sort order.

The tests were commented out in the index file.

This is issue is an attempt to ensure that no decreased coverage, goes overlooked.