[JarryShaw]

• Searched for similar pull requests
• Followed the coding style (pylint, mypy, isort run on the two files: no new findings; tests/project/test_isort_clean.py passes)
• make test passes, and a test case covers the change (only the modules listed below were run)
• Added a changelog entry — N/A — centralised in docs(changelog): shared 1.5.0 changelog — long-lived, merges last (#610, #616, #617, #618, #620) #657

What is the purpose of your pull request?

• test — tests only

---

Closes #1428

• DEADLINE goes from 5 s to 30 s, the per-case budget test_option_roundtrip_unit already gives the same cycle. A working case takes ~1–5 ms. A real hang still trips it.
• New scale_deadline() stretches it by PCAPKIT_TEST_TIMEOUT_SCALE, with the same contract as tests._support.scale_timeout. It reads the variable directly, because the generator is a standalone script. Blank means unscaled. 0, negative, nan, inf, non-numeric, or past 86400 s raise ValueError before any handler is installed. deadline=0 stays off.
• 'TIMEOUT' and the did not finish within Ns detail are unchanged. N is now the seconds actually allowed.
• New tests/protocols/test_option_generator_deadline_scale_1428_unit.py: 7 tests. Against main's options.py: 15 failed, 5 passed. With this change: 7 passed, 13 subtests.
• make_samples.py before and after: all 23 captures have the same md5.
• Run one module per process, all green: httpv2_stream, 1337, tcp_base, option_roundtrip, option_coverage_runtime, construction_keyword_check, generators_import_their_own_tree, test_support_helpers, and tests/project (404 passed). Ordering leg protocols --exclude protocols/internet: 1091 tests, OK.
• CI does not set PCAPKIT_TEST_TIMEOUT_SCALE anywhere in .github/workflows/. This PR does not edit workflows.

[JarryShaw]

Verdict: GOOD TO GO at cc234a329 (Sonnet cross-review; the author ran on Opus).

• scale_deadline() matches tests/_support.py scale_timeout across 60 probes: blank, whitespace, junk, 0, negative, nan/±inf, 1e400, the 86400 ceiling, ceil, and the min of 1. No divergence.
• deadline=0 arms nothing. A bad scale raises before any handler or alarm is armed, so nothing is left behind.
• I re-ran it myself. On the PR, the new module gives 7 passed with 13 subtests. With options.py taken from main, it gives 15 failed, 5 passed.
• All 23 examples/captures/ md5s match main. The neighbour generator modules and tests/project are green (419 passed; the 404 in the body predates later merges).
• Unverified locally: Python 3.10, since no interpreter is installed. CI covers it.

Nits, no change needed:

• The parity with scale_timeout is by copy, so a parity assertion could guard against drift.
• A stray bad PCAPKIT_TEST_TIMEOUT_SCALE now ends make_samples.py with a raw ValueError.

[github-actions]

Coverage: 89.48% (unit tier, Python 3.14, cc234a329, Unit Tests run success)

Package	Statements	Missed	Branches	Partial	Cover
pcapkit (top level)	104	4	20	4	93.55%
pcapkit/const	18791	968	2352	869	90.90%
pcapkit/corekit	2043	89	636	25	94.77%
pcapkit/dumpkit	234	2	84	2	98.74%
pcapkit/foundation	2648	98	930	48	94.80%
pcapkit/interface	112	7	40	5	92.11%
pcapkit/protocols	16672	218	4490	182	98.07%
pcapkit/toolkit	539	74	168	3	84.58%
pcapkit/utilities	429	4	122	4	98.55%
pcapkit/vendor	4409	2342	1006	157	43.25%

Per-file detail: the coverage-html artifact of this run.