`circleci tests` doesn't catch previous timings


#1

Hello!

Here’s the relevant config.yml:

 - run:
   name: Rails run tests
   command: |
      bin/rspec \
         --format RspecJunitFormatter --out /tmp/test-results/rspec.xml \
         --format progress \
         $(circleci tests glob "spec/**/*_spec.rb" "front/spec/**/*_spec.rb" | circleci tests split --split-by=timings)

 - store_test_results:
    path: /tmp/test-results

 - store_artifacts:
   path: /tmp/test-results

I’ve checked Artifacts tab and rspec.xml was indeed stored. However, when running the build again I get “Requested historical based timing, but they are not present. Falling back to name based sorting”.

https://circleci.com/docs/2.0/parallelism-faster-jobs/ states that “CircleCI automatically makes timing data from previous runs available inside your container in a default location so the CLI tool can discover them (/.circleci-task-data/circle-test-results/).” I thought that “store_test_results” takes care of that (at least https://circleci.com/docs/2.0/language-ruby/ doesn’t mention anything related).


#2

Can you link to where you’re seeing that functionality?


#3

I’m not sure if the problem still exists, because I don’t see it in latest builds.

The branch is here https://circleci.com/gh/hasanove/halalbooking/tree/circle-20
Starting from https://circleci.com/gh/hasanove/halalbooking/9490 you can see that store_test_results is present in config.yml. Despite that those builds

https://circleci.com/gh/hasanove/halalbooking/9492
https://circleci.com/gh/hasanove/halalbooking/9513
https://circleci.com/gh/hasanove/halalbooking/9525
https://circleci.com/gh/hasanove/halalbooking/9535

didn’t catch previous timing.

However, when I temporarily removed usage of circleci tests in https://circleci.com/gh/hasanove/halalbooking/9537 (was debugging a failing spec) and brought it back in https://circleci.com/gh/hasanove/halalbooking/9543 then the next builds

https://circleci.com/gh/hasanove/halalbooking/9546
https://circleci.com/gh/hasanove/halalbooking/9549

don’t contain the warning message anymore.


#4

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.