Repository navigation
Install Windows CI dependencies with pip instead of conda, test 3.12 too - #1344
Merged
Merged
Conversation
conda was only used on Windows because msprime had no Windows wheels; it now ships them for Python 3.11 through 3.14. The conda-forge solve recently started pulling in both MKL (libiomp) and llvm-openmp (libomp), which makes threadpoolctl raise a RuntimeWarning in test_genee and fails the run because warnings are errors. Using pip for everything avoids the mixed OpenMP runtimes and removes the setup-miniconda step.
This was referenced Sep 3, 2026
Closed
Matches the Build workflow, which already covers 3.11 and 3.12.
Billyzhang1229
marked this pull request as ready for review
September 3, 2026 16:21
Member
|
This seems like a straightforward win, merging |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Windows workflow started failing in
test_geneewith warnings treated as errors:conda install msprimeon conda-forge now resolves to MKL (libiomp) plusllvm-openmp(libomp), while the pip-installed scientific stack brings its own OpenMP, so threadpoolctl sees both runtimes. I confirmed the failure is independent of thesetup-minicondaversion by running the same job with v2 and v4.conda was only used on Windows because msprime had no Windows wheels at the time. It now publishes them for Python 3.11 through 3.14, so this switches the job to
setup-python+ pip like the other workflows and drops the miniconda step entirely.Second commit adds Python 3.12 to the matrix so Windows covers the same versions as the Build workflow.
Verified green on my fork