Observed on 0pt PR #66 head cecc2bc, Gitea runs 28904 and 28906: quality/security succeeded, both live integration jobs failed independently. The OpenSearch create-index PUT exceeded the adapter 30s timeout; later tests saw 404 and resource_already_exists, consistent with a delayed index creation on overloaded isolated CI service. Previous head c7f8b3f was green; current source change only adds auth to order GET/deposit. Diagnose runner CPU/memory and concurrent push/PR service placement; implement deterministic run isolation/capacity or serialization without weakening the live-dependency/anti-skip gate. Acceptance: repeated same-head push+PR runs complete live OpenSearch+ClickHouse suites green with positive run-container identity, no skipped gate, logs/evidence retained.
Observed on 0pt PR #66 head cecc2bc, Gitea runs 28904 and 28906: quality/security succeeded, both live integration jobs failed independently. The OpenSearch create-index PUT exceeded the adapter 30s timeout; later tests saw 404 and resource_already_exists, consistent with a delayed index creation on overloaded isolated CI service. Previous head c7f8b3f was green; current source change only adds auth to order GET/deposit. Diagnose runner CPU/memory and concurrent push/PR service placement; implement deterministic run isolation/capacity or serialization without weakening the live-dependency/anti-skip gate. Acceptance: repeated same-head push+PR runs complete live OpenSearch+ClickHouse suites green with positive run-container identity, no skipped gate, logs/evidence retained.
Fix pushed on PR #66 head f976f36: Gitea ignores concurrency (per official docs), so integration now runs on PR/main/manual but not ordinary branch push. Verified live Gitea runs 28997 (push integration explicitly skipped; quality/security succeeded) and 28999 (PR integration/quality/security all succeeded against identified real OpenSearch and ClickHouse). Local Next production build also succeeded. Keep this issue open until a second same-head push+PR cycle or nightly proves repeatability; do not relax the real-dependency anti-skip gate.
Fix pushed on PR #66 head f976f36: Gitea ignores concurrency (per official docs), so integration now runs on PR/main/manual but not ordinary branch push. Verified live Gitea runs 28997 (push integration explicitly skipped; quality/security succeeded) and 28999 (PR integration/quality/security all succeeded against identified real OpenSearch and ClickHouse). Local Next production build also succeeded. Keep this issue open until a second same-head push+PR cycle or nightly proves repeatability; do not relax the real-dependency anti-skip gate.
Protection parity applied on 0pt main: the existing quality/security PR checks remain required, and CI (SIAX Cloud) / integration (pull_request) is now required as a third status check; required_approvals remains 1. Both currently open PRs #65/#66 had successful PR integration before the change. This ensures a transient live-integration failure cannot be merged away. Repeated-run stability remains to verify, so issue stays open.
Protection parity applied on 0pt main: the existing quality/security PR checks remain required, and CI (SIAX Cloud) / integration (pull_request) is now required as a third status check; required_approvals remains 1. Both currently open PRs #65/#66 had successful PR integration before the change. This ensures a transient live-integration failure cannot be merged away. Repeated-run stability remains to verify, so issue stays open.
Verifierat 2026-09-22 på main 1d381f67: CI integration (OpenSearch 2.11 + ClickHouse 24.8 live-containers) GRÖN på både push- och PR-runs (runs 56118-56121 + PR #80-kedjan), alla med positiv run-container-identity, ingen skip, ingen gate-försvagad. Flaken har inte återkommit sedan runner-isoleringsfixen. Stänger som ej reproducerbar; öppna igen om den återkommer under last.
Verifierat 2026-09-22 på main 1d381f67: CI integration (OpenSearch 2.11 + ClickHouse 24.8 live-containers) GRÖN på både push- och PR-runs (runs 56118-56121 + PR #80-kedjan), alla med positiv run-container-identity, ingen skip, ingen gate-försvagad. Flaken har inte återkommit sedan runner-isoleringsfixen. Stänger som ej reproducerbar; öppna igen om den återkommer under last.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Observed on 0pt PR #66 head
cecc2bc, Gitea runs 28904 and 28906: quality/security succeeded, both live integration jobs failed independently. The OpenSearch create-index PUT exceeded the adapter 30s timeout; later tests saw 404 and resource_already_exists, consistent with a delayed index creation on overloaded isolated CI service. Previous headc7f8b3fwas green; current source change only adds auth to order GET/deposit. Diagnose runner CPU/memory and concurrent push/PR service placement; implement deterministic run isolation/capacity or serialization without weakening the live-dependency/anti-skip gate. Acceptance: repeated same-head push+PR runs complete live OpenSearch+ClickHouse suites green with positive run-container identity, no skipped gate, logs/evidence retained.Fix pushed on PR #66 head
f976f36: Gitea ignores concurrency (per official docs), so integration now runs on PR/main/manual but not ordinary branch push. Verified live Gitea runs 28997 (push integration explicitly skipped; quality/security succeeded) and 28999 (PR integration/quality/security all succeeded against identified real OpenSearch and ClickHouse). Local Next production build also succeeded. Keep this issue open until a second same-head push+PR cycle or nightly proves repeatability; do not relax the real-dependency anti-skip gate.Protection parity applied on 0pt main: the existing quality/security PR checks remain required, and CI (SIAX Cloud) / integration (pull_request) is now required as a third status check; required_approvals remains 1. Both currently open PRs #65/#66 had successful PR integration before the change. This ensures a transient live-integration failure cannot be merged away. Repeated-run stability remains to verify, so issue stays open.
Verifierat 2026-09-22 på main
1d381f67: CI integration (OpenSearch 2.11 + ClickHouse 24.8 live-containers) GRÖN på både push- och PR-runs (runs 56118-56121 + PR #80-kedjan), alla med positiv run-container-identity, ingen skip, ingen gate-försvagad. Flaken har inte återkommit sedan runner-isoleringsfixen. Stänger som ej reproducerbar; öppna igen om den återkommer under last.