Repository navigation
ci(unit-tests): run the whole suite on latest CPython (#1958) - #1976
Merged
Merged
Conversation
- test, integration: a step on the latest leg alone installs the whole suite's extras (Scapy, PyShark, vendor, docs, cli on top of the base); every other leg keeps its install line and runs the ALL tier. - project-tests, gate: install the same set. - tests/_dependency_gates.py: read a latest-only install step as that leg's extras; drop the exclusions it closes (HAS_SCAPY, HAS_PYSHARK, HAS_RUNTIME, HAS_VENDOR_DEPS, HAS_SPHINX, HAS_DOCUTILS, HAS_FURO). - tests/project/test_whole_suite_on_latest_1958.py pins the lines, the leg, the gates closed and the docs; tier-guard, #1732 and #1954 pins follow the new reading. - workflows.rst describes it; unit-tests.yml line citations re-anchored. Selection steps and tests/_tiers.py are unchanged.
JarryShaw
added
ci
…1958) - test, integration: the install comments said cli, and crypto and NGAP, are not installed; the latest leg's whole-suite step installs them. - workflows.rst, releasing.rst: unit-tests.yml line citations re-anchored.
Owner
Author
|
GOOD TO GO at |
Owner
Author
|
GOOD TO GO at |
JarryShaw
added
review: good-to-go
Contributor
|
Coverage: 91.52% (unit tier, Python 3.15,
Per-file detail: the |
This was referenced Oct 20, 2026
JarryShaw
removed
the
review: good-to-go
This was referenced Oct 20, 2026
Closed
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.
make pylint,make mypy,make isort)make testpasses, and a test case covers the changeWhat is the purpose of your pull request?
ci— workflows or build toolingDescription of your pull request and other information
#1958 phase 2 (rulings C and E). On latest CPython,
test,integrationandproject-teststogether run the whole suite, and each installs everything the suite gates on, so the tests that ran nowhere get a job.testandintegrationgain a latest-only step, "Install the whole suite's dependencies on latest", installing.[test,Scapy,DPKT,crypto,cli,NGAP,vendor,docs,PyShark].project-testsandgateinstall the same set. Other legs keep their install line.gate, the html5lib vendor tests, the Sphinx/docutils/furo docs tests, and the PyShark gates.tests/_dependency_gates.pyreads the new step as the latest leg's extras and drops the exclusions it closes. PCAP_CT (needs system libpcap;engine-testscovers it) and PyPCAP/PyPCAPFile (do not install on 3.12+) stay excluded. The mypy/pylint-gated tests still run in no pytest job, unchanged here; they are lint tools no extra declares.tests/project/test_whole_suite_on_latest_1958.pypins the new install set. It fails onmainand passes here.The review ran the PyShark, Sphinx and html5lib modules, the fixture tier and the project pins on a fresh 3.15 venv with exactly these extras and no tshark on
PATH. There were no failures.Refs #1958