cc-ci

recipe-maintainers/cc-ci

Fork 0

Commit Graph

Author	SHA1	Message	Date
autonomic-bot	db124d5107	fix(2): matrix register test — bounded readiness-retry on transient post-restore 5xx (synapse re-establishing DB pool after restore-tier DROP DATABASE); assertion unchanged, RAISEs on persistent failure Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-30 00:52:18 +01:00
autonomic-bot	83508656f9	fix(2): Q4.1 matrix-synapse — e2e now COLD GREEN after capacity unblock + admin-via-container Capacity unblock (cc-ci RAM 4→8GB) cleared the deploy timeout. Additionally: - recipe_meta.py: dropped ENABLE_REGISTRATION=true (synapse refuses to start without enable_registration_without_verification=true, which the recipe doesn't expose); kept TIMEOUT=900. - functional/test_register_and_message.py: pivoted from public client-API register to the shared-secret admin endpoint called via container localhost () — bypasses the public router (where /_synapse/admin/* is not exposed), uses the abra-generated registration_shared_secret with HMAC-SHA1, doesn't require ENABLE_REGISTRATION. Cold-verifiable on cc-ci (log /root/ccci-q41-matrix-r7.log): RECIPE=matrix-synapse STAGES=install,custom cc-ci-run runner/run_recipe_ci.py install + custom both PASS; deploy-count=1; 5 assertions PASS: - generic + cc-ci install overlay - federation_version (server.name=Synapse + non-empty version) - health_check (client/versions) - register_and_message (two users register, send/receive, marker round-trips) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-28 15:54:42 +01:00
autonomic-bot	3036c60251	feat(2): Q4.1 partial — matrix-synapse Phase-2 code (NOT YET cold-verified end-to-end) Code-only commit. The Phase-2 functional tests + PARITY.md are written and locally consistent, but the e2e cold-verify on cc-ci is BLOCKED by abra deploy timing out (900s) on the matrix-synapse stack. The deploy hits the orchestrator's wait_healthy timeout — synapse + postgres-autoupgrade are too slow on this host (28GB disk, 3.5GB RAM, single node). Even after pruning Docker images (freed disk from 90% → 55% used), the deploy still times out. Root cause appears to be CPU/IO-bound startup on this host rather than disk space. What's landed (code-only): - tests/matrix-synapse/PARITY.md: parity table; the 3 recipe-maintainer shell-script tests (compress_state / test_complexity_limit / test_purge) deferred with technical rationale (operational regressions against persistent state — incompatible with the ephemeral per-run model). Phase-2 health_check added (the corpus has no health_check.py). - tests/matrix-synapse/functional/test_health_check.py: GET /_matrix/client/versions → 200 + JSON. - tests/matrix-synapse/functional/test_federation_version.py: GET /_matrix/federation/v1/version → 200, asserts server.name='Synapse' + non-empty server.version (plan §4.3 prescribed). - tests/matrix-synapse/functional/test_register_and_message.py: plan §4.3 prescribed test — registers two users via the public client API (m.login.dummy UIAA flow), logs in, creates a private_chat room, invites + joins user_b, sends an m.room.message with a uuid marker, reads the room's messages, asserts the marker appears in user_b's view. Non-vacuous full client-API roundtrip. - tests/matrix-synapse/recipe_meta.py: EXTRA_ENV adds ENABLE_REGISTRATION=true (lets the test use public client registration; admin endpoints aren't routed publicly by this recipe) and TIMEOUT=900 (overrides the recipe's default 300s abra-deploy convergence timeout). Cold-verify status: BLOCKED on cc-ci host capacity for matrix-synapse deploys — needs operator review (more disk / RAM / a heavier-recipe sequencing strategy). Filed in JOURNAL-2 + PushNotification. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-28 11:37:52 +01:00

Author

SHA1

Message

Date

autonomic-bot

db124d5107

fix(2): matrix register test — bounded readiness-retry on transient post-restore 5xx (synapse re-establishing DB pool after restore-tier DROP DATABASE); assertion unchanged, RAISEs on persistent failure

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-30 00:52:18 +01:00

autonomic-bot

83508656f9

fix(2): Q4.1 matrix-synapse — e2e now COLD GREEN after capacity unblock + admin-via-container

Capacity unblock (cc-ci RAM 4→8GB) cleared the deploy timeout. Additionally:

- recipe_meta.py: dropped ENABLE_REGISTRATION=true (synapse refuses to start without
  enable_registration_without_verification=true, which the recipe doesn't expose); kept
  TIMEOUT=900.
- functional/test_register_and_message.py: pivoted from public client-API register to the
  shared-secret admin endpoint called via container localhost () — bypasses the public router (where
  /_synapse/admin/* is not exposed), uses the abra-generated registration_shared_secret with
  HMAC-SHA1, doesn't require ENABLE_REGISTRATION.

Cold-verifiable on cc-ci (log /root/ccci-q41-matrix-r7.log):
  RECIPE=matrix-synapse STAGES=install,custom cc-ci-run runner/run_recipe_ci.py
  install + custom both PASS; deploy-count=1; 5 assertions PASS:
    - generic + cc-ci install overlay
    - federation_version (server.name=Synapse + non-empty version)
    - health_check (client/versions)
    - register_and_message (two users register, send/receive, marker round-trips)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-28 15:54:42 +01:00

autonomic-bot

3036c60251

feat(2): Q4.1 partial — matrix-synapse Phase-2 code (NOT YET cold-verified end-to-end)

Code-only commit. The Phase-2 functional tests + PARITY.md are written and locally consistent,
but the e2e cold-verify on cc-ci is BLOCKED by abra deploy timing out (900s) on the
matrix-synapse stack. The deploy hits the orchestrator's wait_healthy timeout — synapse +
postgres-autoupgrade are too slow on this host (28GB disk, 3.5GB RAM, single node).

Even after pruning Docker images (freed disk from 90% → 55% used), the deploy still times out.
Root cause appears to be CPU/IO-bound startup on this host rather than disk space.

What's landed (code-only):
- tests/matrix-synapse/PARITY.md: parity table; the 3 recipe-maintainer shell-script tests
  (compress_state / test_complexity_limit / test_purge) deferred with technical rationale
  (operational regressions against persistent state — incompatible with the ephemeral per-run
  model). Phase-2 health_check added (the corpus has no health_check.py).
- tests/matrix-synapse/functional/test_health_check.py: GET /_matrix/client/versions → 200 + JSON.
- tests/matrix-synapse/functional/test_federation_version.py: GET /_matrix/federation/v1/version
  → 200, asserts server.name='Synapse' + non-empty server.version (plan §4.3 prescribed).
- tests/matrix-synapse/functional/test_register_and_message.py: plan §4.3 prescribed test —
  registers two users via the public client API (m.login.dummy UIAA flow), logs in, creates a
  private_chat room, invites + joins user_b, sends an m.room.message with a uuid marker, reads
  the room's messages, asserts the marker appears in user_b's view. Non-vacuous full client-API
  roundtrip.
- tests/matrix-synapse/recipe_meta.py: EXTRA_ENV adds ENABLE_REGISTRATION=true (lets the test
  use public client registration; admin endpoints aren't routed publicly by this recipe) and
  TIMEOUT=900 (overrides the recipe's default 300s abra-deploy convergence timeout).

**Cold-verify status: BLOCKED on cc-ci host capacity for matrix-synapse deploys** — needs
operator review (more disk / RAM / a heavier-recipe sequencing strategy). Filed in JOURNAL-2 +
PushNotification.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-28 11:37:52 +01:00

3 Commits