[JarryShaw]

• Searched for similar pull requests
• Followed the coding style (make pylint, make mypy, make isort)
• make test passes, and a test case covers the change
• 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?

• ci — changes to CI configuration files and scripts

---

Description of your pull request and other information

Closes #2073. Nothing was missing. Both legs in run 39898029852 were stopped as superseded (#1938):

• The logs: job 120233865230 shows Terminated … systemd-run at 60 s, then main is at 27288aa93, no longer at 271534c35; job 120233865247 shows the same. Only after that does Upload test timings warn about junit*.xml, which pytest never got to write.
• The path is fine: --junitxml="$RUNNER_TEMP/junit.xml" matches the glob.
• When it started: 6a4a72f (ci(experimental): skip or stop superseded runs instead of cancelling them (#1938) #1942), which changed cancelling superseded runs into stopping them. Across 114 Experimental runs on main since then, 57 of 58 missing-JUnit warnings come from stopped legs. The other one is a real OOM kill that already warns on its own.

The fix:

• util/superseded.py watch writes stopped=true to $GITHUB_OUTPUT after it stops the tests, without failing the stop if that write fails.
• Upload test timings sets if-no-files-found to ignore when steps.tests.outputs.stopped == 'true', and warn otherwise. A stopped leg is already explained by its notice, while a leg that finished without JUnit still warns.
• workflows.rst gets one paragraph in the ci(experimental): skip or stop superseded runs instead of cancelling them, so commits are not marked red #1938 section.

Tests: the new test_superseded_junit_upload_2073 covers the expression for each value, the glob against the step's path, and the watcher's output on stop, on a normal exit and on a failed write. It also runs the real Run unit tests script with a stub pytest. On main it gives 8 failed; here, 8 passed. The superseded, KTLO-guard, matrix-tier, reporter, timing, shard and workflow tests all pass.

Unverified until a live run: that upload-artifact v7.0.2 accepts the expression for if-no-files-found.

[JarryShaw]

GOOD TO GO at 60ee02f32 (Sonnet cross-review).

• Root cause: confirmed from both jobs' logs. pytest stops at 27% with Terminated … systemd-run, the superseded notice follows, and only then comes the junit*.xml warning.
• The output reaches the step: superseded.py watch is the step's foreground command, not a background process. It inherits that step's $GITHUB_OUTPUT, writes stopped=true before return 0, and the step id is tests.
• if-no-files-found: the pinned upload-artifact (cf430e03, v7.0.2) lists warn/error/ignore, and the expression always yields one of them.
• Real failures still warn: stopped=true is written only after a successful stop. A crash or normal exit writes nothing, so a missing file still warns, and GraalPy's partial shard files are still uploaded.

The same two warnings recur in Discussion #2072 for run 39898095976; this PR and #2075 cover both.

[github-actions]

Coverage: 91.54% (unit tier, Python 3.15, 60ee02f32, Unit Tests run success)

Package	Statements	Missed	Branches	Partial	Cover
pcapkit (top level)	104	4	20	2	95.16%
pcapkit/const	19599	880	2618	866	92.12%
pcapkit/corekit	2565	71	812	37	96.56%
pcapkit/dumpkit	282	3	102	3	98.44%
pcapkit/foundation	2930	23	1022	25	98.79%
pcapkit/interface	138	4	52	3	96.32%
pcapkit/protocols	17414	219	4574	185	98.14%
pcapkit/toolkit	869	36	298	10	95.20%
pcapkit/utilities	473	7	136	5	98.03%
pcapkit/vendor	4432	1988	1018	167	51.87%

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

[JarryShaw]

Ready to merge at 60ee02f32: the review is GOOD TO GO and CI is complete (56 passed, 0 failed). The ordering leg ran 2049 tests with 0 failures. The 3.8–3.10 KTLO legs show 0 failing tests, and the PR is based on current main (61bb4ba66).