simpletest/who_need_help
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record final local candidate verification

Browse Source
This commit is contained in:
SimpleTest 2026-08-13 06:18:32 +03:00
parent 67fd3feba7
commit 1eea74f454
1 changed files with 20 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/verification.md
View File

@ -5,19 +5,32 @@ results from product limits and unknown production properties.
## Current local candidate and operations recheck on 2026-08-13 ## Current local candidate and operations recheck on 2026-08-13
- Application source candidate `2aa246dcfc242150b6f1bc9a20aa0ff533bab932` passed the - Application source candidate `67fd3feba7861cb8a02217c8561d59a1348bb79c` passed the
complete isolated `scripts/quality.sh` pipeline in user-systemd unit complete isolated `scripts/quality.sh` pipeline in user-systemd unit
`codex-heavy-wnh-quality-head-2aa246d-20260813-043521-20260813-043521-1148257.service`. `codex-heavy-wnh-full-quality-67fd3fe-20260813-055440-3469820.service`.
ExUnit reported 469 passing tests with seed `142388`; the fourteen browser ExUnit reported 470 passing tests with seed `370513`; the fourteen browser
map tests passed; every configured quality and security gate passed; and the map tests passed; every configured quality and security gate passed; and the
final Debian 13.6 runtime-image scan reported zero detected final Debian 13.6 runtime-image scan reported zero detected
vulnerabilities. The unit exited successfully after 2 minutes 33.375 vulnerabilities. The unit exited successfully after 3 minutes 56.093
seconds with a measured 349.8 MiB systemd-unit memory peak. Exact-name seconds with a measured 319.5 MiB systemd-unit memory peak. Exact-name
inspection after the run found no remaining run-scoped container, network, inspection after the run found no remaining run-scoped container, network,
volume, or temporary quality/security image. volume, or temporary quality/security image.
- The same candidate passed the complete isolated browser E2E suite in
Chromium, Firefox, and WebKit: 63 expected tests passed, with zero skipped,
unexpected, or flaky results, in 318.724 seconds. The run covered desktop
and phone accessibility, registration and account settings, request and
activity workflows, private chat, consent-based tracking, handover and blind
reviews, notifications, viewport discovery and clustering, staff queues,
localization, and active-node failure recovery. The isolated user-systemd
unit
`codex-heavy-wnh-full-e2e-67fd3fe-20260813-061049-3960219.service`
completed successfully after 6 minutes 19.128 seconds with a 65.6 MiB
unit-level memory peak. Its structured result is retained at
`output/e2e/20260813031050-3960590/results.json`; exact-name inspection found
no remaining run-scoped container, network, volume, or temporary image.
- A fresh read-only production release plan compared this candidate with - A fresh read-only production release plan compared this candidate with
production revision `dafcdb36cbe221af0c880fd05da3321e181ddd2c`. It observed production revision `dafcdb36cbe221af0c880fd05da3321e181ddd2c`. It observed
twenty-one pending twenty-seven pending
commits, one reviewed `application_safe` migration commits, one reviewed `application_safe` migration
(`20260812120611_allow_inbox_only_nearby_subscriptions.exs`), external (`20260812120611_allow_inbox_only_nearby_subscriptions.exs`), external
PostgreSQL 18.4, unchanged shared-edge routing, and all twelve environment PostgreSQL 18.4, unchanged shared-edge routing, and all twelve environment
@ -37,7 +50,7 @@ results from product limits and unknown production properties.
`0600` on the independent BuyVM monitor host at `0600` on the independent BuyVM monitor host at
`/home/simple/.local/state/who-need-help/production-backup.json`. `/home/simple/.local/state/who-need-help/production-backup.json`.
- The independent BuyVM monitor remained enabled and active on its minute - The independent BuyVM monitor remained enabled and active on its minute
schedule. Its fresh check at `2026-08-12T22:48:15Z` reported production schedule. Its fresh check at `2026-08-13T03:09:02Z` reported production
readiness and the authenticated aggregate metrics scrape `up`. Its installed readiness and the authenticated aggregate metrics scrape `up`. Its installed
configuration still has no backup-freshness section because no operator configuration still has no backup-freshness section because no operator
maximum acceptable backup age has been selected. The heartbeat therefore maximum acceptable backup age has been selected. The heartbeat therefore