Added python3.10 env

[5hv5hvnk]

Ran test suit and added coda environment for python 3.10

resolves #5209

[ricardoV94]

You seem to have based your branch on an old version of the repository. The tests were recently merged into a single file: #5623

[michaelosthege]

Just start fresh from the latest main branch. Trying to resolve the git conflicts would be much more work than reapplying them manually.

And make sure that you only commit the necessary files. There are some coverage files that should not be git committed.

[codecov]

Codecov Report

Merging #5638 (917d7f0) into main (7a6bd02) will not change coverage.
The diff coverage is n/a.

❗ Current head 917d7f0 differs from pull request most recent head 5182ae7. Consider uploading reports for the commit 5182ae7 to get more accurate results

@@           Coverage Diff           @@
##             main    #5638   +/-   ##
=======================================
  Coverage   88.57%   88.57%           
=======================================
  Files          75       75           
  Lines       13677    13677           
=======================================
  Hits        12114    12114           
  Misses       1563     1563           

[ricardoV94]

You still seem to have committed 3 files that shouldn't have been committed: https://github.com/pymc-devs/pymc/pull/5638/files

[ricardoV94]

And you will need to swap the conda environment used in the tests to use this new one (and delete the old py37 environments): https://github.com/pymc-devs/pymc/blob/main/.github/workflows/tests.yml

[ricardoV94]

@michaelosthege Could the failing tests be a conda cache issue?

[michaelosthege]

I don't know about conda caching.

But the changes in test.yml affect all jobs at the same so it's really hard to tell. The current changes are

• Ubuntu 3.7→3.8
• Windows 3.8→ 3.9
• MacOS 3.9→3.10
• Ubuntu/Jax 3.9→3.10
• Windows/float32 3.8→3.9

The Windows jobs are failing because the corresponding environment YAML does not exist.

The MacOS jobs fail because of build problems?

→→ I would advise to first bump only the Ubuntu job from 3.7→3.10 to see if it's even working there. But the Ubuntu/Jax job also has build problems, so the answer is likely "No"