Files
aevolution/docs/engineering/VALIDATION.md
T

4.0 KiB

Validation report

Recorded 2026-09-19. Native checks apply to base commit 8ab48d3 plus the foundation-delivery working changes committed with this report. Simulation rules and snapshot format remain version 1; the only C++ change is benchmark metadata. Results below distinguish executed checks from pending Linux/cluster gates.

Tools and host

  • Windows NT 10.0.26200, AMD Ryzen 7 9800X3D, 8 cores / 16 logical processors.
  • MSVC 19.44.35217.0, CMake 3.31.6-msvc6, Ninja 1.12.1.
  • clang-format and clang-tidy 19.1.5 (Visual Studio LLVM tools).
  • kubectl 1.31.4 / Kustomize 5.4.2 for offline manifest rendering.

Executed native checks

Command Observed result
./tools/windows-check.ps1 -Preset debug -Action check Configure/build passed; 5/5 CTests passed
./tools/windows-check.ps1 -Preset release -Action check Configure/build passed; 5/5 CTests passed under NDEBUG
./tools/windows-check.ps1 -Preset analysis -Action check clang-tidy/warnings-as-errors build passed; 5/5 CTests passed
./tools/windows-check.ps1 -Preset asan -Action check MSVC AddressSanitizer build passed; 5/5 CTests passed; this is NOT UBSan
./tools/windows-check.ps1 -Preset debug -Action format Passed with clang-format 19; repeated twice in one shell after helper fix
./build/release/evo-sim --seed 123456 --entities 8 --ticks 1000000 --verify-replay Exit 0; replay_verified=true; hash fab22c2e8ae1c379
./build/release/evo-benchmark Exit 0; MSVC 1944 Release, seed 123456, 10000 entities, 1000 ticks, 0.0210666 seconds, hash 3bad6db1612cbd1
Git Bash bash -n tools/ci/linux-check.sh and bash -n tools/ci/publish-image.sh Syntax checks passed; no Linux execution implied
kubectl kustomize deploy/kubernetes/dev Rendered Job, ServiceAccount and NetworkPolicy in evolution-dev; image marker intentionally unresolved

CTest covers the independently frozen 1000-tick fingerprint d61ad5bf0c928c76, seeded replay properties, malformed/semantic snapshot rejection, entity lifecycle, capacity/overflow, telemetry and CLI file continuation/alias protection. The expected-failure harness confirms tests remain active in Release.

The benchmark is a single uncontrolled wall-clock observation, not a performance threshold or an MMO capacity estimate. Its initial compiler output accidentally used hexadecimal; the stream now returns to decimal and reports MSVC 1944.

Gitea evidence

The maintainer's run 1399 on 8ab48d3a5639121693f5881b600482e870b49f05 completed successfully. API job records confirm verify (configure/build/CTest) and publish (Docker build/push) succeeded on runner theraborn-runners-runner-0, label ubuntu-22.04. This is evidence for the original workflow, not the expanded sanitizer/analysis jobs added in this change. Exact Linux tool versions must come from the expanded job logs; a runner label is not a compiler version.

Limitations and next gates

  • Local Docker Desktop has no running Linux engine. Container checks must run on the configured Gitea runner; no local container success is claimed.
  • Expanded Linux GCC14/Clang19, ASan/UBSan, TSan and libFuzzer jobs are pending a pushed workflow run. A configured job is not a passing check.
  • Sandbox process restrictions stalled native Ninja and blocked Git Bash signal pipes. Those attempts were stopped; checks reran successfully outside sandbox.
  • Repeated VsDevCmd initialization grew PATH beyond cmd's limit. The helper now reuses the matching x64 environment and deduplicates PATH; repeated checks pass.
  • The maintainer reports Argo setup, but this workspace has no Kubernetes context. No dev Job completion or cluster admission result is recorded yet.
  • No biology, network/load, durable server recovery or backup restore exists. Those remain M2, M7/M8 and later gates, not failing or passing foundation tests.

Update this report with run URL, tested commit, image digest and Job result when those checks execute. Never overwrite a golden merely to make CI pass.