Hey, we are splitting our rspec tests across parallel nodes to decrease the end-to-end time, and we’re trying to do it by the
timings split type as specified here: https://circleci.com/docs/2.0/parallelism-faster-jobs/#splitting-patterns
But despite many, many runs through, each job continues to report:
Requested historical based timing, but they are not present. Falling back to name based sorting
We are storing the test results as per https://circleci.com/docs/2.0/configuration-reference/#store_test_results (despite the documentation still stating that key is not supported for workflows [?]) and the job’s test summary does display timing data about the slowest test etc once the job is run, so Circle is obviously picking it up, but it looks like it’s just not persisting it and making it available to future runs as promised.
Are we doing something wrong or is this just broken?