Repository navigation
ci(unit-tests): run the LATEST tier in a job of its own under coverage (#2751) - #2754
Merged
Merged
Conversation
#2751) `test`'s `latest` leg ran the `ALL` and `LATEST` tiers under coverage, and its p90 reached 55% of the 45-minute cap. The `LATEST` tier, less the project pins, was 57-58% of its test-seconds. - `test-latest-tier` runs that tier on `latest` by `test`'s steps, a half a cell, from `tests._tiers.latest_tier_half()` cut at `LATEST_TIER_BOUNDARY`; every `test` leg, `latest`'s included, now ignores the whole `LATEST` tier. - Each coverage leg checks its part (`coverage_report.py check`) and uploads it; the new `coverage` job combines the parts (`combine`), and posts no total unless every part arrived. - `required-checks` needs both jobs; the docs-only path may skip them. - `ci_timing.py` reads the halves' JUnit files as part of `latest`'s; `check_suite_report.py` counts `Coverage` as a gated leg. - The workflows and test-coverage pages, and the pins, follow.
JarryShaw
added
ci
Contributor
|
Coverage: 94.44% (unit tier, Python 3.15,
Per-file detail: the |
Owner
Author
|
GOOD TO GO at
After merge, CI Timing needs a re-baseline dispatch for the new job shape. |
JarryShaw
added
review: good-to-go
JarryShaw
removed
the
review: good-to-go
JarryShaw
added a commit
that referenced
this pull request
Nov 4, 2026
- Breaking: each protocol is a package of protocol, schema and data modules, the pcapkit.protocols.schema and .data trees and their aggregate exports removed with no alias, and a 1.5.x data model pickle fails to load (#2753), a new entry with the 1.5.1 imports and pickle measured. - 1.6.0's pcapkit.protocols role targets point at the package modules; the aggregator export claims of unreleased entries, the NoPayload and FrameRecord pickle claims and the TLSKeyLogEntries alias follow the layout. - CI: the LATEST tier's own job and the Coverage merge (#2754) and the ordering leg's halved rest of tests/protocols (21ec0a6, #2751), into the CI-legs entry; the package ruling into the conventions entry. - No entry for the test-only #2752. - The merge keeps #2483's class names in 1.5.0's conflicting roles under #2753's package paths. - CHANGELOG.md regenerated; util/changelog_md.py --check passes.
1 of 5 tasks
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
Python 3.15was the only leg that ran both test tiers, and it ran them under coverage. ItsRun unit testsstep took 23–31 min. The LATEST tier, minus the project pins, was 57–58% of that time.Python 3.15now skips the LATEST tier, as every other leg does, and runs only ALL, under coverage.test-latest-tierjob runs the LATEST tier minus the pins, under coverage. It is split in half atLATEST_TIER_BOUNDARYintests/_tiers.py, the way ci(timing): the project ordering leg will hit its 20-minute step cap within about a week #2254 splitproject.Coveragejob merges the three cells' data. It posts a number only when all three arrive, so coverage is still never reported from incomplete data. Both new jobs joinrequired-checks, and the ruleset contexts are unchanged.Python 3.15about 14.7 min, each LATEST half about 10.8 min, against a 45-minute cap.actionlintis clean, and thetests/projectpins and the docs that describe the legs are updated.Closes #2751