mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-07 01:53:24 +09:00
[CI] (.github/workflows, docs/ci, scripts/ci, tools/trace_replay): drop the retrace-split reruns
- retrace-split loses its two negative controls, which re-ran every leg (~68 runner-min per run), and its dependency on the monolith-control artifact; the in-test evidence check from the previous commit replaces them - build-linux-monolith-control keeps its zero-MG_Remote proof and its upload; on the disaggregation branches the new retrace-shipped job replays OpenRA on both backends through that library (elsewhere the retrace job's library has that shape), so the shipped shape is still replayed on every branch - delete retrace_transport_control.sh, retrace_drop_draw_control.sh, their smoke cases and stub modes, and the uncalled redcheck_control_smoke_test.sh - control-runtime/build-push-control leaves the eleven metadata loops; remove-artifact-clutter waits for retrace-shipped
This commit is contained in:
@@ -394,11 +394,11 @@ def github_transport_matrix(cases, *, apk=False):
|
||||
THE SPAWN LANE IS APK-ONLY, and that is a statement about where the evidence is missing
|
||||
rather than about what spawn can do. On Linux the spawn arm already has a job of its own -
|
||||
test.yml's `retrace-split`, which is {backend, case, transport} over inproc AND spawn and
|
||||
carries the two negative controls that make it mean anything (the pull library must red it,
|
||||
dropping the draws must red it). Adding spawn to THIS matrix as well would pay for a second
|
||||
full Linux sweep that proves nothing the first one does not, and test.yml's `retrace` job
|
||||
has neither the server image staged nor MOBILEGL_IPC_SERVER_PATH set - so the lane would
|
||||
not merely be redundant, it would be red.
|
||||
whose legs prove in-test that the transport resolved and, on OpenRA, that draw records
|
||||
crossed the wire (run_trace_case.cmake's evidence). Adding spawn to THIS matrix would pay
|
||||
for a second full Linux sweep that proves nothing the first one does not, and test.yml's
|
||||
`retrace` job has neither the server image staged nor MOBILEGL_IPC_SERVER_PATH set - so the
|
||||
lane would not merely be redundant, it would be red.
|
||||
|
||||
On Android there is no such job. Until this lane existed, nothing in CI ever started a
|
||||
second MobileGL process on a device.
|
||||
|
||||
Reference in New Issue
Block a user