ci: run the throw-away PostgreSQL without durability
CI / Build and test (pull_request) Failing after 4m5s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 12s
CI / Build and test (pull_request) Failing after 4m5s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 12s
On the runner's shared storage the 100k-frame bulk insert of the Phase 2 gate took 21-33 s against its 15 s budget: the timed tests should measure the client's COPY path, not the host's disk flushes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
7830fe46de
commit
f4800fd86d
2 files changed
+7
-2
No files matched your search
+1
-1
@@ -423,7 +423,7 @@ One line per decision: date · decision · alternative · reason.
|
||||
| 2026-10-23 | Releases are published in the repository that runs the workflow; the separate public releases repository of BRIEF §19.4 becomes optional (`RELEASES_REPO` and `RELEASES_TOKEN`). `EULA.md` and `SECURITY.md` move to the repository root and the issue forms to `.gitea/ISSUE_TEMPLATE` (Gitea's `about` key instead of GitHub's `description`), so they are live where the releases are; `deploy/releases-repo/` keeps only the README of a separate repository, to which release.yml copies the rest. Security reports go privately to the maintainers: Gitea has no private vulnerability reporting. (R2.) | Create `BalboSoft/chronos-releases` | §19.4 split the repositories because a private GitHub repository cannot serve release files; on a self-hosted Gitea the owner decides visibility of the one repository. |
|
||||
| 2026-10-23 | Gitea Actions workflows in `.gitea/workflows` run on act_runner in Docker mode: the .NET jobs use the `mcr.microsoft.com/dotnet/sdk:10.0` container and check out with git (the image has no Node.js for JavaScript actions), install the system SQLite (`libsqlite3-0`) the image lacks, use no artifacts or caches, and build with 4 cores (`BUILD_CPUS`) because the runner shares its host with Gitea, which stalled during the first unthrottled ReadyToRun build. Jobs that need docker use the runner's own image and the host's daemon. (R3.) | `actions/checkout` and `actions/setup-dotnet` in the runner image | Downloading the SDK on every job costs minutes and network; the SDK image stays on the host after its first pull. |
|
||||
| 2026-10-23 | The release cross-compiles the Windows programs on Linux (`EnableWindowsTargeting`, win-x64 runtime packs, ReadyToRun through the Linux crossgen). `Chronos.Tools pe-check` fails the release (and CI) when a published program is not a GUI program or lacks its icon, version information or PerMonitorV2 manifest, which the SDK copies into the apphost. Optional Authenticode signing uses osslsigncode (signtool needs Windows); the payload format already tolerates the appended certificate table. (R3.) | Require a Windows runner for releases | The owner's only runner is Linux; the resource check measured on the runner showed icon, version and manifest present, and the check keeps it that way. |
|
||||
| 2026-10-23 | New `Chronos.Tools` commands for the Linux runner: `zip` (the SDK image has no zip program), `gitea-release` (creates a draft for a new tag, uploads every file replacing same-named ones, publishes, then checks that every file is listed at its size; token from an environment variable, never printed) and `postgres-ci` (MD5, cleartext and trust roles with their pg_hba lines and TLS with a self-signed certificate for the service host name, all through SQL as the superuser: `pg_read_file`, `lo_export`, `ALTER SYSTEM`). `.github/scripts/postgres-ci-setup.sh` is gone: Gitea gives no service container id to `docker exec` into. (R3.) | curl and jq scripts; install docker or psql into the job | The SDK image has neither jq nor psql nor docker; C# commands are tested like the rest and keep the zero-package rule. |
|
||||
| 2026-10-23 | New `Chronos.Tools` commands for the Linux runner: `zip` (the SDK image has no zip program), `gitea-release` (creates a draft for a new tag, uploads every file replacing same-named ones, publishes, then checks that every file is listed at its size; token from an environment variable, never printed) and `postgres-ci` (MD5, cleartext and trust roles with their pg_hba lines and TLS with a self-signed certificate for the service host name, all through SQL as the superuser: `pg_read_file`, `lo_export`, `COPY … TO PROGRAM 'chmod 600'` for the key, `ALTER SYSTEM`; the CI server also runs without durability, fsync, synchronous commit and full-page writes off, because on the runner's shared storage the 100k-frame bulk insert of the Phase 2 gate took 21–33 s against its 15 s budget, a measure of the host's disk instead of the client's COPY path). `.github/scripts/postgres-ci-setup.sh` is gone: Gitea gives no service container id to `docker exec` into. (R3.) | curl and jq scripts; install docker or psql into the job | The SDK image has neither jq nor psql nor docker; C# commands are tested like the rest and keep the zero-package rule. |
|
||||
| 2026-10-23 | The server image is built for linux/amd64 only and pushed to the Gitea container registry (`<host of PUBLIC_URL>/<owner>/chronos-server`) with the `REGISTRY_TOKEN` secret; `:latest` moves only to the highest stable version among the published releases, read back after publishing. The workflow's own token is refused by the organisation's registry (measured), so without the secret the image job fails with instructions while the release itself is already published. (R3.) | Multi-arch with QEMU; fail the whole release | Multi-arch needs QEMU's binfmt handlers installed on the owner's host, a change to the host outside the repository; the Windows programs should not wait on a registry credential. |
|
||||
| 2026-10-23 | The Windows-only CI (Core.Windows and App tests, screenshots and their diff, the installer test) is the `windows` job, run only when the repository variable `WINDOWS_RUNNER` names a Windows act_runner in host mode; until then those tests run on a Windows PC before a merge. The Definition of Done says so (CLAUDE.md, BRIEF Appendix A). (R3.) | Drop them; fail CI without a Windows runner | They are the only automatic proof of the installer and the screens; a job that waits for a runner that does not exist would hold every run. |
|
||||
| 2026-10-23 | Update check: the client reads the published stable releases and takes the highest version, because Gitea's `releases/latest` is the most recently created release (a re-published older tag or a backport would become it); a pre-release build (`0.1.0-rc.1`) is offered the final release of its own version, which it used to call "up to date" forever; a 404 is a failed check, because Gitea answers 404 for a repository the client may not see (the `BalboSoft` organisation is private today) and that used to read as "up to date". The release workflow picks `:latest` the same way. `gitea-release` checks every file's size before it publishes, and when it replaces the files of a release clients can already see it removes the old `SHA256SUMS` first and uploads the new one last. (R2, R3; independent review of this change.) | Trust `releases/latest`; leave the pre-release rule as it was | The first release is a pre-release: its testers must be told when 0.1.0 is out; a download checked against the checksums of another build would be refused. |
|
||||
@@ -10,7 +10,8 @@ namespace Chronos.Tools.Commands;
|
||||
/// <summary>
|
||||
/// Prepares a PostgreSQL service container for the wire-protocol tests that need more than the image's defaults
|
||||
/// (BRIEF §6.3): one role per authentication method (MD5, cleartext, trust) with its pg_hba line ahead of the image's
|
||||
/// catch-all SCRAM line, and TLS with a self-signed certificate for the service's host name. Everything goes through
|
||||
/// catch-all SCRAM line, TLS with a self-signed certificate for the service's host name, and no durability (a CI
|
||||
/// server: fsync, synchronous commit and full-page writes off). Everything goes through
|
||||
/// SQL as the superuser (server-side file functions), so the CI job needs neither docker nor psql
|
||||
/// (amended 2026-10-23, R3: Gitea Actions gives no id of the service container to exec into).
|
||||
/// </summary>
|
||||
@@ -63,6 +64,10 @@ internal sealed class PostgresCiCommand : ICommand
|
||||
if (method == "md5") await session.ExecuteAsync("RESET password_encryption", [], ct);
|
||||
}
|
||||
await session.ExecuteAsync("ALTER SYSTEM SET ssl = on", [], ct);
|
||||
// A throw-away server on the runner's shared storage: no durability, so the timed tests (the 100k-frame bulk
|
||||
// insert of the Phase 2 gate) measure the client's protocol path rather than the host's disk flushes.
|
||||
foreach (var setting in new[] { "fsync", "synchronous_commit", "full_page_writes" })
|
||||
await session.ExecuteAsync($"ALTER SYSTEM SET {setting} = off", [], ct);
|
||||
await session.QuerySingleAsync("SELECT pg_reload_conf()", [], ct);
|
||||
}
|
||||
|
||||
|
||||
Reference in new issue
Block a user