|
Ran
|
Jobs
1
|
Files
7
|
Run time
1min
|
Badge
README BADGES
|
push
github
Define the per-Python notebook environments tox.ini meant to define (#398) (#404) envlist asks for py310-notebook through py314-notebook, but none of those environments existed. tox expands numeric ranges in a section name before it splits the name on braces, so [testenv:{,py-,py3-,py310-,py311-,py312-,py313-,py314-}notebook] parses as "py3" plus the range "10-14". That defines py3notebook, 4notebook, 5notebook, 6notebook and 7notebook -- none of which anything asks for -- and never defines py310-notebook or its siblings. Those then fall through to [testenv], where they pick up the test extras and a bare pytest, so tox -e py312-notebook installed the unit-test dependencies and ran the unit tests instead of the notebooks, reporting success without executing a single cell. Spelling the names out fixes it. CI is unaffected either way, since it runs `tox -e py,notebook` and the unfactored notebook env always resolved correctly; this only ever bit someone running a versioned env by hand. Also modernize the key spellings tox 4 prefers -- minversion, envlist, basepython and passenv become min_version, env_list, base_python and pass_env -- and drop isolated_build, which has been the default since tox 4. The resolved configuration of every environment is unchanged apart from PYTHONHASHSEED, which tox randomizes per run. Assisted-by: Claude Opus 5 (cherry picked from commit 74c08801a) Co-authored-by: Jim Garrison <garrison@ibm.com>
668 of 806 relevant lines covered (82.88%)
0.83 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 38982270876.1 | 7 |
82.88
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|