Foundation / checks (ecs) (push) Successful in 2m33s
Foundation / checks (deploy) (push) Successful in 4m36s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 8m8s
Foundation / checks (checks) (push) Canceled after 10m47s
Foundation / checks (client) (push) Canceled after 10m49s
Foundation / checks (network) (push) Canceled after 10m48s
Foundation / checks (postgres) (push) Canceled after 10m49s
47 lines
2.9 KiB
Markdown
47 lines
2.9 KiB
Markdown
# M12 CI execution repair
|
|
|
|
The maintainer supplied `Build_Errors.txt`, retained as local evidence rather than
|
|
committed build output. Its repeated checks/TSan logs show the unchanged full
|
|
cohort verification exceeding 180 seconds. The read-only TSan container also
|
|
rejects the new population/migration fixture directories under `/source/build`.
|
|
The client gate passes its 14 CTests, then intermittently fails while opening the
|
|
rebinding test's SDL application under a real Xvfb display.
|
|
|
|
## Changes
|
|
|
|
- Keep every cohort case, seed, capacity sample and sanitizer enabled. Its CTest
|
|
budget is 180/600/900 seconds for normal/ASan/TSan. The larger migration contract
|
|
gets 180/360/600 seconds. These are execution bounds, not performance acceptance.
|
|
- Population/migration restart scripts accept runtime `EVO_TEST_TMPDIR`, using a
|
|
distinct fixture directory for each invocation. The TSan container sets it to
|
|
the existing bounded `/tmp` tmpfs. Source/build mounts stay read-only; user,
|
|
capabilities, network isolation and the pinned seccomp policy are unchanged.
|
|
- Allow 90 minutes for the checks matrix job: the captured cold/shared-runner run
|
|
reached 59 minutes before the timeout, before remaining fuzz/benchmark steps.
|
|
- Xvfb lifecycle invocations use `-noreset` to retain their display server across
|
|
deliberate SDL quit/reopen cycles. If opening still fails, the test now records
|
|
the typed Application error category instead of only an uninformative line.
|
|
The server-reset explanation is an inference: the original reopen failure was
|
|
not reproduced in twenty local runs of the old invocation. CI must confirm it.
|
|
- Full GCC client builds exposed two additional warnings-as-errors: extraction
|
|
through `std::exchange(optional, {})` and a copied panel-fixture range value.
|
|
The grant is now checked/moved/reset under the same mutex, preserving its
|
|
consume-once public contract; the fixture uses a const reference. No warning
|
|
suppression, authentication policy, protocol, UI appearance or biology changes.
|
|
|
|
## Evidence and limits
|
|
|
|
Executed compiler/test results are in [VALIDATION](VALIDATION.md). Local Linux
|
|
TSan runs the full cohort matrix and both process-restart contracts; ASan runs
|
|
the full cohort verification. Protected configured output fails without the
|
|
runtime override and both restart scripts pass using `/tmp` with that output
|
|
still inaccessible. CTest metadata confirms the normal and instrumented budgets.
|
|
GCC/MSVC client contracts, repeated real-X11 lifecycle runs and sanitizer checks
|
|
exercise the affected client paths without an external identity provider.
|
|
|
|
The local Docker executable cannot reach its Linux engine. No full Docker image,
|
|
actual read-only/seccomp container, remote CI success or deployment is claimed.
|
|
The captured client reopen failure remains unconfirmed locally; the next CI run
|
|
has an explicit display lifetime and an informative failure category.
|
|
World0, live regions and the biological/persistence contracts were not changed.
|