You have --shuffle in use, so --load-list does not determine the order
of execution. Certainly for other test runners, or for test runs
without --shuffle, you could use the load-list files as an
approximation, *as long as* the test runner in question cooperates.
For your scenario here though, of being able to reconstruct what an
arbitrary run did, you can't depend on them. (Due to shuffle).
> Your approach certainly sounds more general, and could be the basis of
> nice general purpose support. As you'd expect, a full solution for our
> own use case needs to provide easy access to the filtered list of tests
> for a particular worker in a format that we can then use bin/test
> --load-list on.
Yes, you'd be able to filter the run down quite easily I think.
You have --shuffle in use, so --load-list does not determine the order
of execution. Certainly for other test runners, or for test runs
without --shuffle, you could use the load-list files as an
approximation, *as long as* the test runner in question cooperates.
For your scenario here though, of being able to reconstruct what an
arbitrary run did, you can't depend on them. (Due to shuffle).
> Your approach certainly sounds more general, and could be the basis of
> nice general purpose support. As you'd expect, a full solution for our
> own use case needs to provide easy access to the filtered list of tests
> for a particular worker in a format that we can then use bin/test
> --load-list on.
Yes, you'd be able to filter the run down quite easily I think.